nv-l
[Top] [All Lists]

Re: [nv-l] Net-snmp on suse 9

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Net-snmp on suse 9
From: George deSocio <desocio@us.ibm.com>
Date: Mon, 3 Oct 2005 17:43:00 -0400
Delivery-date: Mon, 03 Oct 2005 22:43:34 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <OFB911ABBB.F54F025E-ON8625708F.0057BC68-8525708F.0059AAC4@us.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

Hello list, one more time,

After one more test, I found there are two ways to build the flags for net-snmp's snmpd daemon that will correctly handle the pass statement in the conf file, and stay running.

1)  -C -c /etc/snmpd.conf   <or>   -Cc /etc/snmpd/conf

2)  <neither of the above, that is no -C, and no "-c /etc/snmpd.conf">

The conclusion I have come to is this:

With only "-c /etc/snmpd.conf" coded (in /etc/init.d/snmpd after the rpm is installed), the default conf file, /etc/snmpd.conf, is being processed twice.  Once because -C is not specified, and once because -c is specified.  With a pass statement coded, processing the pass statement twice is what appears to cause the core.  At least that's the mile high view based on what I can see in an strace output.

With neither "-C" or "-c /etc/snmpd.conf" specified, the default is processed (which is /etc/snmpd.conf), snmpd activates correctly and works correctly.

Regards,
Geo.

George deSocio
IBM Americas Support - Distributed Network Management
Dept 46-E1ZA
Bldg B062  Office B318
PO Box 12195
Research Triangle Park, NC  27709-2195






George deSocio/Raleigh/IBM@IBMUS
Sent by: owner-nv-l@lists.us.ibm.com

10/03/2005 12:19 PM
Please respond to
nv-l

To
nv-l@lists.us.ibm.com
cc
Subject
Re: [nv-l] Net-snmp on suse 9






Hello list,


As a followup to the original question to the list:  


We found that the release of net-snmp found in some newer SUSE 9's,  net-snmp-5.1-80.11, when the pass statement (any pass statement) is added to /etc/snmpd.conf, snmpd cores with signal 11 (SIGSEGV).  This doesn't seem to be known in the net-snmp community.


In /etc/init.d/snmpd script, there is a command, startproc.  Add a -C flag after $SNMPD.   After that change, the daemon comes up, processes the pass statement, and stays up.  mgragentd also works and gets passed its oid part.


I don't know why this works :-)     But it does work around the problem as far as NetView is concerned.


This looks like a bug in net-snmp.




Regards,
Geo.

George deSocio
IBM Americas Support - Distributed Network Management
Dept 46-E1ZA
Bldg B062  Office B318
PO Box 12195
Research Triangle Park, NC  27709-2195




"Kain, Becki \(B.\)" <bkain1@ford.com>
Sent by: owner-nv-l@lists.us.ibm.com

09/29/2005 12:37 PM
Please respond to
nv-l

To
<nv-l@lists.us.ibm.com>
cc
Subject
[nv-l] Net-snmp on suse 9







Does anyone have net-snmp working on suse 9, instead of ucd-snmp?  This is for netview 7.1.4 fixpack 3.  If I put in the lines:

pass .1.3.6.1.4.1.2.6.4.6.1 /bin/sh /usr/OV/bin/mgragentd
view system included .1

Snmp won't start up.  It starts up fine without these.

TIA

-Becki Kain

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web