Fw: pass_persist issue...

Regarding my query last week on my pass_persist issue (see below), I've upgraded my Net-SNMP to 5.4.1, but am seeing the same behavior.
It must be something with my script that's causing the Net-SNMP agent to send my script 4 SIGPIPE signals, but I just can't see what it is.

Any help in debugging this would be greatly appreciated. For example, how can I put the agent into a verbose debug logging mode so I can possibly see if, and what, it might be complaining about?

Thanks.

Ken....



----- Original Message ----- 
From: Ken Adey 
To: [email protected] 
Sent: Thursday, August 30, 2007 4:34 PM
Subject: pass_persist issue...


Hello,
    I'm trying to implement my private MIB using the persist_test.py script posted here recently, and am having a problem.
The script starts up and does the PING/PONG handshake, but when I try an snmpget, after the stdin/stddout lines are exchanged,
the script receives 4 SIGPIPE signals, and snmpget reports "There is no such variable name in this MIB".

If I run the script manually, everything looks fine:

[root@myserver kware]# ./persist_test.py 
PING
PONG

get
.1.3.6.1.4.1.29090.1.1
.1.3.6.1.4.1.29090.1.1
integer
1



I'm using Fedora Core 6 and the Net-SNMP that comes with it.

Any help would be appreciated.

Ken....

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
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