티스토리 뷰

System logs are stored on nonpersistent storage (2032823)

Details

You receive this message when your system stores its log files on non-persistent storage.

Example

When you use the advanced system parameter Syslog.global.logDir to configure the system log location, if you configure the system log location as temporary, for example [] /tmp, you get the esx.problem.syslog.nonpersistent message.

When the location for system logs is not configured, your system uses the scratch partition by default. If the scratch location is set to nonpersistent storage, such as /tmp, you get the esx.problem.syslog.nonpersistent message.

Impact

System logs are required for auditing and diagnostic purposes. If you do not store system logs permanently, for example on a datastore, they disappear after a reboot.





Solution

Verify the Location of System Logs in the vSphere Client

  1. In the vSphere Client, select the host in the inventory panel.
  2. In the Configuration tab, under software, click Advanced Settings.
  3. Make sure that Syslog.global.logDir points to a persistent location.

    The directory should be specified as [datastorenamepath_to_file where the path is relative to the datastore. For example,[datastore1] /systemlogs.

  4. If the Syslog.global.logDir field is empty or explicitly points to a scratch partition, make sure that the fieldScratchConfig.CurrentScratchLocation shows a location on persistent storage.

Verify the Location of System Logs in the vSphere Web Client

  1. Browse to the host in the vSphere Web Client navigator.
  2. In the Manage tab, click Settings.
  3. Under System, click Advanced System Settings.
  4. Make sure that Syslog.global.logDir points to a persistent location.
  5. If the field Syslog.global.logDir is empty or points to a scratch partition, make sure that the fieldScratchConfig.CurrentScratchLocation shows a location on persistent storage. 

    Note: You must reboot the host for the changes to take effect.



댓글