[FreeNX-kNX] freeNX periodic SSL problem

[chris at ccburton.com]

freenx-knx-bounces at kde.org wrote on 18/05/2012 21:29:33:

Hi,

I am using nomachine's NX client v3.5.0 (windows) to connect to freenx 
0.7.3-7.el5 (centOS 5).
Every now and then. reconnecting to suspended sessions fails and I am 
forced to kill the session and start a new one. Here's the error I get:
. . . intermittent . . . 

[SNIP]

Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- 
-------------- ----------- ------------------------------
1007 unix-kde 060CF4E4561C494760E76E483405266D -RD--PSA 24 1674x997 
Running vgate3

This session is of "Status" Running, not suspended.

When you see this issue you are reporting,
have you "disconnected" manually, are you purposefully re-connecting to a 
running session or did your session just disconnect without user 
intervantion ??

1013 unix-kde BCAA296613CB5ECC7AC27C80D41D8DF2 -RD--PSA 16 1274x747 N/A 
vgate3
NX> 148 Server capacity: not reached for user: XXXX
NX> 105 restoresession --link="adsl" --backingstore="1" --encryption="1" 
--cache="128M" --images="512M" --shmem="1" --shpix="1" --strict="0" 
--composite="1" --media="0" --session="vgate3" --type="unix-kde" 
--geometry="1674x997" --client="winnt" --keyboard="pc102/en_US" 
--id="060CF4E4561C494760E76E483405266D" --resize="1" 

NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: not 
detected)
NX> 700 Session id: XXXX.com-1007-060CF4E4561C494760E76E483405266D
NX> 705 Session display: 1007
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 3d47c0c03c0f3fca2b1ec0d03a3c1fa3
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 3d47c0c03c0f3fca2b1ec0d03a3c1fa3
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1

Not sure why you highlight this.
It just means an encrypted link is selected (--encryption="1")

NX> 1004 Error: Session did not start.

nxnode didn't start correctly

NX> 596 Session resume failed.

Something went wrong . . . (unquote)

NX> 999 Bye
NX> 280 Exiting on signal: 15

Any idea how to fix this?

. . . not for an intermittent, with this much info.

Try waiting 5 mins & re-connecting a few times before giving up.

If that doen't work look at the contents of the session file
e.g.

 cat /var/lib/nxserver/db/running/sessionId{
060CF4E4561C494760E76E483405266D}

and
what's still running for user "XXXX"
e.g.
 ps -ef | egrep "^XXXX.*nx[a-z]{3,}" 

as a start . . . . 

also look at  nxserver.log where the disconnection took place, if it 
wasn't a user disconnect . . .

If you run "top", is any process running away with the CPU ??


Regards,
Siamak Shafiei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20120521/25b6ef63/attachment.html>