Hi VMware Guru's
One of our ESXi 5.1 rebooted automatically i need to investigate why reboot happened because of esxi crash, hardware failure or anybody intentionally rebooted. Please help me out.Below are logs
# cat /var/log/vmksummary.log | grep bootstop
2014-09-30T02:23:50Z bootstop: Host has booted
# esxcfg-advcfg -g /Misc/BlueSreenTimeout
Exception occured: Unable to find option BlueSreenTimeout
# cat /var/log/hostd.log | grep poweroff
2014-09-30T02:23:48.844Z [FF934D20 verbose 'Solo.VmwareCLI'] Command poweroff (p oweroff)
2014-09-30T02:23:48.844Z [FF934D20 error 'Solo.VmwareCLI'] Creating Command CLII nfo for poweroff (poweroff)
# cat /var/log/hostd.log | grep shutdown
2014-09-30T02:23:48.844Z [FF934D20 info 'Solo.VmwareCLI'] (vim.EsxCLI.system.shutdown) ha-cli-handler-system-shutdown created
2014-09-30T02:23:55.230Z [FF934D20 info 'TagExtractor'] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0xf674e58], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operations involving foundry
# cat /var/log/hostd.log | grep reboot
2014-09-30T02:23:48.844Z [FF934D20 verbose 'Solo.VmwareCLI'] Command reboot (reboot)
2014-09-30T02:23:48.844Z [FF934D20 error 'Solo.VmwareCLI'] Creating Command CLIInfo for reboot (reboot)
2014-09-30T02:23:55.230Z [FF934D20 info 'TagExtractor'] 8: Rule type=[N5Hostd6Common31MethodNameBasedTagExtractorRuleE:0xf674e58], id=rule[VMFoundryOpRule], tag=IsVMFoundryOp, regex=vim\.VirtualMachine\.(acquireMksTicket|clone|createSecondary|createSnapshot|customize|disableSecondary|enableSecondary|makePrimary|migrate|mountToolsInstaller|powerOff|powerOn|rebootGuest|reconfigure|reload|reloadFromPath|relocate|removeAllSnapshots|turnOffFaultTolerance|recommendHostsForSecondaryVm|rename|reset|resetGuestInformation|retrieveScreenshot|revertToCurrentSnapshot|revertToSnapshot|screenshot|setScreenResolution|shutdownGuest|standbyGuest|startRecording|startReplaying|stopRecording|stopReplaying|suspend|terminate|terminateFaultTolerantVM|unmountToolsInstaller|unregister|upgradeTools|upgradeVirtualHardware) - Identifies Virtual Machine operations involving foundry
Please let me know if you require more logs
Thanks in advance
Well the host didn't find a coredump at bootup so it wasn't a crash. Looks like someone powered it off by command line or a script.
Having the exact same issue, my server is rebooting every 4 hours roughly, this started yesterday out of the blue.
my logs look like the logs posted by OP.
anyone found the cause / solution yet ?
thanks in advance
As said above this looks like being script initiated, so check if some script is running on either CLI/ssh or PowerCLI.
If your host is connected to a UPS this might even be caused by a (nearly) dead battery inside the UPS.
