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