hostd failed to write to file

[llinasenc]

Hello,

I have an esxi 5.1 U2, that some system logs are not updating.

The file .vmsyslogd.err has the following information:

2020-03-23T13:22:26.803Z vmsyslog	: CRITICAL] vmsyslogd daemon starting (2409)
2020-03-23T13:22:56.971Z vmsyslog.main	: ERROR   ] reloading (2409)
2020-03-23T13:23:15.482Z vmsyslog.loggers.file	: ERROR   ] Write to /scratch/log/hostd.log failed: No such file or directory
2020-03-23T13:23:15.482Z vmsyslog.main	: ERROR   ] <hostd> failed to write log, disabling

I've check the file sytems, and there is enough space.

I've also revised the scratchconfig location, and points to valid path, as well as the syslog global dir:

The end of the hostd.log file is:

How could I solve this issue? The server keeps rebooting randomly, and I can't get why is doing so.

Regards,

[Reza Ardaneh]

Hi

- In your log file (last screenshot), there is a problem with your config.xml file (the last screenshot), so check your config.xml file from /etc/vmware/hostd to see what is the problem. If you have a backup from your config.xml file, you can restore it by replacing it with the old one.

- You can also run "vdf -h" to check your RAMDisk space.

- Check other log files such as vmkwarning.log, vmkernel.log, and vpxa.log to find more clues

I hope these could be helpful

[llinasenc]

Hello Ardaneh,

What shuold I check on config.xml?

BTW, ramdisk space is fine:

I can't upgrade to newer version because the hardware is not supported, is a HP Proliant DL 180 G6 with a basic RAID controller, no hard.

Regards,

[Reza Ardaneh]

Hello

I mean check if your config.xml file is not corrupted or missing proper tags. Please check other log files to find more information.

[Scott Vessey]

You do know you’re running an unsupported version right? Get to 6.5 at least if you can...