ESXi Reboot Reason

[redfoxw85]

Hi, there's a ESXi 6.5.0 (Build 4564106) running on a LENOVO x3250 M6 at a remote site. This host has recently rebooted and I'm trying to figure out if it was a power failure, manual power cycle or if an update cuased the reboot.

Following are what I gathered from logs, not sure if these are enough, appreciate if someone can assist by looking at these logs or if I need to be looking somewhere else.

 

From syslog.log

2023-10-11T02:45:01Z crond[66331]: crond: USER root pid 716657 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2023-10-11T02:45:01Z syslog[716660]: starting hostd probing.
2023-10-11T02:50:01Z crond[66331]: crond: USER root pid 716676 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2023-10-11T02:50:01Z syslog[716679]: starting hostd probing.
2023-10-11T02:55:01Z crond[66331]: crond: USER root pid 716696 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2023-10-11T02:55:01Z syslog[716699]: starting hostd probing.
2023-10-11T03:02:15Z watchdog-vobd: [65863] Begin '/usr/lib/vmware/vob/bin/vobd', min-uptime = 60, max-quick-failures = 5, max-total-failures = 1000000, bg_pid_file = '', reboot-flag = '0'
2023-10-11T03:02:15Z watchdog-vobd: Executing '/usr/lib/vmware/vob/bin/vobd'
2023-10-11T03:02:15Z jumpstart[65848]: Launching Executor
2023-10-11T03:02:15Z jumpstart[65848]: Setting up Executor - Reset Requested
2023-10-11T03:02:15Z jumpstart[65848]: ignoring plugin 'vsan-upgrade' because version '2.0.0' has already been run.
2023-10-11T03:02:15Z jumpstart[65848]: executing start plugin: check-required-memory
2023-10-11T03:02:15Z jumpstart[65848]: executing start plugin: restore-configuration
2023-10-11T03:02:15Z jumpstart[65894]: restoring configuration
2023-10-11T03:02:15Z jumpstart[65894]: extracting from file /local.tgz
2023-10-11T03:02:15Z jumpstart[65894]: ConfigCheck: Running ipv6 option upgrade, redundantly
2023-10-11T03:02:15Z jumpstart[65894]: Util: tcpip4 IPv6 enabled
2023-10-11T03:02:15Z jumpstart[65848]: executing start plugin: vmkeventd
2023-10-11T03:02:15Z watchdog-vmkeventd: [65896] Begin '/usr/lib/vmware/vmkeventd/bin/vmkeventd', min-uptime = 10, max-quick-failures = 5, max-total-failures = 9999999, bg_pid_file = '', reboot-flag = '0'
2023-10-11T03:02:15Z watchdog-vmkeventd: Executing '/usr/lib/vmware/vmkeventd/bin/vmkeventd'
2023-10-11T03:02:15Z jumpstart[65848]: executing start plugin: vmkcrypto

 

vmksummary.log

up 69d1h49m20s, 1 VM; [[65853 vmsyslogd 13296kB] [66730 hostd-worker 35484kB] [676459 vmx 6055080kB]] [[65853 vmsyslogd 0%max] [66730 hostd-worker 0%max] [676459 vmx 0%max]]
up 69d2h49m20s, 1 VM; [[65853 vmsyslogd 13296kB] [66730 hostd-worker 35484kB] [676459 vmx 6057984kB]] [[65853 vmsyslogd 0%max] [66730 hostd-worker 0%max] [676459 vmx 0%max]]
up 69d3h49m20s, 1 VM; [[65853 vmsyslogd 13296kB] [66730 hostd-worker 35484kB] [676459 vmx 6057372kB]] [[65853 vmsyslogd 0%max] [66730 hostd-worker 0%max] [676459 vmx 0%max]]
0:00:00:04.377 cpu0:65536)WARNING: CacheSched: 246: The measured L2 cache miss cost 4 is not within the expected range, using 40 instead
0:00:00:04.510 cpu0:65536)WARNING: Serial: 274: logPort initialization failed
0:00:00:04.510 cpu0:65536)WARNING: Serial: 283: gdbPort initialization failed
0:00:00:04.510 cpu0:65536)WARNING: Serial: 300: shellPort initialization failed
0:00:00:04.510 cpu0:65536)WARNING: Serial: 317: consolePort initialization failed
2023-10-11T03:02:24.391Z cpu7:65929)WARNING: lsi_mr3: fusion_init:1420: To sync map
2023-10-11T03:02:27.478Z cpu7:65929)WARNING: rxRing->size = 1024
2023-10-11T03:02:27.577Z cpu7:65929)WARNING: rxRing->size = 1024
2023-10-11T03:02:27.613Z cpu7:65929)WARNING: xhci_pci_attach:208: xhci devid 0xa12f8086: Success
2023-10-11T03:02:28.191Z cpu7:65929)WARNING: vmw_ahci[00000017]: ProbeDevice:No device
2023-10-11T03:02:28.295Z cpu7:65929)WARNING: vmw_ahci[00000017]: ProbeDevice:No device
2023-10-11T03:02:28.399Z cpu7:65929)WARNING: vmw_ahci[00000017]: ProbeDevice:No device
2023-10-11T03:02:28.504Z cpu7:65929)WARNING: vmw_ahci[00000017]: ProbeDevice:No device
2023-10-11T03:02:28.609Z cpu7:65929)WARNING: vmw_ahci[00000017]: ProbeDevice:No device
2023-10-11T03:02:29.511Z cpu6:65875)WARNING: NetDVS: 681: portAlias is NULL
2023-10-11T03:02:41Z mark: storage-path-claim-completed
2023-10-11T03:02:39.763Z cpu2:66365)WARNING: FTCpt: 875: Using IPv6 address to start server listener
2023-10-11T03:02:52.316Z cpu4:66730)WARNING: PCI: 179: 0000:03:00.0: Bypassing non-ACS capable device in hierarchy
2023-10-11T03:02:52.316Z cpu4:66730)WARNING: PCI: 179: 0000:03:00.1: Bypassing non-ACS capable device in hierarchy
Host has booted

[denisglups]

Hello redfoxw85,

you could have a look into the following log:

/var/log/hostd.log

and search something like 

Hostd: [12:51:54.284 27D13B90 info ‘TaskManager’] Task Created : haTask-ha-host-vim.HostSystem.reboot-50

If you find anything in this logs, this will indicate, that it was an deliberate reboot. 

What you also could test is to execute this command to check if ESXi is configured to automatically reboot after a Purple Screen of Death (PSOD):

esxcfg-advcfg -g /Misc/BlueScreenTimeout

If the value listed is anything other than 0, then ESXi automatically reboots after the PSOD. If the output is 0, the system is configured to wait for you to manually restart the host.

Maybe this will help you to find the reason for the reboot.

BR

[redfoxw85]

Hi denisglups,

This's all hostd.log had.

2023-10-11T03:02:51.769Z Section for VMware ESX, pid=66730, version=6.5.0, build=4564106, option=Release

So I guess I can safely assume either the device was rebooted due to a power failure or someone manually power cycled it. Or else it could've been rebooted due to a PSOD.

Unfortunately I only have web access, I'll try to get ssh access and execute this command.

Thank you so much for your reply.