VMware ESXi 5 Error “XXX esx.problem.syslog.nonpersistent.formatOnHost not found XXX”

VMware_vSphere_Logo

Here is rather not interestingly looking error message popping up when you don’t have Syslog configured properly on ESXi 5.x. I have seen few variations of this error but only have one screenshot at hand!

VMware_ESXi_5_Error_XXX_esx.problem.syslog.nonpersistent.formatOnHost_not_found_XXX_1

In a nutshell the cryptic message says that you have logs configured on non-persistent storage and they’ll not survive a reboot of the host. If we look closely at the exact location they’re indeed configured to point at ESXi scratch partition i.e. [] /scratch/log:

VMware_ESXi_5_Error_XXX_esx.problem.syslog.nonpersistent.formatOnHost_not_found_XXX_2

There are at least three ways to get us out of trouble in this situation:

  • Use 3rd party Syslog server,
  • Use Syslog server that’s bundled with vCenter 5,
  • Use persistent storage to store your logs.

  • I’m going with option 3. To get us started we have to create a folder on one of our datastores, call is let’s say Syslog and underneath that create another folder with hostname of your ESXi host (always good to know which logs are which). In my example my host is SPN-ESX-04, datastore is called VMware_ESXi_NFS_L:

    VMware_ESXi_5_Error_XXX_esx.problem.syslog.nonpersistent.formatOnHost_not_found_XXX_3

    Once done we have to re-point the Syslog option under Configuration –> Advanced Settings to our newly created folder, please note there is space between datastore name and rest of the path:

    VMware_ESXi_5_Error_XXX_esx.problem.syslog.nonpersistent.formatOnHost_not_found_XXX_4

    Few seconds later our host should move all logs and the error message will naturally go away. Also, there is no need to reboot for this setting to take effect.

    VMware_ESXi_5_Error_XXX_esx.problem.syslog.nonpersistent.formatOnHost_not_found_XXX_5

    6 thoughts on “VMware ESXi 5 Error “XXX esx.problem.syslog.nonpersistent.formatOnHost not found XXX”

    1. Michael

      That worked! I found the equivalent fix on VMwares KB site, but your posted resolution was more clear and easiy to implement.

    2. Adrian Kielbowicz Post author

      Superb! Thanks for commenting Michael.

      There is quite few similar solutions to this error floating around the internet – I tried to make mine as short and simple as possible.

    Leave a Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.