-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Small issue with syslog after upgrading from VMware vSphere™ 4.1 to 5.0

I was recently updating ESXi hosts from vSphere 4.1 to 5.0 using VMware vSphere™ Update Manager and after the update was finished, I had a small issue telling that syslog was not configured.

This is the warning in question:

  • System logging warning

So, let’s go to Host, click on the Configuration tab, then on the left, in the Software part, click on Advanced Settings. In Syslog → global, check the Syslog.global.logDir setting as shown in the following screenshot :

  • System logging warning 2

Uh-Oh!. It’s empty, and this is not good. After searching on a well configured host, I entered the following value : [] /scratch/log, closed the window and the problem went away. Well done !

  • System logging warning 3
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJW5eROAAoJEBeKS2x6xuR7QSAQAJzThvn0mcBFDJIftqADYqA5
tgfOFJS2zWDO4q3q9NnhPuing/m/kIa9a01IjjG4xc+8OjlQ2jKtjm1H2iT9jONQ
ZKqpfStJGDadBrpOcJr8E+Ho+HdEjj3KI4U+dqslCwt+cYqcQibI64xJrOkYGGo+
miMscG49Pw5EEzOaBDmy+bt0r9Vvk3qaVhSSSaPTSXMQGRYBDAJa2+U806rP+zta
xpoWYtjVadKSmQBfAry2udpBh65obo3JZ4YuzqlcJVaGlV37abjZZ6PaXTPmHgqP
pg2sh+81d9o8NUaqrgWLqXJQIa1+zdzMBy8y5HTtEsD5IuJZI1sB5ZCNDTPsu/l5
wwLoApTz2aBNBc+6JGNfJeaWYK/7wPd/oxpfiA6yoJXGtLl9MKiQnM5nDFmPR972
kA4laOCxa83EX9sJDEwWkQCtjYcMJams0z6CDd7Bk2mzUGuPbCFL8zRjEZvsvVwt
N5Kytbr5HwhYjAmvFiq0erie9knm/53VyLD6Dz2SlNAUq8A475BwIjWOwEc59zqi
YddA+GwK47uCTC71h2Wb2+gA4Ez2FznyzWEYu+pUOSbeRdw2EY0at0PytlyhynyP
ANvW7Ydqi6/9xK+rksYJNllaCAUVUHZcW3Xkl6oj4lNi/0PvdTjPrg2TTcg+RLiF
JijDdFsUJPukrEkyqh1P
=8jol
-----END PGP SIGNATURE-----

Hint: To validate signature, please view page source and copy html code between BEGIN PGP Signed message and END PGP Signature anchors.

Created the 2012-03-05

Share this


Resources

10 last articles

blog comments powered by Disqus