Error printout for set requests
Eirik Nordbrøden
We are developing an enterprise specific agentx subagent using the =
net-snmp 5.1.1 release for Linux. The subagent are currently using the =
old-api code. For the set requests we have implemented so far we get the =
following error message for each action that is taken in all the =
write_... functions:
netsnmp_assert requests->agent_req_info =3D=3D asp->reqinfo failed =
snmp_agent.c:2207 netsnmp_check_requests_status()
All the set requests seems to work fine. Anyone know what the problem =
is?
___________________________________________________________
Eirik Nordbr=F8den Telephone (+47) 90 17 47 89
moreCom A/S Switchboard (+47) 90 06 44 44
T=F8nne Huitfeldts plass 2 Fax. (+47) 69 18 81 19
N-1767 Halden Home (+47) 69 18 78 99
Norway
Email: mailto:eirik.no...@moreCom.no
WWW: http://www.moreCom.no/
___________________________________________________________
=20
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snm...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Robert Story (Coders)
EN> We are developing an enterprise specific agentx subagent using the net-snmp
EN> 5.1.1 release for Linux. The subagent are currently using the old-api code.
EN> For the set requests we have implemented so far we get the following error
EN> message for each action that is taken in all the write_... functions:
EN>
EN> netsnmp_assert requests->agent_req_info == asp->reqinfo failed
EN> snmp_agent.c:2207 netsnmp_check_requests_status()
EN>
EN> All the set requests seems to work fine. Anyone know what the problem is?
It means that two structure which should be internally consistent aren't. It's
unlikely to cause problems, so you can ignore it.
If you have some time, however, I'd appreciate it if you could provide me with
some more information to help me figure out why they aren't consistent. There
are a few different ways you could help, depending on your situation.
1) send me a copy of the simplest implementation of your handler that exhibits
the problem, so I can see if I can reproduce the problem.
2) apply a patch I can send you, and run with debug turned on, and send me the
debug results.
--
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
Eirik Nordbrøden
It will not be an easy task to send you our code since it it is =
dependant on other software that we have written so we need to consider =
oprion 2. Could you send us the patch and I will come back to you in =
some days.
-----Original Message-----
From: Robert Story (Coders) [mailto:rst...@freesnmp.com]
Sent: 14. april 2004 16:17
To: Eirik Nordbr=F8den
Cc: net-snm...@lists.sourceforge.net
Subject: Re: Error printout for set requests
On Wed, 14 Apr 2004 14:54:20 +0200 Eirik wrote:
EN> We are developing an enterprise specific agentx subagent using the =
net-snmp
EN> 5.1.1 release for Linux. The subagent are currently using the =
old-api code.
EN> For the set requests we have implemented so far we get the following =
error
EN> message for each action that is taken in all the write_... =
functions:
EN>=20
EN> netsnmp_assert requests->agent_req_info =3D=3D asp->reqinfo failed
EN> snmp_agent.c:2207 netsnmp_check_requests_status()
EN>=20
EN> All the set requests seems to work fine. Anyone know what the =
problem is?
It means that two structure which should be internally consistent =
aren't. It's
unlikely to cause problems, so you can ignore it.
If you have some time, however, I'd appreciate it if you could provide =
me with
some more information to help me figure out why they aren't consistent. =
There
are a few different ways you could help, depending on your situation.
1) send me a copy of the simplest implementation of your handler that =
exhibits
the problem, so I can see if I can reproduce the problem.=20
2) apply a patch I can send you, and run with debug turned on, and send =
me the
debug results.
--=20
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive: =
<http://sourceforge.net/mailarchive/forum.php?forum=3Dnet-snmp-coders>
You are lost in a twisty maze of little standards, all different.=20