I have not been successful at getting x2go to work consistently onmachines I have upgraded to Ubuntu 17.04, oddly it works on some and not others. I have two machines on which it appears to work fine and two which it does not, one of those it just gives me a black screen and the other it immediately exits. On the machine that it immediately exits it prints some error messages but the client exits too fast to read them. I can't figure out if and where x2go logs erros. I do see some things in the syslog but indicates it is starting the session successfully when obviously it is not.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 installed exactly the same repositories on a machine that isn't workingas a machine that is, did an apt clean all, removed all x2go* and nxlibs and libNX* and nxagent and re-installed, still it immediately exits on this machine.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Mon, 24 Apr 2017, Robert Dinse wrote:
Date: Mon, 24 Apr 2017 21:18:43 -0700 (PDT) From: Robert Dinse <nanook@eskimo.com> To: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: [X2Go-User] x2goserver on Ubuntu 17.04 Zesty
I have not been successful at getting x2go to work consistently onmachines I have upgraded to Ubuntu 17.04, oddly it works on some and not others. I have two machines on which it appears to work fine and two which it does not, one of those it just gives me a black screen and the other it immediately exits. On the machine that it immediately exits it prints some error messages but the client exits too fast to read them. I can't figure out if and where x2go logs erros. I do see some things in the syslog but indicates it is starting the session successfully when obviously it is not.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
I have not been successful at getting x2go to work consistently on machines I have upgraded to Ubuntu 17.04, oddly it works on some and not others. I have two machines on which it appears to work fine and two which it does not, one of those it just gives me a black screen and the other it immediately exits. On the machine that it immediately exits it prints some error messages but the client exits too fast to read them. I can't figure out if and where x2go logs erros. I do see some things in the syslog but indicates it is starting the session successfully when obviously it is not.
Have you seen this page on how to enable debug logging? http://wiki.x2go.org/doku.php/wiki:development:debugging <http://wiki.x2go.org/doku.php/wiki:development:debugging> Other logging locations apart from the system's log are:
X2Go Server: /var/log/syslog X2Go Client: stderr (use –debug) PyHoca-GUI: stderr (use –libdebug –debug) Xsession itself: $HOME/.xsession-x2go-errors NX (server-side): $HOME/.x2go/C-<sessionid>/session.* NX (client-side): $HOME/.x2go/S-<sessionid>/session.* The default log levels for x2goserver and cups-x2go are set to notice. Available log levels are: emerg, crit, alert, err, warning, notice, info, debug. The x2goserver log level can be set by editing:
root@x2goserver:~$ editor /etc/x2go/x2goserver.conf Debugging X2Go Session Broker
The x2gobroker debug mode can be enabled in:
root@broker:~$ editor /etc/default/python-x2gobroker The log files normally get written to /var/log/x2gobroker/*.log
You can also run
root@broker:~$ x2gobroker-daemon-debug as user root. This is equivalent to running the broker daemon provided by the package x2gobroker-daemon, but you will see all output piped to stderr while the X2Go Session Broker daemon runs in foreground mode.
No, but appreciate the reference. I've been up all night, going to getsome sleep. I now know the issue is somehow related to the Arctica Project's nx-libs, without them I don't automatically get a full screen but it at least works and I can set manually. I'll try to narrow down which specific item is broken by installing one at a time until I find what breaks.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Tue, 25 Apr 2017, Robert Kudyba wrote:
Date: Tue, 25 Apr 2017 10:39:51 -0400 From: Robert Kudyba <rkudyba@fordham.edu> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] x2goserver on Ubuntu 17.04 Zesty
I have not been successful at getting x2go to work consistently on machines I have upgraded to Ubuntu 17.04, oddly it works on some and not others. I have two machines on which it appears to work fine and two which it does not, one of those it just gives me a black screen and the other it immediately exits. On the machine that it immediately exits it prints some error messages but the client exits too fast to read them. I can't figure out if and where x2go logs erros. I do see some things in the syslog but indicates it is starting the session successfully when obviously it is not.
Have you seen this page on how to enable debug logging? http://wiki.x2go.org/doku.php/wiki:development:debugging <http://wiki.x2go.org/doku.php/wiki:development:debugging> Other logging locations apart from the system's log are:
X2Go Server: /var/log/syslog X2Go Client: stderr (use ÿÿdebug) PyHoca-GUI: stderr (use ÿÿlibdebug ÿÿdebug) Xsession itself: $HOME/.xsession-x2go-errors NX (server-side): $HOME/.x2go/C-<sessionid>/session.* NX (client-side): $HOME/.x2go/S-<sessionid>/session.* The default log levels for x2goserver and cups-x2go are set to notice. Available log levels are: emerg, crit, alert, err, warning, notice, info, debug. The x2goserver log level can be set by editing:
root@x2goserver:~$ editor /etc/x2go/x2goserver.conf Debugging X2Go Session Broker
The x2gobroker debug mode can be enabled in:
root@broker:~$ editor /etc/default/python-x2gobroker The log files normally get written to /var/log/x2gobroker/*.log
You can also run
root@broker:~$ x2gobroker-daemon-debug as user root. This is equivalent to running the broker daemon provided by the package x2gobroker-daemon, but you will see all output piped to stderr while the X2Go Session Broker daemon runs in foreground mode.
Hi guys, I'm running a CentOS 6.8 x86_64 system using the following versions of x2go:
rpm -qa |grep x2go x2goclient-4.0.1.4-1.el6.x86_64 x2goserver-4.0.1.20-1.el6.x86_64 x2golxdebindings-debuginfo-1.0.2.4-1.1.x86_64 x2goserver-xsession-4.0.1.20-1.el6.x86_64 python-x2go-0.5.0.3-1.el6.noarch x2goagent-3.5.0.32-3.1.x86_64 x2gognomebindings-2.0.2.1-2.1.x86_64
My home system is a Linux Mint Serena 18.1 MATE x86_64 system. It's having problems connecting to the CentOS system.
So I use this CentOS system as both the x2go server, and as the client, so I can work from either home or work with the same session. But now from my home system (Linux Mint Serena 18.1 x86_64), I can't get a running session, it just hangs. Running x2goclient --debug I get the following:
x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 3: "x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 wan 16m-jpeg-9 us auto 1 both"
x2go-DEBUG-../src/sshprocess.cpp:204> this=SshProcess(0x264ec60) Running masterCon->addChannelConnection(this, ' "47d7a6d9-893d-45ed-b62c-4fe558416916" ', ' "bash -l -c 'echo "X2GODATABEGIN:47d7a6d9-893d-45ed-b62c-4fe558416916"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 w" ');
x2go-DEBUG-../src/sshmasterconnection.cpp:1325> Locking SSH channel connection MUTEX.
x2go-DEBUG-../src/sshmasterconnection.cpp:1327> Passing new channel conenction object to channelConnections.
x2go-DEBUG-../src/sshmasterconnection.cpp:1329> Unlocking SSH channel connection MUTEX.
x2go-DEBUG-../src/sshmasterconnection.cpp:1517> Creating new channel.
x2go-DEBUG-../src/sshmasterconnection.cpp:1521> New channel:0x7fc7f4012790
x2go-DEBUG-../src/sshmasterconnection.cpp:1552> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:47d7a6d9-893d-45ed-b62c-4fe558416916"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; x2goresume-session stoffj-50-1490735175_stDGNOME_dp24 1800x1100 wan 16m-jpeg-9 us auto 1 both; echo "X2GODATAEND:47d7a6d9-893d-45ed-b62c-4fe558416916";'"
x2go-DEBUG-../src/sshmasterconnection.cpp:1575> New exec channel created.And it just seems to hang here. On the server, I see the following in /var/log/messages:
Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:16 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:22 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:27 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:35 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfully
Apr 25 18:09:41 sekrit /usr/bin/x2gosuspend-session: session with ID stoffj-50-1490735175_stDGNOME_dp24 has been suspended successfullyAnd on the x2goserver system, in the session.log file I see:
[root@sekrit C-stoffj-50-1490735175_stDGNOME_dp24]# tail session.log
Session: Suspending session at 'Tue Apr 25 18:11:31 2017'.
Session: Session suspended at 'Tue Apr 25 18:11:31 2017'.
Session: Resuming session at 'Tue Apr 25 18:11:31 2017'.
Warning: Option file doesn't contain a port specification.
Info: Proxy running in server mode with pid '14478'.
Info: Waiting for connection from any host on port '4050'.
Info: Aborting the procedure due to signal '1'.
Session: Display failure detected at 'Tue Apr 25 18:11:37 2017'.
Session: Suspending session at 'Tue Apr 25 18:11:37 2017'.
Session: Session suspended at 'Tue Apr 25 18:11:37 2017'.so I'm wondering what has happened here? I'm trying to update my CentOS system to the latest packages, but it's probably not going to help since I don't see any x2go packages in the update.
Is there anything else I can do to help debug this?
Thanks, John
-
John Stoffel -
Robert Dinse -
Robert Kudyba