2013/3/2 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
We have tried running /usr/lib/x2go/x2gobroker-agent abo findbusyservers
and got this output:
OK
16:testterm2
83:testterm1
Which tells me that it might be the x2gobroker-daemon which isn't using the
information correctly.
My plain guess is that this is related a DNS hostname / FQDN mismatching. The broker code has to become more tolerant about this.

Yes, after some more testing, that is indeed a problem. I have tried added some strategic debug-logging to the code and this is the content of busy_server_list in broker.base_broker.select_session(), after it gets info back from servers:

busy_server_list: [(0, 'testterm1.dsl.lan'), (0, 'testterm2.dsl.lan'), (100, 'testterm2')]

Meaning that it doesn't see those as the same. That is of course what bug #133 is about.

A more interesting problem as I see it, is why testterm2 is being reported with 100 in the above. In fact, when I look at the value of server_list in agent.find_busy_servers() this is the content:

busy_servers: {'testterm2': 100}

That is when I have a couple of users logged in to testterm1 and a load of 2.0 while testterm2 has no users and a load of 0.29. I still think something is wrong with the script that determines if a server is busy or not :)

--
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)