A reboot occurred.

[sehi1239]

Suddenly with esxi5.5.0 build-2456374 Update2 (HP customization)

A reboot occurred.

I saw all the logs, but only after startup.

Is there a problem with this version that suddenly restarts?

[Scott Vessey]

Moderator: Moved to ESXi

[b.w]

an esxi never restarts by itself.

psod or power lost ?

when the logs showing only entries after reboot -> are you booting from usb/sd? in this case you nedd to configure an external syslog server because logs are never written to sd/usb. without syslog server you never find the reason for the reboot

[sehi1239]

Thank you for your reply.

Since esxi is installed in hdd, syslog etc. are saved and written. A log indicating the restart is also included.

Because I cannot identify the cause, I want to know the contents of the update after esxi5.5.0 build-2456374 Update2 at the following URL

Do you know anyone?

https://kb.vmware.com/s/article/2143832?lang=en

[sehi1239]

I'm sorry, what is a moderator?

[Scott Vessey]

I'm sorry, what is a moderator?

You posted this in the wrong forum area, I moved it to the ESXi area in my capacity as a forum moderator.

[Nishant Panchal]

is it a reoccurring issue ?, check the esxtop and if you have a valid support contract i would suggest contact VMware support to review the logs.

[sehi1239]

Although it has not been repeated, since there are nearly 10 esxis and there are currently no support contracts and it takes a long time to investigate, we are considering contracts including vcenter, but first the cost merit is boss I'm thinking about collecting information and verifying the vcenter to explain it.

[KocPawel]

Take a look into log files:

/var/run/log.

hostd.log	Logs all hostd service operations
vpxa.log	Logs interactions between the host vpxa agent and the vpxd service on vCenter Server
fdm.log	Logs related to vSphere HA clusters

Check entries from time when restart occurred or paste here files, maybe someone will find something interesting.

Leave only entries from date when restart occurred.

Remember that vSphere 5.5 is end of life. Think about upgrade to newer versions.

[sehi1239]

Thank you for your reply.

The hostd.log has exceeded the applicable time including the compressed file, so it could not be confirmed. HA and vcenter did not have logs because they have no function.

[NathanosBlightc]

You should give more detail information such as physical server vendor and model (You must also check the HCL for integration of your server with ESXi 5.5)

Also, you need to check the /var/log/vmksummary.log file carefully, are you sure there is no related log information?!

[sehi1239]

bootstop; Before hosthass booted, just the same heartbeet log runs every hour. .

Personally, I think that the automatic optimization of storage resources running at the same time is suspicious. I tried it for the first time, but I have heard from you what you are asking for support.