Excessive amount of “addVob” logs in syslog.log on ESXi 6.5 (Updated)

Last week we noticed that the amount of logs that our ESXi 6.5 servers are sending to syslog server have increased significantly. After some analysis we say that almost 60% of logs are from syslog.log with lines like this – “2018-11-15T15:37:18Z addVob[297777]:<message>” 

We have opened a case in VMware Support but no help so far. I will update the post as the support case progresses.

Some one else had/has a similar issue: https://communities.vmware.com/message/2817143

Update 18.11.2018 These following lines repeat in syslog.log every 5 seconds.

2018-11-15T21:09:42Z addVob[316208]: Could not expand environment variable HOME.
2018-11-15T21:09:42Z addVob[316208]: Could not expand environment variable HOME.
2018-11-15T21:09:42Z addVob[316208]: DictionaryLoad: Cannot open file “/usr/lib/vmware/config”: No such file or directory.
2018-11-15T21:09:42Z addVob[316208]: DictionaryLoad: Cannot open file “~/.vmware/config”: No such file or directory.
2018-11-15T21:09:42Z addVob[316208]: DictionaryLoad: Cannot open file “~/.vmware/preferences”: No such file or directory.
2018-11-15T21:09:42Z addVob[316208]: Wrong number of arguments for vob vob.user.vmsyslogd.remote.failure (got 2; expected 1)
2018-11-15T21:09:42Z addVob[316208]: Usage: /usr/lib/vmware/vob/bin/addvob vob-id [vob-args]
2018-11-15T21:09:42Z addVob[316208]: Recognized vobs:
2018-11-15T21:09:42Z addVob[316208]: vob.user.shell.enabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.shell.disabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.ssh.enabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.ssh.disabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.dcui.enabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.dcui.disabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.lockdownmode.enabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.lockdownmode.disabled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.account.loginfailures (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.account.locked (3 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.maintenancemode.entering (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.maintenancemode.canceled (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.maintenancemode.entered (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.maintenancemode.exited (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.maintenancemode.failed (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.vmsyslogd.remote.failure (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.vmsyslogd.storage.failure (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.vmsyslogd.unexpected (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.vmsyslogd.storage.logdir.invalid (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.hostacceptance.changed (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.install.invalidhardware (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.install.securityalert (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.install.stage.error (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.install.error (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.vib.install.successful (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.vib.remove.successful (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.install.novalidation (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.profile.install.successful (3 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esximage.profile.update.successful (3 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.dhclient.lease.none (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.dhclient.lease.offered.noexpiry (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.ntpd.clock.correction.error (2 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.host.boot (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.host.stop.reboot (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.host.stop.shutdown (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esxcli.host.reboot (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.esxcli.host.poweroff (1 arg)
2018-11-15T21:09:42Z addVob[316208]: vob.user.host.coredump (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.coredump.unconfigured (0 args)
2018-11-15T21:09:42Z addVob[316208]: vob.user.coredump.copyspace (1 arg)

VMware Support claims this is normal.

Update 19.11.2018

In the repeating logs entries there is a message “2018-11-15T21:09:42Z addVob[316208]: Wrong number of arguments for vob vob.user.vmsyslogd.remote.failure (got 2; expected 1)”. This line got me thinking. We have configured two syslog targets. I decided to remove one them and as soon as I did that the spamming in syslog.log stopped. As soon as I added second syslog target back it started again.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

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