VMware has identified an issue affecting VMware ESXi 5.0x and 5.1x where CIM monitoring applications fail to authenticate with “No space left on device” error in /var/log/syslog.log: kb.vmware.com/.../search.do
This issue can cause previously discovered systems to move to an unknown status, fail to discover, or not show in both OpenManage Essentials (OME) and Dell Management Plugin for VMware vCenter (DMPVV).
The current workaround is to issue “/etc/init.d/wsman restart” on the ESXi host shell.
While a permanent solution to this issue has not been identified by VMware as of 13 March 2013, the following steps can be followed to create a persistent cron job to restart the wsman service once a day.
Add the following to /etc/rc.local (for ESXi 5.1 systems edit: /etc/rc.local.d/local.sh):
# Added by Dell to add cronjob for restarting wsman 12:15 AM/PM
/bin/kill $(cat /var/run/crond.pid)
/bin/echo '15 0,12 * * * /etc/init.d/wsman restart' >> /var/spool/cron/crontabs/root
/bin/busybox crond
Execute auto-backup.sh (sh /sbin/auto-backup.sh) after making edits.
Reboot the system.
On reboot “cat /var/spool/cron/crontabs/root” should show:
#min hour day mon dow command
1 1 * * * /sbin/tmpwatch.py
1 * * * * /sbin/auto-backup.sh
0 * * * * /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5 * * * * /sbin/hostd-probe
15 0,12 * * * /etc/init.d/wsman restart
NOTE: In previous releases of ESXi, you could add custom commands in /etc/rc.local which would automatically execute after all startup scripts have finished. With the latest release of ESXi 5.1, this functionality has been moved to /etc/rc.local.d/local.sh.
Thanks,
Raj Shresta