I have net-snmpd (ucd-compat) running on two machines.  net-snmp 5.4.1 was 
compiled and installed on each machine, from identical code.  Both machines 
are kernel 2.6.11.4 (SuSE 9.3).

For testing, I am running a Windows utility which sends GetRequest commands 
to the target, using our oids, and dumps the responses to a window.  On one 
machine, I can successfully read snmp data back (including our mib) using 
this utility, but on the second machine, I *cannot* do so; I do not get 
responses from snmpd.

I've tried adding some debug messages into the socket handler and my 
modules.

In the working machine I see:
Jan 18 13:12:54 hub26 snmpd: calling dispatch (count=1)
Jan 18 13:12:54 hub26 snmpd: calling snmp_read()
Jan 18 13:12:54 hub26 snmpd: in snmp_sess_read()
Jan 18 13:12:54 hub26 snmpd: ip3 magic [727]=2    <===  this is my module 
responding
Jan 18 13:12:54 hub26 snmpd: in snmp_sess_read()

and this is repeated for each field, each device, in our system.

In the failing machine, I see:
Jan 18 14:03:51 hub snmpd: calling dispatch (count=1)
Jan 18 14:03:51 hub snmpd: calling snmp_read()
Jan 18 14:03:51 hub snmpd: in snmp_sess_read()
        <===  my mib module is not being called!!
Jan 18 14:03:51 hub snmpd: in snmp_sess_read()

So somewhere between snmp_sess_read and my mib-module code, something is 
breaking down.  I'm seeing NO messages being logged in either 
/var/log/messages nor /var/log/snmpd.log that would give any hints to what 
is failing.

BTW, this doesn't appear to have anything to do with snmpd.conf; I now have 
the file in the correct location on both machines, and the behaviors have 
not changed on either.

Dan Miller



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to