On 01/16/2012 07:42 PM, Richard Strysniewicz wrote:
On 01/16/2012 07:28 PM, John A. Sullivan III wrote:
<Snip> Just a hunch - I wonder if there is an underlying SSH problem - John
I cannot say for sure, but I do believe basic ssh is working fine...
I have public/private keys set up and I do ssh between the machines frequently. I have never had a failure to connect or any other error using ssh from the command line. Is there something I can try besides plain old command line ssh to more closely emulate what is going on with x2go connections?Thanks, Richard
Sorry, accidentally replied directly instead of to the list...
On Mon, 2012-01-16 at 21:22 -0500, Richard Strysniewicz wrote:
On 01/16/2012 07:42 PM, Richard Strysniewicz wrote:
On 01/16/2012 07:28 PM, John A. Sullivan III wrote:
<Snip> Just a hunch - I wonder if there is an underlying SSH problem - John
I cannot say for sure, but I do believe basic ssh is working fine...
I have public/private keys set up and I do ssh between the machines frequently. I have never had a failure to connect or any other error using ssh from the command line. Is there something I can try besides plain old command line ssh to more closely emulate what is going on with x2go connections? <snip>I'm wondering if it has nothing to do with establishing a new session but confusion about an existing session. When that existing session finally times out, then you can magically connect. Just an off the cuff guess - John
Hi John,
and hello to all others in the list, Here are some hints from my side. Did you change some Network Hardware? I had it in the past with ltsp (which I used before) that somehow a change of network hardware causes in this error. (change of network card, router/switch, additional clients?)
Maybe you can install iptraf (traffic monitor) apt-get install iptraf
It seems to be that the network stream break down and the session still exist, and after a timeout you can connect again. Now we have to find out why this happen ...
How often does this happen? (After 10 minutes connection ... or once a day?)
Did you tail -f /var/log/syslog on the server when you try to connect with this error message?
Best regards T.
Am 17. Januar 2012 04:09 schrieb John A. Sullivan III < jsullivan@opensourcedevel.com>:
On Mon, 2012-01-16 at 21:22 -0500, Richard Strysniewicz wrote:
On 01/16/2012 07:42 PM, Richard Strysniewicz wrote:
On 01/16/2012 07:28 PM, John A. Sullivan III wrote:
<Snip> Just a hunch - I wonder if there is an underlying SSH problem - John
I cannot say for sure, but I do believe basic ssh is working fine... I have public/private keys set up and I do ssh between the machines frequently. I have never had a failure to connect or any other error using ssh from the command line. Is there something I can try besides plain old command line ssh to more closely emulate what is going on with x2go connections? <snip>
I'm wondering if it has nothing to do with establishing a new session but confusion about an existing session. When that existing session finally times out, then you can magically connect. Just an off the cuff guess - John
X2go-User mailing list X2go-User@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-user
I've been trying to isolate an still no luck. I installed x2goserver on another ubuntu 10.10 machine and get similar issues.
To answer the how often question - I create and/or reconnect to to sessions several times each day and have not had a success on the first try for as long as I can remember, maybe some time mid to late last year.
And to answer the hardware question, no, same NICs on all machines, same cabling, same switch for past year or more. And these are all on a LAN, all on the same subnet. All are using wired Gig Ethernet.
Connecting to an existing session - from syslog: Feb 2 12:06:40 ubuntuservera /usr/bin/x2goresume-session: client 192.168.1.22 has successfully resumed session with ID rich-50-1328202198_stDGNOME_dp24 Feb 2 12:06:42 ubuntuservera /usr/bin/x2gomountdirs[21954]: WARNING: insertion of /home/rich/.x2go/S-rich-50-1328202198_stDGNOME_dp24/spool failed (already mounted?), not mounting get dialog box with X2Go - 50 message "The connection with the remote server was shut down. Please check the state of your network connection."
Try again - from syslog: Feb 2 12:09:14 ubuntuservera /usr/bin/x2goresume-session: client 192.168.1.22 has successfully resumed session with ID rich-50-1328202198_stDGNOME_dp24 get dialog box with X2Go - 50 message "The connection with the remote server was shut down. Please check the state of your network connection."
Try again 8 more times, same results as previous. Feb 2 12:10:42 ubuntuservera /usr/bin/x2goresume-session: last message repeated 2 times Feb 2 12:11:34 ubuntuservera /usr/bin/x2goresume-session: last message repeated 6 times
On the 9th try connected fine and had another message written to syslog: Feb 2 12:11:34 ubuntuservera /usr/bin/x2gomountdirs[26660]: successfully mounted rich@127.0.0.1:30003/home/rich/.x2go/S-rich-50-1328202198_stDGNOME_dp24/spool to /tmp/spool_rich/rich-50-1328202198_stDGNOME_dp24
This is just an example, does not always take 9 tries.
When closed above sesion the following was written to syslog: Feb 2 12:13:29 ubuntuservera /usr/bin/x2gosuspend-session: session with ID rich-50-1328202198_stDGNOME_dp24 has been suspended successfully Feb 2 12:13:29 ubuntuservera /usr/bin/x2goumount-session[27079]: ERROR: failed to unmount /tmp/spool_rich/rich-50-1328202198_stDGNOME_dp24
Tried to connect again, same error results as earlier.
Waited 5 minutes, tried again, successful connection: Feb 2 12:20:54 ubuntuservera /usr/bin/x2goresume-session: client 192.168.1.22 has successfully resumed session with ID rich-50-1328202198_stDGNOME_dp24 Feb 2 12:20:56 ubuntuservera /usr/bin/x2gomountdirs[29308]: successfully mounted rich@127.0.0.1:30003/home/rich/.x2go/S-rich-50-1328202198_stDGNOME_dp24/spool to /tmp/spool_rich/rich-50-1328202198_stDGNOME_dp24
Closed: Feb 2 12:21:48 ubuntuservera /usr/bin/x2gosuspend-session: session with ID rich-50-1328202198_stDGNOME_dp24 has been suspended successfully Feb 2 12:21:49 ubuntuservera /usr/bin/x2goumount-session[29580]: ERROR: failed to unmount /tmp/spool_rich/rich-50-1328202198_stDGNOME_dp24
Waited 5 minutes, tried again, same error results as earlier: Feb 2 12:27:53 ubuntuservera /usr/bin/x2goresume-session: client 192.168.1.22 has successfully resumed session with ID rich-50-1328202198_stDGNOME_dp24 Feb 2 12:27:55 ubuntuservera /usr/bin/x2gomountdirs[30721]: WARNING: insertion of /home/rich/.x2go/S-rich-50-1328202198_stDGNOME_dp24/spool failed (already mounted?), not mounting get dialog box with X2Go - 50 message "The connection with the remote server was shut down. Please check the state of your network connection."
Tried again, failed 14 times, connected on 15th try.
So is there possibly a mount/unmount issue? That might explain the variability in the number of times I have to try before getting a successful connection. Or perhaps an ssh issue that is not apparent from the logs? I looked in /var/log/messages, user.log, auth.log, daemon.log but no other x2go messages. No other files in /var/log were written to during the above testing.
On 01/17/2012 03:33 AM, Torsten Bade wrote:
Hi John,
and hello to all others in the list, Here are some hints from my side. Did you change some Network Hardware? I had it in the past with ltsp (which I used before) that somehow a change of network hardware causes in this error. (change of network card, router/switch, additional clients?)
Maybe you can install iptraf (traffic monitor) apt-get install iptraf
It seems to be that the network stream break down and the session still exist, and after a timeout you can connect again. Now we have to find out why this happen ...
How often does this happen? (After 10 minutes connection ... or once a day?)
Did you tail -f /var/log/syslog on the server when you try to connect with this error message?
Best regards T.
-
John A. Sullivan III -
Richard Strysniewicz -
Torsten Bade