2,187
edits
(→Build Notes: Added Installation and CLI) |
(→Useful paths / logfiles: Added ESXi) |
||
Line 505: | Line 505: | ||
= Troubleshooting = | = Troubleshooting = | ||
== Useful paths / logfiles== | == Useful paths / logfiles== | ||
=== ESX === | |||
{|cellpadding="2" cellspacing="0" border="1" | {|cellpadding="2" cellspacing="0" border="1" | ||
|- | |- | ||
Line 520: | Line 521: | ||
|- | |- | ||
|} | |} | ||
=== ESXi === | |||
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...''' | |||
#* Tick the appropriate object | |||
#* Untick ''Include information from vCenter Server and vSphere Client'', unless you additionally want this info | |||
# 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, 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, | |||
== CPU == | == CPU == |