i didnt find any informations, so i am trying here.
I am using Esxi 6.5, this morning i was checking logs and i saw lot of lines with some error messages.
All seems to work well, i don't see any trouble on VM. Esxi is running like a charm.
But i Get this kind of messages in syslog:
2020-07-09T02:52:41Z addVob: Could not expand environment variable HOME.
2020-07-09T02:52:41Z addVob: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2020-07-09T02:52:41Z addVob: DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.
2020-07-09T02:52:41Z addVob: DictionaryLoad: Cannot open file "~/.vmware/preferences": No such file or directory.
I saw lof of people on internet with same messages in their log, but none seems to care about it.
Do anyone get info on how can i get/generate this /usr/lib/vmware/config files ?
Or anyway to solve this logs messages ?
these are leftover references to config files that were used in ancient times (with older ESXi version or even other products like the very old VMware GSX server).
/usr/lib/vmware/config is now really at /etc/vmware/config, but a lot of the ESXi code still checks the old location. You will find these references in a lot of other log files in /var/log and also in the per-VM log files.
I just checked an ESXi 7.0 host, and even there you find these messages.
However, I would not consider them real error messages, and they are definitely not harmful. Just ignore them.
I submitted a new idea for this on the vSphere Ideas site.
Please vote for it: https://vsphere.ideas.aha.io/ideas/VSP-I-229
Thanks a lot for the answer and explaination.
As it is a production server i can't make some tests, but :
if i try to create a symlink from /etc/vmware/config to /usr/lib/vmware/config it may launch scripts that are obsolet and add trouble ?
If you have information about it, it would be nice, thanks
No guarantee, but I guess it's safe to create this symlink. It's just a config file (not a script) and the system already reads /etc/vmware/config, so it would just read it twice.
However, please note that the system runs from a volatile RAM disk, so after a reboot the symlink will be gone and you need to recreate it.
I think a better idea is to create an empty file with
instead of linking to another one that is already evaluated anyway.
Thanks a lot for the "touch" tips, it is a better solution and it worked for this message
To keep the changes after reboot, i use
I added in it the command
I don't know if it is a good practice but it works
There is still some messages:
020-07-10T14:38:54Z addVob: Could not expand environment variable HOME.
2020-07-10T14:38:54Z addVob: Could not expand environment variable HOME.
2020-07-10T14:38:54Z addVob: DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.
2020-07-10T14:38:54Z addVob: DictionaryLoad: Cannot open file "~/.vmware/preferences"
With the information provided in this post, if i understand well, in the past root as a home folder was used
So i tried
but it didn't worked, does any one has idea how could i achieve it ?
Try to add
to the file
But please note that both /etc/rc.local.d/local.sh and /etc/profile.local will not be evaluated if the esxi host has UEFI secure boot enabled.