[01] SSH Server Technical Support


These discussion groups are closed due to spam that could not be controlled within abilities of this support system.

For any technical or licensing inquiries about Bitvise SSH Server, please open a new support case.

Any information you find herein is outdated, and not applicable to our latest software versions.

Unable to create child process

When trying to ssh2 to WinSSHd (latest version), I got this error on the client's ssh display: Unable to create child process. The connection was immediately cut off.

The same error occurs when I connect from localhost or from anywhere.

Here are the logs:

[040] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
Logon attempt 1 for user name paultwang succeeded. Logon attempt method: 'password'.

[049] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
Session server 3: Session server created.

[055] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
Session server 3: Executing command 'toterm cmd:' in working directory 'C:\Documents and Settings\paultwang'.

[139] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
Session server 3: Process terminated with exit code 1, reporting exit code to remote

[093] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
The client disconnected without sending a disconnect message.

[135] WinSSHD 3.26: ProcessTerminator for 'toterm cmd:', session ID 1003:
No process handle supplied to Terminate(), terminating job.

[050] WinSSHD 3.26: Session thread 1003 for user paultwang from 127.0.0.1 port 4411:
Session server 3: Closing session server.

 
paultwang
Saturday, July 17, 2004
 
 
Hello Paul,

check your settings for Terminal Shell. Apparently your current settings are to use none - "" - and this is a program which cannot be executed. :) If you have account-specific settings for the paultwang account, make sure that the Terminal Shell column is set to * (a single asterisk character). This will inherit the Terminal Shell setting from the template, where I assume it is set correctly. The same applies to the Initial Directory and SFTP Root Dir columns.

This may be related to misleading behavior of the GUI configuration utility in version 3.25 which was subsequently fixed in 3.26. This problem would appear if you added configuration settings for the paultwang account with the version 3.25 GUI, before upgrading to 3.26. If you never used 3.25, or if you added the paultwang account with a version of the GUI settings utility other than 3.25, let me know - according to my knowledge this bug should have been fixed in 3.26.

Best regards,

denis
denis bider
Saturday, July 17, 2004
 
 
I deleted the accounts and recreated them. It works now. I imported the configuration from another computer. I guess that caused the problem.
paultwang
Saturday, July 17, 2004
 
 
The problem in the 3.25 Settings utility was that when an account entry was created, the string fields were initialized to an empty string ("") instead of the asterisk ("*"), so the string settings weren't being inherited from the template settings. In 3.26 this was fixed and an asterisk is now the default value of these settings. This is why recreating the accounts with the 3.26 Settings utility fixed the problem.
denis bider
Saturday, July 17, 2004
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz