I mentioned this problem last week and went back and forth a few times but there was no resolution.  Since I am being paid to implement this I have no choice but to bring it up again.  My apologies.

I have the broker running on a login server and my applications running on 3 x2go servers.  Everything is working fine except for this one thing.

I can suspend a session, and when I run x2golistsessions I am seeing the suspended sessions in the database.  But when I run the same application the suspended session is not starting up, I am getting a new one.  I can verify that because if I run x2golistsessions while the new session is running I see two sessions in the database.

I’ve tried taking two of my application servers out of the picture and limiting it to 1, but I still see the same thing.

I’ve got PostgreSQL running on my broker server, and all the application servers access it without a problem.  At least I can run x2golistsessions on all three without a problem.

If it matters, after running x2goversion on the application servers I’m seeing this

x2goserver: 4.1.0.0

x2goserver-common: 4.1.0.0

x2goserver-extensions: 4.1.0.0

x2goserver-x2goagent: 3.5.99.16

x2goserver-xsession: 4.1.0.0

And on the broker server I see this

X2goserver: 4.1.0.2

X2goserver-common: 4.1.0.2

X2goserver-extensions: 4.1.0.2

X2goserver-x2goagent: 3.5.99.16

X2goserver-xsession: 4.1.0.2

Any suggestions would be appreciated.