[FreeNX-kNX] FreeNX CentOS 1004 Error: NX Agent exited with exit status 1

[Chris]

freenx-knx-bounces at kde.org wrote on 31/07/2013 06:48:30:

[SNIP]
> 
> The log shows this:
> 
> server_nxnode_echo: NX> 1004 Error: NX Agent exited with exit status
> 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and 
> investigate "/home/user/.nx/F-C-vt-1000-
> C3AD0301B4AC7A75961E2BA00CBC8E02/session". You might also want to 
> try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic 
> functionality. Session log follows:
> session_close C3AD0301B4AC7A75961E2BA00CBC8E02
> server_nxnode_echo: NX> 1006 Session status: closed
> NX> 1001 Bye.
> server_nxnode_echo: NX> 1001 Bye.
> 
> So, then I try:
> 
> [root at vt nx]# cd /home/user/.nx/F-C-vt-1000-
> C3AD0301B4AC7A75961E2BA00CBC8E02/session
> -bash: cd: /home/user/.nx/F-C-vt-1000-
> C3AD0301B4AC7A75961E2BA00CBC8E02/session: No such file or directory


It's (usually) a "race" caused by nxagent not opening within the
timeout  due to a delay loading libraries when first executed.

It doesn't get as far as creating the session directory hence :-
        "No such file or directory"

If it occurs, you mayn expect this to happen just the first few times
( say 4 or 5 ) you try to connect after you boot up or try to connect
to  FreeNX after not running it for some time
( i.e. nxagent is no longer in memory/swap )



> 
> Guess I can't really investigate it.  But again, chown -R nx:root 
> /var/lib/nxserver/db and chmod -R 775 nx:root /var/lib/nxserver/db 
> fixes it.  I have no idea why this is.

A coincidence.

Notice the "owner:group" and "mode/permissions" aren't changed . . .


If it becomes annoying add the line
        sleep 4
to
         /usr/bin/nxnode
 at line 300 i.e.just before

        echo "Xft.dpi: 96" | DISPLAY= . . .

It's asynchronous, so you won't see the 4 second delay.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130731/cf131c56/attachment.html>