I am running Silvercreek on net-snmp. I get the following error:
The response OID
1.3.6.1.2.1.2.2.1.1.49
is lexicographically less than or equals to
The request OID
1.3.6.1.2.1.2.2.1.1.4294967295
I used mib2c.table_data.conf table helpers to handle the get/next.
index of the table is an INTEGER
Test fails on get-next
Does anyone know why net-snmp fails to handle this test correctly.
Or how to fix it?
Apparently net-snmp is responding with the first row in the table - it
should be responding with the next lexicographically greater oid in the
mib tree, when it gets a value of 4294967295 as an index.
any help on this would be appreciated.
thanks
________________________________
From: Hu, Fengliang [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2008 6:00 PM
To: Joan Landry; [email protected]
Subject: RE: A SIGHUP signal just kills snmpd daemon instead of
reloading theconfig.
Hi, Joan,
I just tried it and it didn't work... what's the version of net-snmp you
used?
On Linux tried:
kill -1 <pid>
kill -SIGHUP <pid>
kill -s SIGHUP <pid>
kill -s 1 <pid>
kill -hup <pid>
Thanks,
Feng
________________________________
From: Joan Landry [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2008 2:38 PM
To: Hu, Fengliang; [email protected]
Subject: RE: A SIGHUP signal just kills snmpd daemon instead of
reloading theconfig.
kill -hup pid, where pid = the snmpd process id.
worked when I tried it.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hu,
Fengliang
Sent: Friday, August 01, 2008 5:29 PM
To: [email protected]
Subject: A SIGHUP signal just kills snmpd daemon instead of reloading
theconfig.
Hi,
This is Feng. I am poking net-snmp software 5.4 on x86 Linux (ubuntu
7.4) and trying to see how it can reloads the new configuration (such as
the updated community string). Googled some articles, I thought SIGHUP
signal needs to be sent to snmpd process. I also took a look at the code
and it seems that on Linux it installs the signal handler for SIGHUP to
set a reconfig flag. But for me, snmpd always simply died after I "kill
-s SIGHUP <snmpd_pid>".
Snmpd was started with the following command line options:
"
-u 0 -Ls5 -Lf /dev/null -p <PID_FILE_FULL_PATH> -c
<SNMP_CONFIG_FILE_FULL_PATH> -M <MIB_DIRS>"
"
Thanks for any feedback here.
Feng
Overture Networks Inc. The information contained in this message is
privileged, confidential, and non-binding and is intended for use by the
intended recipient or entity. All other uses, including distribution to
third parties, are prohibited. Please notify the sender if you have
received this message in error. Thank You, Overture Networks.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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
