Stan J
asked on
ESXi Core Dump
We have an ESXi 6.0 server that had a core dump this morning. Screen attached. Not sure what caused it yet..
The system is not booted.
We did not pre-configure an area for the core dump or enable anything to my knowledge
can i boot it up and pull logs by following the below link?
https://kb.vmware.com/s/article/1002769
IMG_0026.jpg
The system is not booted.
We did not pre-configure an area for the core dump or enable anything to my knowledge
can i boot it up and pull logs by following the below link?
https://kb.vmware.com/s/article/1002769
IMG_0026.jpg
ASKER
yes,,,only VMware can decipher it.,
if i recall, core data is saved until the next crash...
I can update firmware and also upgrade the host to the latest 6.0 version
not sure it just happened,,,i have to boot it up,,,,,
if i recall, core data is saved until the next crash...
I can update firmware and also upgrade the host to the latest 6.0 version
not sure it just happened,,,i have to boot it up,,,,,
The "trick" is if it can be reproduced, or happens all the time!
ASKER
yes,,,i will check and report back
Hello,
Similarly, I recommend you do a review at the hardware level on your server. To rule out a hardware failure.
Do you have support with your physical hardware provider? What servers do you use?
Greetings.
Similarly, I recommend you do a review at the hardware level on your server. To rule out a hardware failure.
Do you have support with your physical hardware provider? What servers do you use?
Greetings.
ASKER
We do not have VMware Support . This is a test and eval server.
System was rebooted yesterday at about 5 PM.
So far it is staying up.
I puled over the ESXi logs to a PC and can check them, although not sure how much info they will show pertaining to the crash.
System was rebooted yesterday at about 5 PM.
So far it is staying up.
I puled over the ESXi logs to a PC and can check them, although not sure how much info they will show pertaining to the crash.
Hello
consider. Please let us know if there is any strange behavior.
It also validates if there are alarms at the hardware level on the server.
you can share the printer of the registry here, to see them.
regards..
consider. Please let us know if there is any strange behavior.
It also validates if there are alarms at the hardware level on the server.
you can share the printer of the registry here, to see them.
regards..
ASKER
The server has not experienced any further issues. The logs did not show anything that indicated a shutdown.,
It may have been a one off event .
At this point, we are monitoring the server.
It may have been a one off event .
At this point, we are monitoring the server.
np
ASKER
So far, no more core dumps. It may have been a one off event,,,,
We will continue to monitor ....hope for the best!
We will continue to monitor ....hope for the best!
Please select a solution and close.
ASKER
still no change, so we can assume it was a one off event,,,,
hopefully... unless you can reproduce difficult to come to a conclusion.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Another purple screen event on the same serve,,
I pulled the below info from the core dump.....vrli-1 is our vRelaize Log Insight VM.
I don't recall if i saved the last core dump to check if a similar issues occurred ,,,
2018-10-29T04:30:16.438Z cpu20:321501) [45m [33;1mVMware ESXi 6.0.0 [Releasebuild-5572656 x86_64] [0m
#PF Exception 14 in world 321501:vmm1:vrli-1 IP 0x41802d8c5a2d addr 0x8
I pulled the below info from the core dump.....vrli-1 is our vRelaize Log Insight VM.
I don't recall if i saved the last core dump to check if a similar issues occurred ,,,
2018-10-29T04:30:16.438Z cpu20:321501) [45m [33;1mVMware ESXi 6.0.0 [Releasebuild-5572656 x86_64] [0m
#PF Exception 14 in world 321501:vmm1:vrli-1 IP 0x41802d8c5a2d addr 0x8
Not sure what you are going to do with it, best escalate to VMware Support, unless you are a specialist in this area.
PSOD are usually caused by:-
1. faulty hardware
2. faulty drivers
3. E1000/VMXNET3 bug
4. Bug in the Kernel
Update firmware and ESXi build version on the host.
Can you reproduce the crash ?