Good call, Dave: I put the line in snmpd.conf and restarted. Everything came
up happily (and I noticed that /var/agentx/master exists as a socket, where
even the directory /var/agentx had not existed before). For some reason it
is behaving as if the subagent is not there, i.e. skipping over our subtree
when I do a "getnext". But I expect I can turn on DEBUG in the subagent and
track it down. If not, I'll get back to you...

Thanks,

Larry

On 4/16/08, Dave Shield <[EMAIL PROTECTED]> wrote:
>
> On 15/04/2008, Larry Dickson <[EMAIL PROTECTED]> wrote:
> > netsnmp_assert !"registration != duplicate" failed
> >      agent_registry.c:535 netsnmp_subtree_load()
> > netsnmp_assert !"registration != duplicate" failed
> >      agent_registry.c:535 netsnmp_subtree_load()
> >  netsnmp_assert !"registration != duplicate" failed
> >      agent_registry.c:535 netsnmp_subtree_load()
>
> You can ignore those - they're harmless.
>
>
> > Turning on AgentX master support.
> > Error: Couldn't open a master agentx socket to listen on ():
>
> Who are you running this agent as?  Root, or a different user?
>
> Do you have an "agentXSocket" directive in your snmpd.conf file?
> What AgentX-related config settings do you have?
>
> Does the directory /var/agentx exist before you start the agent?
> What about the socket /var/agentx/master
> (both before and after starting the agent).
>
>
> >                        This means agentx_sockets =
> > strdup(netsnmp_get_string(NETSNMP_DS_APPLICATION_ID,
> > NETSNMP_DS_AGENT_X_SOCKET)) returned nothing
>
> That's normal.
> This is the mechanism for overriding the default AgentX socket
> (either via the 'AgentXSocket' config directive, or the -x command
> line option).
>
>
> The issue actually lies with setting the default value (a few lines
> later).
> This changed from
>    agentx_sockets = strdup(  {NETSNMP_}AGENTX_SOCKET );
>
> in the 5.2.x and 5.3.x lines, and is now
>    agentx_sockets = strdup( "" );
>
> This was part of SVN revision 15258, aimed at introducing a
> more flexible transport creation mechanism.   It may be that
> this has broken (or changed) the default AgentX behaviour.
>
> A simple workaround would be to specify the AgentX port
> explicitly - either in the snmpd.conf file
>
>    agentXSocket    /var/agentx/master
>
> or on the command line
>
>   snmpd  -x  /var/agentx/master .....
>
> Dave
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to