package: x2goserver
version: 4.1.0.1-0~1613~ubuntu16.04.1
priority: bug
I added a limit of 10 for the x2gousers group like this :
[limit groups]
x2gousers=10
It seems to work when you connect directly with x2goclient (I get blocked when
I reach the limit so the group is the good one
package: x2gobroker
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: enhancement
I'm not really sure of that because it is pretty hard to reproduce that one but
I have the impression that, if you have many users connecting nearly at the
same time (and especially within the loadchecker sleep
package: x2gobroker
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: enhancement
In case of trouble, this is sometimes needed to block any new incoming
connection to the broker (the broker itself, not the x2go server).
For example, lately I did a stupid thing by mistake, I shut down a
package: x2gobroker-loadchecker
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: bug
I had a problem with broker loadbalancing not working anymore even though the
loadchecker service seemed to work well.
Looking at the logs, I found an unusual "sleep time" for the loadchecker
service then,
package: x2gobroker
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: enhancement
We encountered another corner case very annoying.
The whole broker stack does its work quite well when everything works as
expected (which is mostly the case).
A failing server for example is perfectly
package: x2gobroker-agent
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: bug
I don't have a "0" value anymore since latest fixes so the loadchecker process
don't crash anymore but still, there is something strange.
Here is a fragment of my loadchecker logs from this morning.
Just to give you
