I can't tell from just the commands. They look normal. Were there any WARNING messages during the image process prior to the reboot?
What error message is reported when you try to ssh from the management node? (Connection timed out, etc) It may be helpful if you send the output from running "ssh -v <win_computer>". To troubleshoot, you'll need to login as root using the password which was redacted from the vcld.log output. Check the following: Is the Cygwin SSHD service running? If not, try to start it. If you get an error related to incorrect credentials then something went wrong when root's password was set early on in the image capture process. If SSHD is running, it could be a firewall problem. Try simply turning off the firewall temporarily on the Windows computer and try to ssh from the management node. If the firewall isn't the problem, something isn't configured correctly with the sshd service. While logged in as root, you can try running C:\cygwin\root\VCL\Scripts\update_cygwin.cmd. This gets run automatically when an image is loaded and configures sshd correctly and starts the service. If running this solves the problem, then you'll have to figure out which commands or changes made by this script fixed it. If possibly, it will be easier to troubleshoot if you take a snapshot of the computer before running this script so that you can revert to the broken state in order to narrow down the problem. -Andy On Tue, Apr 1, 2014 at 6:28 PM, Curtis <[email protected]> wrote: > On Tue, Apr 1, 2014 at 4:16 PM, Curtis <[email protected]> wrote: > > Hi All, > > > > We are having an issue with some of our images where when we try to > > create a new image from an existing image, everything goes ok until > > the part where the virtual machine is rebooted, and after it's > > rebooted sshd does not start up and the imaging process fails. > > > > Anyone have any thoughts? I'm fairly sure it has something to do with > > the various commands that are run on the image once an image creation > > process starts. > > Also, this gist has all the commands that are being run: > > https://gist.github.com/curtisgithub/6117a73b47e994d9be03 > > But I'm not much of a windows administrator -- does anyone see > anything unusual in that gist that might be causing issues? Perhaps > something with the root logon or password? > > > > > Thanks, > > Curtis. > > > > -- > > Twitter: @serverascode > > Blog: serverascode.com > > > > -- > Twitter: @serverascode > Blog: serverascode.com >
