RE: snmpwalk on vacm tables returns error after agent restart due to sighup

Yes. After the sighup, the snmp request does not come to the handler
functions at all. I had put some debug prints which dont get printed after
the sighup.
I've observed the same behaviour for the system table also.

Yogeeta

-----Original Message-----
From: Wes Hardaker [mailto:[email protected]]
Sent: Thursday, February 09, 2006 10:19 PM
To: T R, Yogeeta (Yogeeta)
Cc: [email protected]
Subject: Re: snmpwalk on vacm tables returns error after agent restart
due to sighup


>>>>> On Tue, 7 Feb 2006 17:33:17 +0530, "T R, Yogeeta (Yogeeta)"
<[email protected]> said:

T> The message I get is: 
T> SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupTable = No more variables
left
T> in this MIB View (It is past the end of the MIB tree)

That looks suspiciously like either the VACM tables aren't getting
re-registered after the HUP or (more likely) the vacm tokens aren't
handling the HUP cleaning properly.  I actually thought that the VACM
code was doing proper clean up (unlike other parts that I know
aren't).

For now, I'd resort to stopping and starting it entirely instead of
using HUP.

-- 
Wes Hardaker
Sparta, Inc.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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