[FreeNX-kNX] Shadow Session fails to attach

Wed May 29 09:27:25 UTC 2013

I cleared all the old session files and folders, restarted freenx-server and I was left with the following in the .nx folder.

drwx------  2 cscs cscs  4096 Apr  5 13:31 cache-gnome
drwx------  2 cscs cscs  4096 Apr 16 11:14 cache-unix-desktop
drwx------  2 cscs cscs  4096 Apr 16 15:38 config
-rw-rw-r--  1 cscs cscs 23414 May 29 08:29 nxnode.log

After starting an NX client session with my 'cscs' account, I get a new session folder and a related log file.
drwx------  2 cscs cscs  4096 Apr  5 13:31 cache-gnome
drwx------  2 cscs cscs  4096 Apr 16 11:14 cache-unix-desktop
drwx------  4 cscs cscs  4096 May 29 08:32 C-me-promis-1001-F788D968C2342B30F59E25FE2F04A052
drwx------  2 cscs cscs  4096 Apr 16 15:38 config
-rw-rw-r--  1 cscs cscs  2904 May 29 08:32 nxnode-F788D968C2342B30F59E25FE2F04A052.log
-rw-rw-r--  1 cscs cscs 23991 May 29 08:32 nxnode.log

I started a shadow session, also with 'cscs' and I then get a file and folder related to my shadow session
drwx------  2 cscs cscs  4096 Apr  5 13:31 cache-gnome
drwx------  2 cscs cscs  4096 Apr 16 11:14 cache-unix-desktop
drwx------  4 cscs cscs  4096 May 29 08:32 C-me-promis-1001-F788D968C2342B30F59E25FE2F04A052
drwx------  4 cscs cscs  4096 May 29 08:44 F-C-me-promis-1001-722C9235C4CB53CFF4EEDF5DB15E703D
-rw-rw-r--  1 cscs cscs  4993 May 29 08:45 nxnode-722C9235C4CB53CFF4EEDF5DB15E703D.log
-rw-rw-r--  1 cscs cscs  2904 May 29 08:32 nxnode-F788D968C2342B30F59E25FE2F04A052.log
drwx------  2 cscs cscs  4096 Apr 16 15:38 config
-rw-rw-r--  1 cscs cscs 26079 May 29 08:43 nxnode.log

The shadow client shows me the list of active sessions that can be shadowed, I select the session and click attach, the client says 'negotiating link parameters' and the after a moment says 'Connection timeout'.

I've attached a tar of my .nx folder, the /etc/nxserver and the nxserver.log.

Many thanks for all your assistance.  Much appreciated.

Len

From: freenx-knx-bounces at kde.org [mailto:freenx-knx-bounces at kde.org] On Behalf Of chris at ccburton.com
Sent: 28 May 2013 10:56
To: User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Shadow Session fails to attach

freenx-knx-bounces at kde.org wrote on 28/05/2013 10:29:27:

> Hi Chris, 
>   
> Thanks for the info. 
>   
> I’ve checked my configuration and I have the following options set 
> in my node.conf file. 
>   
> ENABLE_SESSION_SHADOWING_AUTHORIZATION=0 
> ENABLE_INTERACTIVE_SESSION_SHADOWING=1 

OK 

>   
> Permissions on my nxshadowacl file are :  -rwxr-xr-x   1 root root  
> 143 May 22 19:55 nxshadowacl 
>   
> The contents of my nxshadowacl is : 
> #!/bin/sh 
> # Deny all sessions to be shadowed by anyone besides the same user. 
> # exit 1 
> # Allow all sessions to be shadowed by anyone. 
> exit 0 
>   
> As I just have exit 0 in my nxshadowacl, shadowing should work 
> between any two users. 

Yup 

>   
> When I shadow any session (same user as well other users) I get an 
> error.  The error message is: 
> Error: Aborting session with 'Server is already active for display XXXX 
>         If this server is no longer running, remove /tmp/.XXXXX-lock 
>         and start again'. 
> Session: Aborting session at 'Tue May 28 10:15:57 2013'. 
> Session: Session aborted at 'Tue May 28 10:15:57 2013'. 

> I’m rather stumped as to what could be causing the problem.  Any 
> other thoughts? 
>   
> Any help much appreciated. 
>   
>   
> Len 
>   
>   

Sounds like the shadow cookie isn't working, 
tho 
there may be something else going wrong. 

eg the new uniquid may be being ignored . . 

You should get ( in your ~/.nx/ on the FreeNX machine ) 
two session directories for the shadowing exercise 
one for the original 

 ( going off your logging in your original posting ) 

1/ the original ( shodowed ) session 
        C-me-promis-2003-1A756A55A57CDF54770F8B251B402EF2 

2/ the new shadowing session ( in your example ) 
        C-me-promis-2008-CE1851695B1C61D4D4A2E63C8A2739B9 

2008 being the next free display in the example . . . 

The authority file in the shadowing session in this example 
        C-me-promis-2008-CE1851695B1C61D4D4A2E63C8A2739B9/authority 
should have cookies for both displays. 

>   
> If I remove the lock file and retry I still get the errors and the 
> session file now contains… 

Don't do that .  . 

. . The lock file is OK 

[SNIP] 

> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot 

nxagent falls over straight away . . . 

> set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/cscs/.
> nx/F-C-me-promis-2003-CE1851695B1C61D4D4A2E63C8A2739B9/session". You
> might also want to try: ssh -X myserver; /usr/lib/nx/nxnode --agent 
> to test the basic functionality. Session log follows: 
> Can't open 
> /var/lib/nxserver/db/running/sessionId{CE1851695B1C61D4D4A2E63C8A2739B9}:

. . . before the session is set up . . . 

so 

1/ Try and clear all connections except the two mirroring ones to avoid confusion 
        You don't have to do this if you can't get the others to disconnect but 
        it will make confusion less likely and keep the log clear of other sessions 

2/ Remove all old 
         ~/.nx/[C|F|T].* 
directories 

3/ Set ( in node.conf ) 
        NX_LOG_LEVEL=6 
        NX_LOG_SECURE=1 
        NX_LOGFILE=/var/log/nxserver.log 
        SESSION_LOG_CLEAN=0 

4/ then run 
        sudo chmod 777 /var/log/nxserver.log 
        echo " " >  /var/log/nxserver.log 
this will allow a touch more logging and clear the log 

5/ Connect your first session and wait for it to settle down 
then 

6/ Try a shadow session to your own first session 

7/ See how many new session directories you get in:- 

         ~/.nx/ 

8/ email me any authority and option files 
        from whatever is in ~/.nx/. . . 
and the 
        /var/log/nxserver.log 
file 

email me a tar of your 
        nxserver 
        nxacl  and 
        nxnode 
files. 

Hope you had a good bank hol. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nx.tgz
Type: application/x-compressed
Size: 9774 bytes
Desc: nx.tgz
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130529/47834962/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nxserver.tgz
Type: application/x-compressed
Size: 9499 bytes
Desc: nxserver.tgz
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130529/47834962/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nxserver.log
Type: application/octet-stream
Size: 70991 bytes
Desc: nxserver.log
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130529/47834962/attachment.obj>