2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→ESXi: Added note about log loss when logging to syslog svr
(→Random Problems: Added "Log Bundles Creation Fails") |
(→ESXi: Added note about log loss when logging to syslog svr) |
||
| Line 728: | Line 728: | ||
'''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. | '''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/kb/1016621 VM KB 1016621]), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). | 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/kb/1016621 VM KB 1016621]), or to a vMA server (see http://www.vmware.com/support/developer/vima/vima40/doc/vma_40_guide.pdf). Be aware that when sending logs over the network (eg to a Syslog server) its quite common for that last few log entries to not be written when an ESX fails, you'll get more complete logs when writing direct to a file. | ||
=== ESXi Tech Support Mode === | === ESXi Tech Support Mode === | ||