On 09.03.2015 04:06 PM, Julius K wrote:
2015-03-03 14:13 GMT+01:00 Mihai Moldovan <ionic@ionic.de <mailto:ionic@ionic.de>>:
On 01.03.2015 02:14 PM, Julius K wrote: > $ x2gostartagent > [Error Message] > > I'm on Linux Miant 17 Qiana with the x2go/stable ppa. > [...] x2gostartagent is not meant to be started manually, but only via x2goclient or pyhoca-*. Thus, the behavior shown is correct.Ooh, I'm really sorry for this, I thought I have to start the server manually but it starts automatically after installation, right?
I'll be adding back the list, because this may be of interest for other people, too.
X2Go Server is not using a daemon for its normal mode of operation, so there's nothing "started" (neither automatically nor manually) after installation. The init script that is automatically is merely running "x2gocleansessions" to get rid of stale/disconnected/terminated sessions. (But creating sessions will still work even with this disabled. You just may have a mess on your hands afterwards...)
Every session is started by X2Go Client (or PyHoca-*) via SSH. Both launch x2gostartagent via the SSH connection to the remote server *when creating a new session*.
Thus, once you install x2goserver, it's ready to use (minus special features which come in via, e.g., x2goserver-xsession.)
What is the real problem at hand?Now I try to connect from a windows machine to Linux, but it doesn't work. I checked, ssh works. When I connect, sometimes it gives an error message like this: "failed to suspend session with ID [...]" or the programm just gets totally unresponsive and I have to restart it.
Ok, that's more interesting and actually suitable for the bug report.
Please start up cmd.exe, then:
cd path\where\x2goclient.exe\is\installed\in x2goclient.exe --debug > debug.log 2>&1
The debug log could potentially be helpful in tracking this down. When you respond, please make sure to CC 800@bugs.x2go.org.
Mihai