This happens only occasionally, not for a particular MIB object.
Normally, all queries are fine. When our customer does 2 multiple walks
(both walks repeat in minutes interval), I can find "
netsnmp_call_handler() called illegally" message in log file sometimes,
not always. When this happens, user has to restart snmpd and subagents
in order to get the data again.
I saw On 2003-06-06 net-snmp-user maillist, Olsson, Sten mentioned the
same problem but don't know whether he found the problem or not.
I used old mib2c.old-api.conf to generate the subagent code. At this
point, it is hard to change to new api. I called the following routings
to initialize the subagents:
init_agent()
initAgentMibs
{
if(should_init("gtmAppContextDisable"))init_gtmAppContextDisable();
if(should_init("gtmAppContextStat")) init_gtmAppContextStat();
...
...
}
init_snmp()
Do I miss anything? Is it full initialization code you mentioned?
Thanks,
FT
-----Original Message-----
From: Dave Shield [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 1:15 AM
To: Fong Tsui
Cc: [email protected]
Subject: Re: netsnmp_call_handler() called illegally
On Wed, 2005-09-21 at 13:30 -0700, Fong Tsui wrote:
> Does anybody know what causes the "netsnmp_call_handlers() called
> illegally" log message?
It means that the handler didn't provide all of the necessary
information when it was registered.
Is this triggered when you query a particular MIB object?
How was this object (table, etc) registered?
Please provide the full initialisation code for the
relevant module.
Dave
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
