[FreeNX-kNX] Shadow Session fails to attach

[chris at ccburton.com]

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 --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130528/d5d8cdac/attachment.html>