Thanks for the patch information, it seems that patch is already added in
5.3.1, but the problem still exists.
The following is the "snmpgetnext 10.1 nlmLogEngineID.0.1" GDB back trace:
Breakpoint 2, table_helper_handler (handler=0x10063978, reginfo=0x100633d8,
reqinfo=0x100dd5f8, re
Dave,
I am using 5.3.1, the implementation agent/mibgroup/notification-log-mib
is provided in 5.3.1. Since transport is NULL,
COLUMN_NLMLOGENGINETADDRESS and COLUMN_NLMLOGENGINETDOMAIN are NULL.
However, COLUMN_NLMLOGNOTIFICATIONID is not NULL, but getnext would skip
it because of the two NULL obj
I already tried that. If I try to access the socket with transport->sock or
similar (like snmp_sess_transport(ss)->sock) the application behaves in a very
strange way. Basically every line containig transport->sock and all the
following code is ignored (as if a return call was placed in their p
On 06/09/07, alok bharti <[EMAIL PROTECTED]> wrote:
> I am using net-snmp-5.3.1
>
> when i try to re-configure snmpd without stoping it,
> it throws error. i give SIGHUP to reconfigure.
>
> follwing are the error logs:-
>
> error on subcontainer '' insert (-1)
[snip]
Can you please try with the
Hi,
I am using net-snmp-5.3.1
when i try to re-configure snmpd without stoping it,
it throws error. i give SIGHUP to reconfigure.
follwing are the error logs:-
error on subcontainer '' insert (-1)
error on subcontainer '' insert (-1)
error on subcontainer '' insert (-1)
error on subcontainer ''
On 05/09/07, Emi Yanagi <[EMAIL PROTECTED]> wrote:
> I am reporting a bug in snmpgetnext.
[snip]
> Any idea how to improve snmpgetnext in this case?
It's not a bug in snmpgetnext.It's an error in snmpd agent.
How have you implemented this particular table?
What version of the agent are you
Glad I was able to help!
Oops, it looks like I responded only to you instead of the list. :-)
On 9/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> Hi,
>
> That was mistakenly written but i actually used,
> /usr/local/sbin/snmpd -c /usr/local/share/snmpd.conf -X tcp:localhost:706
>
>
> But
[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 05/09
Problem is in "sparse_table_helper_handler" function,
-if (request->requestvb->type == ASN_NULL ||
-request->requestvb->type == SNMP_NOSUCHINSTANCE) {
+if (request->requestvb->type == SNMP_NOSUCHINSTANCE) {
When ' request->requestvb->type' is ASN_NULL