Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnecting to session hangs with "Session didn't become ready in time" message #73

Open
GoogleCodeExporter opened this issue Feb 1, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Disconnect from session
2. Try to reconnect to session

What is the expected output? What do you see instead?

The expected output is a successful connection with a window containing my 
desktop.  Instead the client says "Session didn't become ready in time" and 
fails to connect.

What version of the product are you using? On what operating system?

The client is version 3.4.0-10 of the windows client.  The server is on RHEL6 
with nx rpm 3.3.0-38.fc12 installed, and the trunk version of neatx (0.1-1.el6) 
installed.

Please provide any additional information below.

I do not think this is like the other "Session didn't become ready in time" 
message because the nxagent is correctly found, or I would not be able to start 
any session.

These are the details as displayed in the client:
NX> 203 NXSSH running with pid: 13172
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.1.83 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 3.3.0 - GPL
NX> 105 Hello nxclient - version 3.3.0
NX> 134 Accepted protocol: 3.3.0
NX> 105 Set SHELL_MODE: SHELL
NX> 105 Set AUTH_MODE: PASSWORD
NX> 105 Login
NX> 101 User: afoglia
NX> 102 Password: **********
NX> 103 Welcome to: wsrs-dev.princeton.com user: afoglia
NX> 105 Listsession --user="afoglia" --status="suspended,running" 
--geometry="1280x800x32+render" --type="unix-gnome"
NX> 127 Session list of user 'afoglia':
Display Type             Session ID                       Options  Depth Screen 
        Status      Session Name
------- ---------------- -------------------------------- -------- ----- 
-------------- ----------- ------------------------------
815     unix-gnome       AC7418E24CF3104C79939F08EA802B37 FRD--PSA    24 
1274x747       Suspended   wsrs-dev

NX> 148 Server capacity: not reached for user: afoglia
NX> 105 Restoresession  --link="adsl" --backingstore="1" --encryption="1" 
--cache="16m" --images="64m" --shmem="1" --shpix="1" --strict="0" 
--composite="1" --media="0" --session="wsrs-dev" --type="unix-gnome" 
--geometry="1274x747" --client="winnt" --keyboard="pc105/en_us" 
--id="ac7418e24cf3104c79939f08ea802b37" --resize="1"
NX> 500 Session didn't become ready in time
NX> 999 Bye.
NX> 280 Exiting on signal: 15



Original issue reported on code.google.com by afog...@gmail.com on 6 May 2011 at 7:20

@GoogleCodeExporter
Copy link
Author

Had a similar problem, if you disconnect the session using the "nx session 
administrator" instead of just closing the window, do you still have the same 
behavior? 

Original comment by averylon...@gmail.com on 16 Aug 2011 at 2:05

@GoogleCodeExporter
Copy link
Author

When I have had this happen, using NX Client under XP, I notice that there is 
an "NXSSh" process still in my task manager list. Killing it permits connecting 
again.

Original comment by krazyka...@googlemail.com on 20 Sep 2011 at 4:34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant