Hello, Sometimes the reserved VM boots up and the Cygwin service fails to start during post_load and the management node gives up after trying for 1800 seconds resulting in a failed reservation.
I logged into the VM and found that Cygwin failed to start with error message in update_cygwin.log The CYGWIN sshd service could not be started. A system error has occurred. System error 1067 has occurred. The process terminated unexpectedly. Error level: 2 If I manually start the service it starts just fine. I checked that time that the VM received IP's from the DHCP server and it was about 1 minute before the update_cygwin script ran, so the VM had network connectivity before the service was attempting start (I am not sure if sshd will crash if network connectivity is not available). The following are the software version details: Cygwin: 1.7.25 (0.270/5/3) CYGWIN_NT-6.1-WOW64 OpenSSH (on VM): 6.4 VCL: 2.2.1 OS (VM): Windows 7 SP1 (64-Bit) The Cygwin sshd service has the following options set: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sshd\Parameters\Environment\CYGWIN ntsec nodosfilewarning Would it help to have Cygwin sshd service recovery options set so it restarts the service after First and Second failure? Would this interfere with the way the post_load scripts are setup? Has anyone seen this behavior? Any suggestions? Thanks. Junaid Ali
