Re: Changing ESXi Syslog from verbose

Hi Aakash

I do not think it is case sensative:

http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.wssdk.pg.doc_50%2FPG_ChA_Diagnostics.19.4.html

But I try your "bet":

      <!-- default log level -->
      <level>None</level>

      <!-- If true, logs to syslog -->
      <outputToSyslog>true</outputToSyslog>

      <!-- syslog configuration.  Only used if outputToSyslog is true. -->
      <syslog>
         <!-- syslog identifier to use when logging -->
         <ident>Hostd</ident>

         <!-- syslog facility to use when logging -->
         <facility>local4</facility>
      </syslog>

   </log>

   <!-- Log level configuration (Rules are applied in order) -->
   <level id = "1">
      <logName> PropertyProvider </logName>
      <logLevel> None </logLevel>
      <prefix> false </prefix>
   </level>

   <level id = "2">
      <logName> SoapAdapter.HTTPService </logName>
      <logLevel> None </logLevel>
      <prefix> false </prefix>
   </level>

After change that I did:

- services.sh restart hostd

- kill -HUP $(cat /var/run/syslogd.pid)

But no changes I still get verbose and info messages in /var/log/messages:

/var/log # tail -100 messages | grep -i verbose

May 29 10:20:19 shell[558287]: tail -100 messages | grep -i verbose

May 29 10:24:30 Hostd: [2013-05-29 10:24:30.045 FFB8CE80 verbose 'Vmomi'] Arg version:

May 29 10:24:58 shell[558287]: tail -100 messages | grep -i verbose

/var/log # tail -100 messages | grep -i info

May 29 10:20:14 shell[558287]: tail -100 messages | grep -i info

May 29 10:24:30 Hostd: [2013-05-29 10:24:30.045 FFB8CE80 info 'Vmomi'] Activation [N5Vmomi10ActivationE:0x6f2d94c0] : Invoke done [waitForUpdates] on [vmodl.query.PropertyCollector:ha-property-collector]

May 29 10:24:30 Hostd: [2013-05-29 10:24:30.046 FFB8CE80 info 'Vmomi'] Throw vmodl.fault.RequestCanceled

May 29 10:24:30 Hostd: [2013-05-29 10:24:30.046 FFB8CE80 info 'Vmomi'] Result:

May 29 10:25:07 shell[558287]: tail -100 messages | grep -i info

Any ideas gurus in ESXi ? , I am getting very frustrated :S ...