sshd Cygwin service won't start properly

[oboeguy]

I'm trying to run it so I can use the "Unison" file synch tool but I can't get the sshd service to run properly. It hangs while starting-up and I have to kill the cygrunsrv process. Ideas?

 

[mattsaccount]

I use unison regularly using exactly the technique you're describing, and it works fine. Maybe try reinstalling?

 

[oboeguy]

Yeah I'm updating my cygwin installation because it works on my work computer (but I can't ssh in because of the firewall, doh). My cygwin installation is probably more than a year old. Almost done, will report back...

Thanks for the encouragement. 🙂

 

[oboeguy]

Boo! Still not working. I'm asking at work to get a port opened... cross your fingers!

 

[oboeguy]

Bwuahahaha! They opened a port for me, I'm good to go. I still would like to fix sshd on my home machine, though... further suggestions?

 

[AlucardX]

i'm not sure what your'e doing, but i use openssh for windows xp on my home box, so i can shtunnel from work. i have no problems with sshd at home, but it does take about 1 whole minute for the service to completely start.

i have a .bat file in my startup folder with: net start openssh

 

[n0cmonkey]

Anything in the logs?

 

[oboeguy]

Question: Where are the logs? I'll gladly check.

Next... Unison won't let me use SSH with a non-standard port, at least not from the GUI. Now what? 🙁

 

[n0cmonkey]

They're in /var/logs or /var/adm on proper machines. Probably in event viewer in Windows though.

 

[oboeguy]

No love from any of those sources. The Event Viewer entry is useless and the other two have nothing related to sshd. 🙁

 

[n0cmonkey]

There is an event viewer entry for SSHd? If so, and it isn't just "sshd failed to start" or something, post it.

If not, kick whoever ported that stuff to Windows in the crotch. There needs to be logs for this sort of stuff.

 

[oboeguy]

<crotchkick>Nothing useful in Event Viewer</crotchkick>

The Service Control Manager event says the service couldn't start, and the sshd one itself says something about not having access to a log message.

 

[n0cmonkey]

Originally posted by: oboeguy
<crotchkick>Nothing useful in Event Viewer</crotchkick>

The Service Control Manager event says the service couldn't start, and the sshd one itself says something about not having access to a log message.

Hmmm, that could be a clue. If it's more specific, try to track down that possible permissions issue.

 

[oboeguy]

If this makes any sense...

Event Type: Error
Event Source: sshd
Event Category: None
Event ID: 0
Date: 10/21/2005
Time: 12:10:05 PM
User: NT AUTHORITY\SYSTEM
Computer: <my computer's name>
Description:
The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: sshd : PID 2000 : starting service `sshd' failed: execv: 255, error 255.

Makes no sense to me.

 

[oboeguy]

I figured out how to get Unison to use a different port in the GUI: do host😛ort#, easy enough. However, I now have to update cygwin on my work machine to get the right version of Unison going. Aaaaaaaagh! This Unison exercise was supposed to save me some headaches and it's instead become a quest of epic proportions! 😀

 

[n0cmonkey]

Originally posted by: oboeguy
If this makes any sense...

Event Type: Error
Event Source: sshd
Event Category: None
Event ID: 0
Date: 10/21/2005
Time: 12:10:05 PM
User: NT AUTHORITY\SYSTEM
Computer: <my computer's name>
Description:
The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: sshd : PID 2000 : starting service `sshd' failed: execv: 255, error 255.

Makes no sense to me.

Makes no sense to me either, but google might help. *scamper*

 

[n0cmonkey]

This might be helpful...
This too.

 

[CTho9305]

So, manually running "net start sshd" does not work? (Sorry if this is what you're doing - it wasn't clear to me whether you had the service on "Automatic" or were doing it manually).

 

[oboeguy]

Originally posted by: CTho9305
So, manually running "net start sshd" does not work? (Sorry if this is what you're doing - it wasn't clear to me whether you had the service on "Automatic" or were doing it manually).

I've tried it every which way.

BTW, after updating cygwin on the work machine, sshd no longer works there either. This is getting ridiculous!

 

[Red and black]

cygwin sshd works fine for me.

 

[oboeguy]

If anyone has more suggestions, I'd appreciate it. Yes, I'm still trying. 😀

I'm going to synch-up to a Linux box I can log into (and have to anyway to run some code on it). I know sshd is running there!

 

[kamper]

Originally posted by: oboeguy
If this makes any sense...

Event Type: Error
Event Source: sshd
Event Category: None
Event ID: 0
Date: 10/21/2005
Time: 12:10:05 PM
User: NT AUTHORITY\SYSTEM
Computer: <my computer's name>
Description:
The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: sshd : PID 2000 : starting service `sshd' failed: execv: 255, error 255.

Makes no sense to me.

I did a little bit of windows event logging a few months ago at work and I think I understand that message. In order to provide a proper log, you first have to install your error messages along with their codes in a special dll (cygwin would ideally have done this for you). Then, when logging, you specify the error code and the appropriate message gets displayed. The message is a format string so you can insert arbitrary info into the message and the simplest case would be to have one message with a %s so that you can just insert any string from the app as your message.

Anyways, I'm rambling. The long and short of it is that windows event logging is a pita for stuff not developed with windows centric tools and while the error message might have been useful, it has simply been dropped because something wasn't set up quite right.