On Fri, 2 Dec 2011 19:16:00 +0000 Todd A. wrote: NTA> Problem solved! My snmpd.conf file was only readable to the USER (600). NTA> I changed the permissions to make it readable to the GROUP and OTHERS NTA> (644), and the problem is now resolved.
Well, I'd say you found a work-around, but the problem remains. NTA> I guess when the reloading of the config file is happening, it was not NTA> doing it as the USER (which in my case is "root"). The agent was started NTA> as "root", so I am a little surprised that it isn't reading the file NTA> during reload as "root". Is the agent configured to run as a different, unprivileged, user? After ou start it initially, 'ps -ef|grep snmpd' should tell what user it is running as. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
