I have installex x2goserver version 4.0.1.19-x86_64-lsalix on a Salix
14.2 Linux system. I have enabled X forwarding in sshd and tested by sshd to the system and running xclock which correctly displays on my lock machine.
I have installed the mate desktop, it works on the local machine.
When I try to connect with x2goclient it hangs forever like it's waiting
for the salix machine but it never times out and prints an error dialogue.
Any suggestions on how to proceed?
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
I followed these steps exactly except for the path to the spool
directory for x2goprint (the instructions didn't have the full path for chown / chmod and in that case I substituted the full path for the directory name.
https://www.slackbuilds.org/repository/14.2/network/x2goserver/
Still, it hangs at connecting.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On the Salix server these are the only relevant messages I can find
in /var/log, these are in messages:
messages:Mar 21 00:50:06 salix /usr/bin/x2gosessionlimit[28105]: x2gosessionlimit has been called messages:Mar 21 00:50:06 salix /usr/bin/x2golistsessions[28171]: x2golistsessions has been called with options: --all-servers messages:Mar 21 00:50:52 salix /usr/bin/x2gosessionlimit[18519]: x2gosessionlimit has been called messages:Mar 21 00:50:52 salix /usr/bin/x2golistsessions[18607]: x2golistsessions has been called with options: --all-servers messages:Mar 21 16:49:40 salix /usr/bin/x2gosessionlimit[22541]: x2gosessionlimit has been called messages:Mar 21 16:49:40 salix /usr/bin/x2golistsessions[22544]: x2golistsessions has been called with options: --all-servers messages:Mar 21 16:53:29 salix /usr/bin/x2gosessionlimit[12527]: x2gosessionlimit has been called messages:Mar 21 16:53:29 salix /usr/bin/x2golistsessions[12596]: x2golistsessions has been called with options: --all-servers messages:Mar 23 01:01:43 salix /usr/bin/x2gosessionlimit[6431]: x2gosessionlimit has been called messages:Mar 23 01:01:43 salix /usr/bin/x2golistsessions[6434]: x2golistsessions has been called with options: --all-servers messages:Mar 23 02:05:44 salix /usr/bin/x2gosessionlimit[7520]: x2gosessionlimit has been called messages:Mar 23 02:05:44 salix /usr/bin/x2golistsessions[7523]: x2golistsessions has been called with options: --all-servers messages:Mar 23 02:17:18 salix /usr/bin/x2gosessionlimit[31642]: x2gosessionlimit has been called messages:Mar 23 02:17:19 salix /usr/bin/x2golistsessions[31671]: x2golistsessions has been called with options: --all-servers
I start the server with service start x2goserver and it launches and
writes a pid file in /var/run but then dies. I have the x2goserver log level set to debug but this is all I get.
This is on a Salix 12.2 (a derivative of Slackware 12.2).
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.