Dave-- Problem solved! My snmpd.conf file was only readable to the USER (600). I changed the permissions to make it readable to the GROUP and OTHERS (644), and the problem is now resolved.
I guess when the reloading of the config file is happening, it was not doing it as the USER (which in my case is "root"). The agent was started as "root", so I am a little surprised that it isn't reading the file during reload as "root". Changing file permissions to make snmpd.conf world-readable solved the problem. Thanks. --Todd SwRI On 12/2/11 10:48 AM, "Dave Shield" <[email protected]> wrote: >On 29 November 2011 21:07, Newton, Todd A. <[email protected]> wrote: >> Yes, the agent is still running. However, I have not checked the log. >> Does logging need to be explicitly enabled? I've just been running >>snmpd >> through /etc/init.d. >> >> I have been running on Linux Ubuntu 10.4 and 11.4. The former is using >> v5.4.2.1, and the latter is using v5.4.3. > >No - you shouldn't need to explicitly enable logging (unless the Ubuntu >startup scripts disable it by default). Have you managed to find the >appropriate log file? > >Alternatively, you could run the agent by hand, using something like > > snmpd -f -Le 9999 > >and then send it the versionUpdateConfig.0 SET request (on port 9999). >That would allow you to see any output immediately. > >Dave ------------------------------------------------------------------------------ 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
