Try to change on nxnode where:<br> if stringinstring "Session: Display failure detected at" "$line"<br> then<br> echo "NX> 596 Error: Session $1 failed. Reason was: $line"<br>
if [ "$1" = "restore" ]<br> then<br> kill $NODE_TAIL_PID<br> break<br> fi<br>
fi<br><br>to:<br> if stringinstring "Session: Display failure detected at" "$line"<br> then<br> echo "NX> 596 Error: Session $1 failed. Reason was: $line"<br>
if [ "$NODE_SUSPEND_STATUS" != "Suspending" ]<br> then<br> if [ "$1" = "restore" ]<br> then<br>
kill $NODE_TAIL_PID<br> break<br> fi<br> fi<br> fi<br><br><br><div class="gmail_quote">
On Sat, Jan 24, 2009 at 3:20 AM, Mario Becroft <span dir="ltr"><<a href="mailto:mb@gem.win.co.nz">mb@gem.win.co.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Here is some more info. I think someone who understands how the<br>
nxserver/nxnode interaction is supposed to function can figure out the<br>
problem from the following debug output. I found that part of the reason<br>
for the confusing nxnode output is because there are in fact two<br>
nxnode's running. You can distinguish between them in the debug output<br>
below by looking at the pid. The one that emits the "1001 Bye" with no<br>
delimiter is the one invoked with "--slave". The other one was invoked<br>
with "--startsession".<br>
<br>
The NNNN lines are emitted by nxnode, and trace when it is starts, stops<br>
and emits messages about the session state.<br>
<br>
The other lines are from nxserver. They have my added instrumentation at<br>
the beginning of the line showing the process name, pid and time. The<br>
ones with AAAA are my additional instrumentation. The "AAAA cmd=..."<br>
line prints all commands received by the loop inside<br>
server_nxnode_start_wait(). It is interesting to note that in the<br>
failure case, it never sees the "suspending" and "suspended" messages.<br>
<br>
The main difference is that when the failure occurs,<br>
server_nxnode_start_wait() reads EOF and the session gets closed. The<br>
message "AAAA method is su, done nxnode_login" is where nxnode_login<br>
invoking su has returned inside server_nxnode_start. When you suspend<br>
the session correctly, this does not happen.<br>
<br>
Please help! I will be doing more work on this tomorrow.<br>
<br>
Output when suspending the session in the proper way, so that there is<br>
no fault:<br>
<div class="Ih2E3d"><br>
--8<---------------cut here---------------start------------->8---<br>
</div>NNNN(/usr/NX/bin/nxnode)(12567)(Sat Jan 24 18:07:30 NZDT 2009) saying that session status is suspending<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:30 NZDT 2009) nxnode_reader: NX> 1009 Session status: suspending<br>
<div class="Ih2E3d">NX> 1009 Session status: suspending<br>
</div>(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:30 NZDT 2009) AAAA cmd=(NX> 1009 Session status: suspending)<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:30 NZDT 2009) session_status 89E5FFF02E9C82347C7085AD85DF24DC Suspending<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:30 NZDT 2009) server_nxnode_echo: NX> 1009 Session status: suspending<br>
NNNN(/usr/NX/bin/nxnode)(12567)(Sat Jan 24 18:07:31 NZDT 2009) saying that session status is suspended<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) Info: Closing connection to slave with pid 12188.<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) nxnode_reader: NX> 1005 Session status: suspended<br>
<div class="Ih2E3d">NX> 1005 Session status: suspended<br>
</div>NNNN(/usr/NX/bin/nxnode)(12200)(Sat Jan 24 18:07:31 NZDT 2009) stopping, delim is ()<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) AAAA cmd=(NX> 1005 Session status: suspended)<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) nxnode_reader: 1001 Bye.<br>
1001 Bye.<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) session_suspend 89E5FFF02E9C82347C7085AD85DF24DC<br>
(/usr/NX/bin/nxserver)(12050)(Sat Jan 24 18:07:31 NZDT 2009) server_nxnode_echo: NX> 1005 Session status: suspended<br>
<div class="Ih2E3d">--8<---------------cut here---------------end--------------->8---<br>
<br>
</div>Output when killing nxssh on the client, resulting in nxagent<br>
automatically suspending the session, but causing the fault condition:<br>
<div class="Ih2E3d"><br>
--8<---------------cut here---------------start------------->8---<br>
</div>(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) Info: Closing connection to slave with pid 10009.<br>
NNNN(/usr/NX/bin/nxnode)(10021)(Sat Jan 24 17:43:48 NZDT 2009) stopping, delim is ()<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) nxnode_reader: 1001 Bye.<br>
1001 Bye.<br>
NNNN(/usr/NX/bin/nxnode)(10416)(Sat Jan 24 17:43:48 NZDT 2009) saying that session status is suspending<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) AAAA cmd=(1001 Bye.)<br>
NNNN(/usr/NX/bin/nxnode)(10416)(Sat Jan 24 17:43:48 NZDT 2009) saying that session status is suspended<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) nxnode_reader: NX> 596 Error: Session failed. Reason was: Session: Display failure detected at 'Sat Jan 24 17:43:48 2009'.<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) nxnode_reader: NX> 1009 Session status: suspending<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) AAAA method is su, done nxnode_login<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) AAAA end of server_nxnode_start<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) AAAA server_nxnode_start_wait about to close session<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) AAAA nxnode_login_stop_slave call 3<br>
(/usr/NX/bin/nxserver)(9867)(Sat Jan 24 17:43:48 NZDT 2009) Info: Closing connection to slave with pid 10009.<br>
<div class="Ih2E3d">--8<---------------cut here---------------end--------------->8---<br>
<br>
</div><div><div></div><div class="Wj3C7c">--<br>
Mario Becroft <<a href="mailto:mb@gem.win.co.nz">mb@gem.win.co.nz</a>><br>
________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br>
</div></div></blockquote></div><br>