I'm having an odd problem where FreeSSHD doesn't start on boot about one in ten times.
I'm using it on Amazon EC2 instances actually, since there's a bug in Amazon's version of Xen which makes it impossible to use cygwin/openssh on their 64-bit instances.
So if I take one image of Windows Server 2008 Data Center with FreeSSHD installed and set to run automatically as a service, and spin up 40 instances, FreeSSHd doesn't start on around 4 of them. The service isn't started and there's nothing in the sshd log file.
In the Event Log I see:
A timeout was reached (30000 milliseconds) while waiting for the FreeSSHDService service to connect. The FreeSSHDService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
But there's nothing else wrong, it seems to just be intermittent. If I remote desktop in and start the service manually later, it runs fine.
Any tips here on how to mitigate this? I'm trying to automate provisioning of these systems, so I really need sshd to start reliably without manual intervention.
FreeSSHD isn't really maintained any more, so I suspect I need a more generic Windows answer to this. Increase the timeout? Is there a way to get it to try again?