www.cendio.com
Bug 2833 - tlclient fails to detect stopped vsmserver on at least SLED10
: tlclient fails to detect stopped vsmserver on at least SLED10
Status: CLOSED FIXED
: ThinLinc
Client
: trunk
: PC Unknown
: P2 Normal
: 4.2.0
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-07-01 16:47 by
Modified: 2014-05-05 12:29 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From cendio 2008-07-01 16:47:19
On my SLED10 system, tlclient fails to detect that the SSH connection succeeded
but that vsmserver is not running. What happens is that "COMMAND_EXITSTATUS: 2"
is recieved before "THINLINC-LOGIN: ERROR". Like this:

SSH_PROMPT:Password:

CONNECTED
THINLINC-LOGIN: HELLO 2.1.0
COMMAND_EXITSTATUS: 2
THINLINC-LOGIN: ERROR: Socket error: (111, 'Connection refused')

For some reason, it works on Ossmans machine. Might be race. We should either
try to make sure that the remote SSH command writes all output before
COMMAND_EXITSTATUS is sent. Or, tlclient should verify that COMMAND_EXITSTATUS
is 0; not treat any value as success.
------- Comment #1 From cendio 2013-12-03 11:58:39 -------
We cleaned up this handling when we ported OpenSSH to Windows and we haven't
seen this problem lately. Closing bug.
------- Comment #2 From cendio 2014-05-05 12:29:35 -------
Works now. From tlclient.log:

2014-05-05T12:28:50: ssh[E]: NEXT AUTHMETHOD: none
2014-05-05T12:28:50: ssh[E]: AUTH FAILURE
2014-05-05T12:28:50: ssh[E]: NEXT AUTHMETHOD: keyboard-interactive
2014-05-05T12:28:50: ssh[E]: SSH_PROMPT:Password: 
2014-05-05T12:28:50: ssh[E]: AUTH SUCCESS
2014-05-05T12:28:50: ssh[E]: CONNECTED
2014-05-05T12:28:51: ssh[E]: THINLINC-LOGIN: HELLO 4.1.1post
2014-05-05T12:28:51: ssh[E]: THINLINC-LOGIN: ERROR: Socket error: [Errno 111]
Connection refused
2014-05-05T12:28:51: ssh[E]: 
2014-05-05T12:28:51: ssh[E]: COMMAND_EXITSTATUS: 2
2014-05-05T12:28:55: Log file ended