2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→Useful paths / logfiles: Updated "ESXi" with more info
(→Troubleshooting: Added "Snapshots") |
(→Useful paths / logfiles: Updated "ESXi" with more info) |
||
| Line 505: | Line 505: | ||
= Troubleshooting = | = Troubleshooting = | ||
== Useful paths / logfiles== | == Useful paths / logfiles== | ||
'''Timestamps in logfiles are in UTC !!!''' | |||
=== ESX === | === ESX === | ||
{|cellpadding="2" cellspacing="0" border="1" | {|cellpadding="2" cellspacing="0" border="1" | ||
|- | |- | ||
! Item | ! Item !! Path !! Comments | ||
|- | |- | ||
| Vmkernel logfile | | Vmkernel logfile || <code> /var/log/vmkernel </code> || Pretty much everything seems to be recorded here | ||
|- | |- | ||
| Vmkernel warnings | | Vmkernel warnings || <code> /var/log/vmkwarning </code> || Virtual machine warnings | ||
|- | |- | ||
| | | Host Daemon logfile || <code> /var/log/vmware/hostd.log </code> || Services log | ||
|- | |- | ||
| | | vCentre Agent logfile || <code> /var/log/vmware/vpx/vpxa.log </code> || vCentre agent | ||
|- | |- | ||
| | | Local VM files || <code> /vmfs/volumes/storage </code> || Storage name can vary, use TAB so shell selects available | ||
|- | |- | ||
| SAN VM files || <code> /vmfs/volumes/SAN </code> || | |||
|- | |||
| HA agent logs || <code> /opt/LGTOaam512/log/ </code> || Various logs of limited use | |||
|} | |} | ||
=== ESXi === | === ESXi === | ||
To view logfiles from an ESX'''i''' server, they need to be downloaded to your client machine 1st, and then viewed from there... | To view logfiles from an ESX'''i''' server, they need to be downloaded to your client machine 1st, and then viewed from there... | ||
# Using VI Client, go to '''File | Export | Export System Logs...''' | # Using VI Client, go to '''File | Export | Export System Logs...''' | ||
| Line 529: | Line 532: | ||
#* Untick ''Include information from vCenter Server and vSphere Client'', unless you additionally want this info | #* Untick ''Include information from vCenter Server and vSphere Client'', unless you additionally want this info | ||
# Once exported, uncompress the ESX's tgz file | # Once exported, uncompress the ESX's tgz file | ||
The files aren't exactly the same, see the <code> messages </code> log rather than <code> vmkernel </code>, for example | However, this is most easily achieved if you've got the PowerCLI installed, in which case see [[VI_Toolkit_(PowerShell)#ESXi_Logs]] | ||
The files aren't exactly the same as found in ESX, see the <code> messages </code> log rather than <code> vmkernel</code>, for example. Most problematic is the lack of history. If you have to reboot your ESX (say, because it locked up) there will be no logs prior to the most recent boot. In theory they'll get written to a dump file if a crash is detected, but I've never found them, so assume they're only generated during a semi-graceful software crash. | |||
{|cellpadding="2" cellspacing="0" border="1" | |||
|- | |||
! Name !! PowerCLI Key !! Diagnostic Dump Path !! Comments | |||
|- | |||
| Syslog || <code> messages </code> || <code> /var/log/messages </code> || Equivalent to ESX ''hostd'' and ''vmkernel'' logs combined | |||
|- | |||
| Host Daemon || <code> hostd </code> || <code> /var/log/vmware/hostd.log </code> || Equivalent to ESX ''hostd'' log | |||
|- | |||
| vCenter Agent || <code> vpxa </code> || <code> /var/log/vmware/vpx/vpxa.log </code> || | |||
|} | |||
== CPU == | == CPU == | ||