Solved

ESXi 4: root cause "freeze", howto find in logging?

Posted on 2013-06-21
6
508 Views
Last Modified: 2013-06-24
Hi,

We had an issue with a "freezing" esxi 4. It was rebooted before I actually could see what happened but now I would like to find out (it is in maintenance mode). I roughly have an idea when it happened (yesterday evening).

What I do can see is that time is totally wrong (January 2013), but how can I find what actually went wrong (looked into the logfile with vi but that's a pain in the ass to find anything usefull, isn't there something more userfriendly?).
0
Comment
Question by:janhoedt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
6 Comments
 
LVL 121
ID: 39265350
With ESXi it will be difficult to find out after the event, when the server was restarted because the logs are not stored.

I would recommend setting up a Syslog Server or using vMA, to send the logs from the ESXi server to a remote logging server, so you will have all the logs the next time this occurs.

VMware KB: Enabling syslog on ESXi 3.5 and 4.x

VMware have just launched vCenter Log Insight, which is also a graphical Syslog server, based losely on Splunk!
http://www.vmware.com/products/datacenter-virtualization/vcenter-log-insight/overview.html

It's in Beta, but shows graphical syslog entries, which may be easier for you to diagnose. It's also FREE, easy to deploy via OVA/OVF appliance, and ready to run and collect syslog entries in 5 minutes.

But I would check hardware, memory, with memtest, re-seat any memory chips, check fans, heatsinks etc
0
 

Author Comment

by:janhoedt
ID: 39265511
Thanks hanccoccka, but logfiles ARE stored, since we moved the scratch-partition  to a LUN. So, I do have the logfiles. Please advise.
J.
0
 
LVL 121

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39271265
No mention in OP, you had the logs on LUN, syslog server is better. (SAN fails/LUN fails logging is lost!)

upload the log files here, in future, send logging to a syslog server, makes the logs easier to read.

are you using iSCSI, any changes to paths, or LUNs, datastores removed?
0
 

Author Closing Comment

by:janhoedt
ID: 39271622
Ok, thanks for the input. So bottomline is: there is no easy way to anaylyze logfiles BUT a syslog-server.
0

Featured Post

[Webinar] Learn How Hackers Steal Your Credentials

Do You Know How Hackers Steal Your Credentials? Join us and Skyport Systems to learn how hackers steal your credentials and why Active Directory must be secure to stop them. Thursday, July 13, 2017 10:00 A.M. PDT

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…
Suggested Courses

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question