Re: [X2Go-User] Can't resume session on RHEL6 system properly

[John Stoffel]

> "Ulrich" == Ulrich Sibiller  writes:

Ulrich> On Thu, Jul 13, 2017 at 4:12 PM, John Stoffel  wrote:
>> 
Ulrich> That kde Session type is irrelevant. Your Session is probably broken 
beyond
Ulrich> repair. You can try sending SIGHUP to the x2goagent process and see if 
that
Ulrich> helps.
>> 
>> And there's no x2goagent process... just an nxagent process.  Damn.  I
>> wonder what happened.  I really like x2go, but debugging it is horrible...

Ulrich> Then try nxagent. I was unsure about the final procress name anyway ;-)

I tried doing a kill -HUP, and it killed it all off.  Oh well...

Ulrich> On the Server you can find a Logfile in ~/.x2go somewhere. Maybe it 
contains
Ulrich> some Information about what happened.
>> 
>> Nothing obivous unfortunately.  Any suggestions on how to make it more
>> stable?

Ulrich> You could try the current nx-libs beta:
Ulrich> http://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting, it
Ulrich> contains lots of bugfixes.

Ulrich> Loop: PANIC! The remote NX proxy closed the connection.
Ulrich> Loop: PANIC! Failure negotiating the session in stage '7'.
Ulrich> Loop: PANIC! Wrong version or invalid session authentication cookie.

Ulrich> Are you really use the same version of nx-libs on both sides?

Ulrich> What packages (+ version) do you have running on both sides?

See my initial email, I gave the package information on both sides.
It's worked in the past without problems, but lately it's been much
more flaky.

Maybe I need to upgrade to the latest release on RHEL6, but from what
I see on the web pages, there are problems with the later versions
with GNOME based desktops.

So it's looking more and more like something else will have to take
over for my needs.  Not sure what...
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't resume session on RHEL6 system properly

[Ulrich Sibiller]

On Thu, Jul 13, 2017 at 4:12 PM, John Stoffel  wrote:
>
> Ulrich> That kde Session type is irrelevant. Your Session is probably broken 
> beyond
> Ulrich> repair. You can try sending SIGHUP to the x2goagent process and see 
> if that
> Ulrich> helps.
>
> And there's no x2goagent process... just an nxagent process.  Damn.  I
> wonder what happened.  I really like x2go, but debugging it is horrible...

Then try nxagent. I was unsure about the final procress name anyway ;-)

> Ulrich> On the Server you can find a Logfile in ~/.x2go somewhere. Maybe it 
> contains
> Ulrich> some Information about what happened.
>
> Nothing obivous unfortunately.  Any suggestions on how to make it more
> stable?

You could try the current nx-libs beta:
http://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting, it
contains lots of bugfixes.

> Ulrich>Loop: PANIC! The remote NX proxy closed the connection.
> Ulrich>Loop: PANIC! Failure negotiating the session in stage '7'.
> Ulrich>Loop: PANIC! Wrong version or invalid session authentication 
> cookie.

Are you really use the same version of nx-libs on both sides?

What packages (+ version) do you have running on both sides?

Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Can't resume session on RHEL6 system properly

[John Stoffel]

Guys,
I've got an x2go session where it looks like there's some disagreement
internally between what the state really is on the system.  I'm seeing
the following messages in the /var/log/messages file:

   Jul 12 22:51:58 x2go-server /usr/sbin/x2gocleansessions[3243]: 
john-50-1498570300_stDGNOME_dp24: session status S desynchronized with current 
status (R) and session suspend already tried unsuccessfully
   Jul 12 22:52:12 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:52:30 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:52:49 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:53:08 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:53:28 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:53:47 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
   Jul 12 22:54:06 x2go-server /usr/bin/x2gosuspend-session: session with ID 
john-50-1498570300_stDGNOME_dp24 has been suspended successfully


Note the first line?  Where is says the session status is desynchronized?  How 
would I fix this?

The server is running CentOS 6.9 (Final) x86_64:

   # 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


And my client in a Linux Mint 18.2 x86_64 system with:

> dpkg-query -l |grep x2go
ii  nxproxy  
2:3.5.0.32-0x2go1+git20170412.734+8.main.1 amd64NX proxy
ii  pyhoca-cli   
0.5.0.3-0x2go1+git20170412.224+8.main.1all  Command line X2Go 
client written in Python
ii  pyhoca-gui   
0.5.0.6-0x2go1+git20170413.1337+8.main.1   all  Graphical X2Go client 
written in (wx)Python
ii  python-x2go  0.5.0.4-1  
all  Python module providing X2Go client API
ii  x2go-keyring 
2012.07.23~jessie~main~17~build1   all  GnuPG keys of all X2Go 
developers and the X2Go archive
ii  x2goclient   
4.1.0.0-0x2go1+git20170413.1549+8.main.1   amd64X2Go Client application 
(Qt4)


Now if I go and sit at the x2go-server system, and use the x2goclient
to connect to the session, it's pretty much going to work, though
sometimes it still fails and I need to wipe my working session.  Which
sucks.

I also see, on the client system the following in the file:

   $ cat ~/.x2go/S-john-50-1498570300_stDGNOME_dp24/sessions
   Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent 
session.
   Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent 
session.
   Loop: PANIC! The remote NX proxy closed the connection.
   Loop: PANIC! Failure negotiating the session in stage '7'.
   Loop: PANIC! Wrong version or invalid session authentication cookie.


But I never use kde as my session, and it's configured to use GNOME
only.  I've never used KDE at all, except to run their great CD buring
tool k3db at points.

What other debug info can I provide?

Thanks,
John
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user