2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→Useful paths / logfiles: Added workaround to ESXi logfile's not surviving restarts
(→Useful paths / logfiles: Updated "ESXi" with more info) |
(→Useful paths / logfiles: Added workaround to ESXi logfile's not surviving restarts) |
||
| Line 533: | Line 533: | ||
# Once exported, uncompress the ESX's tgz file | # Once exported, uncompress the ESX's tgz file | ||
However, this is most easily achieved if you've got the PowerCLI installed, in which case see [[VI_Toolkit_(PowerShell)#ESXi_Logs]] | However, this is most easily achieved if you've got the PowerCLI installed, in which case see [[VI_Toolkit_(PowerShell)#ESXi_Logs]] | ||
{|cellpadding="2" cellspacing="0" border="1" | {|cellpadding="2" cellspacing="0" border="1" | ||
| Line 546: | Line 544: | ||
| vCenter Agent || <code> vpxa </code> || <code> /var/log/vmware/vpx/vpxa.log </code> || | | vCenter Agent || <code> vpxa </code> || <code> /var/log/vmware/vpx/vpxa.log </code> || | ||
|} | |} | ||
'''Logfiles get lost at restart !''' If you have to restart 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. | |||
However, there is a way around this. Message's can be sent to a syslog file (say on centrally available SAN LUN), a syslog server (in both cases see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016621), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). | |||
== CPU == | == CPU == | ||