These are the logs just before it went down not sure though what they mean any help please?
May 04 19:52:52.582: vmx| USBGL: Failed to read arbitrator data, pipe 46: Success (110)
May 04 19:52:52.583: vmx| USBGA Error on arbitrator header read: Broken pipe (110)
May 04 19:52:53.659: vmx| VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF
May 04 19:52:53.660: vmx| SOCKET 1 (110) recv detected client closed connection
May 04 19:52:53.660: vmx| Vix: [11865 mainDispatch.c:2472]: VMAutomation: Connection Error (4) on connection 0.
May 04 19:52:53.660: vmx| Redirecting stdin/stdout/stderr to /dev/null.
May 04 19:52:53.660+0.855: vmx| Caught signal 15 -- tid 11865 (eip 0x52c29062)
Kind Regards
Welcome to the Communities.
Could you please add some more details about the situation, your server platform, version, what was happening at the time etc etc.
VMware ESXi 4.1.0 260247
Running a single host with Symantec Brightmail Gateway 9
We are not sure what exactly happened in the server room other than that a different server was having its ram upgraded.
The ESXi server was down and after investigating the logs I came accross the segment posted above which I am pretty sure is related but not sure what it refers to or whether it explains what happened.
Just to be sure. Host would refer to the physical ESXi server and the Brightmail virtual machine would be the guest. In your situation the Host went down or the Guest?
sorry yeah, the host went down therefore both went down.
The vmware.log file won't necessarily be useful if the host took down the guest. ESXi writes host logs to a RAM disk so logs are lost on a reboot.
If you haven't I would point the ESXi host logs to a datastore. Use the vSphere client Configuration tab -> Advanced -> Software -> Syslog settings.
Do we assume that the Host and Guests are running?