Scott Silva spake the following on 5/22/2007 2:23 PM: > Scott Silva spake the following on 5/22/2007 11:44 AM: >> Dhawal Doshy spake the following on 5/22/2007 9:50 AM: >>> Scott Silva wrote: >>>> Dhawal Doshy spake the following on 5/22/2007 9:25 AM: >>>>> Scott Silva wrote: >>>>>> Abba Communications spake the following on 5/21/2007 4:25 PM: >>>>>>> Anyone besides me totally throw (most) caution into the wind and yum >>>>>>> update >>>>>>> any mission critical production 4.x boxen to 4.5 without any problems? >>>>>>> >>>>>>> 8-p >>>>>>> >>>>>>> - rh >>>>>> The only issues I am seeing are some snmp timeout errors in >>>>>> MailScanner-mrtg. >>>>> Scott, >>>>> >>>>> Did you manage to figure out an answer for this? >>>> Not yet. I can poll snmp without error from the commandline, but get >>>> timeouts >>>> almost every run of mailscanner-mrtg. >>>> I am about ready to disable the snmp tests in mrtg until I can figure >>>> it out. >>>> I am getting tired of having my servers nag me all day. >>>> >>>> Since you asked, are you seeing the same thing? >>> Yup, ever since servers upgraded to 4.5.. something like: >>> >>> Timeout: No Response from localhost:161 >>> . >>> . >>> . >>> >>> Works as expected from the command line though. >>> >>> - dhawal >> I just installed the unstable 0.11.0 and it seems to have cleared up. Since >> unstable is near to 2 years old, it can't be that unstable, but we'll see. >> > Nevermind. It just slowed it down to less than 1 per hour. > I got it to stop by creating \etc\sysconfig\snmpd.options with the following; -------snip------- OPTIONS="-LS 4 d -p /var/run/snmpd.pid -a" -------snip------- I guess the default startup options for snmp daemon cause excessive logging, and can add delays to the responses. You can read what I ran across here: http://article.gmane.org/gmane.linux.centos.general/39531 -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!