I do, indeed, have those in my snmpd.conf.  If you take a look at the
logs, you'll see that the request does seem to be getting to the
sub-agent, according to its output.  I copied the delayed_instance
handler out of the tutorials and set a breakpoint in it:  it isn't
getting called.  I'm not sure why, but it looks like the subagent code
is receiving the GET request, but not calling the handler. 

 

I will try building the 5.5 sources via Visual Studio shortly and let
you know if there's any difference.  If I get them built, I'll add some
debugging statements to see where it's dropping the request.

 

--Evan

 

From: [email protected] [mailto:[email protected]] On
Behalf Of Bart Van Assche
Sent: Monday, July 19, 2010 11:58 AM
To: Van Dyke, Evan (ES)
Cc: [email protected]
Subject: EXTERNAL:Re: Subagent example code timeout on Win32

 

On Mon, Jul 19, 2010 at 5:16 PM, Van Dyke, Evan (ES)
<[email protected]> wrote:

My apologies if this has been discussed before, but I couldn't find it
in a quick search of the archives.

I am trying to build the sub-agent example on the NetSNMP Wiki on a
Win32 system.  I am currently using the NetSNMP v5.5 binary distribution
for Win32.

 

After some judicious searching and debugging, I was able to determine
that I had to add a line to the example-daemon.c file to specify where
the subagent should contact the master agent:

      netsnmp_ds_set_string(NETSNMP_DS_APPLICATION_ID,
NETSNMP_DS_AGENT_X_SOCKET, "tcp:localhost:705");


Do you have the following two lines in snmpd.conf ?

master agentx
agentxsocket tcp:localhost:705

Bart.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to