Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - VMware
cancel
Showing results for 
Search instead for 
Did you mean: 

ESXI 5.1 CRASH

Digfut
Occasional Visitor

ESXI 5.1 CRASH

Hello,

 

This is my first post in this forum, sorry if my english is not very good.

 

I have a ESXI 5.1 server (HP SE316M1/DL 160 G6) with 3 virtual machines, it has been working perfectly for more than a month. Server has 16GB RAM, 14GB for the machines and 2 GB left for the host.

 

Since last Friday I got 3 issues where virtual machines where unresponsive (although they appear as running on host), host was working and I was able to manage it through SSH and client.

 

After a reboot all is running correctly.

 

This has happened 3 times in last 4 days.

 

No hardware issues are found in ESXi report.

 

No RAID controller or drives issues found in hpacucli report (my controller is HP Smart Array P410).

 

I checked vmkwarning.log and found these lines at the time of last incident:

 

2015-03-31T01:20:34.165Z cpu0:4588)WARNING: LinuxSignal: 761: ignored unexpected signal flags 0x2 (sig 17)
2015-03-31T01:20:39.428Z cpu14:4534)WARNING: Team.etherswitch: TeamES_Activate:309:Failed to initialize beaconing on portset 'pps': Not implemented.
2015-03-31T01:20:47.329Z cpu12:4534)WARNING: Uplink: 3075: releasing cap 0x0!
2015-03-31T01:20:47.329Z cpu12:4534)WARNING: Uplink: 3075: releasing cap 0x0!
2015-03-31T01:20:47.329Z cpu12:4534)WARNING: Uplink: 3075: releasing cap 0x0!
2015-03-31T01:20:47.329Z cpu12:4534)WARNING: Uplink: 3075: releasing cap 0x0!
2015-03-31T01:20:47.473Z cpu12:4723)WARNING: LinuxSignal: 761: ignored unexpected signal flags 0x2 (sig 17)
2015-03-31T01:21:28.226Z cpu9:5860)WARNING: UserTeletype: 1639: Unknown cmd 0x5409 (data 0x1) for slave
2015-03-31T01:21:29.948Z cpu13:5876)WARNING: MemSched: 6105: Psharing is disabled but balooning is not.

 

What would explain that host works perfectly and all 3 machines stopped responding at same time? they appear as running on host panel. If it was a hardware issue (memory, processor, disk...) then host would hangs too, right?.

 

Can you shed any light on this?, this is a production server so I´m very worried.

Regards.

2 REPLIES

Re: ESXI 5.1 CRASH

Right.If it was a hardware issue (memory, processor, disk...) then host would hangs too.Did you check the VM guest OS event logs?

Server-Support
Super Advisor

Re: ESXI 5.1 CRASH

OK, how about try to apply the latest firmware from HP SPP 2015.06 and then update the ESXi 5.1 to the latest Update 3 ?

 

I've done this ti rectify the PSoD on my HP servers most of the time.