[FreeNX-kNX] Suspended Session

[Terje Andersen]

On Friday 23 May 2008 13:41:18 Stefan Kohlsmann wrote:
> > I just tested this with the following scenario:
> > 1) DISABLE_PERSISTENT_SESSION="tan"
> > 2) Established a session as the user 'tan'
> > 3) killed nxssh on the client (similar  to a network outage/disruption)
> > 4) 15 seconds later, the session was automatically terminated/removed on
> > the
> > server
> >
> > Isn't this what you want?
>
> Yes, exactly that's it.
> On my old FreeNX / Debian that works similar.
> If I kill the nxssh process / poweroff client on my "new" system, it looks
> like this:
>
> root at nx10:# nxserver --list
> NX> 100 NXSERVER - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
> NX> 127 Sessions list:
>
> Server     Display Username        Remote IP       Session ID
> ------ ------- --------------- ---------------
> -------------------------------- 127.0.0.1       1001    test      
> 192.168.3.155   1FD2D94F846FE88D5AEB2C8D9D4894E NX> 999 Bye
>
> in nxserver.log the status is right:
>
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 1
> NX> 1009 Session status: starting
> NX> 710 Session status: running
> NX> 1002 Commit
> NX> 1006 Session status: running
> NX> 105 bye
> Bye
> NX> 999 Bye
> NX> 596 Error: Session  failed. Reason was: Session: Display failure
> detected at 'Fri May 23 13:26:22 2008'. NX> 1009 Session status: suspending
> NX> 1005 Session status: suspended
>
> I found that "Session failed." in /usr/lib/nx/nxnode in line 843. I try to
> add the line : /usr/bin/nxserver --terminate $session_id (just to kill the
> session directly :-) ), but the nxnode runs whit out root rights :-) . The
> log's are right, but die nxserver --list command show the "wrong" status,
> why ?

Hmm. I don't get the same results as you do - here's my nxserver.log when a 
connected client "powers off" (kill nxssh) with the 
DISABLE_PERSISTENT_SESSION="tan" in node.conf:

NX> 1009 Session status: starting
server_nxnode_echo: NX> 1009 Session status: starting
NX> 710 Session status: running
server_nxnode_echo: NX> 710 Session status: running
NX> 1002 Commit
server_nxnode_echo: NX> 1002 Commit
NX> 1006 Session status: running
session_status E35E2F6D2567BE60CF1478641AF9C632 Running
server_nxnode_echo: NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
session_status E35E2F6D2567BE60CF1478641AF9C632 Terminating
server_nxnode_echo: NX> 1009 Session status: terminating
NX> 1006 Session status: closed
session_close E35E2F6D2567BE60CF1478641AF9C632
server_nxnode_echo: NX> 1006 Session status: closed
NX> 1001 Bye.
server_nxnode_echo: NX> 1001 Bye.

All I did here was to kill the nxssh process on the client, and the session 
state changed from running to terminating.

The only difference I can see, are the nxlibs version - I use 3.1.0, but I 
can't see how that could cause the difference in reactions to the broken 
communication with the client.

Within the ~15 seconds timeframe, my server shows the session as running until 
it times out, then it's terminated without entering the suspending state.

Regards,
Terje