still problems with monitor

all, I'm still having problems with monitor and net-snmp 5.4.2.1 on solaris 5.10 I have the following lines in my snmpd.conf proc xntpd monitor "Process table" -r 30 -u solarw -e prErrorFlag != 0 I then stop the xntpd process for testing. While I can see, via snmpwal

Re: Problems with Monitor on Solaris 9

Dave Shield wrote: > On 02/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: >> Note: If I do not provide a valid user name with the noauth >> parameter, the monitor line >> fails requesting that I provide a user name with the agentSecName >> parameter, and I >> have definitely added one. > > As you

Re: Problems with Monitor on Solaris 9

On 02/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: Note: If I do not provide a valid user name with the noauth parameter, the monitor line fails requesting that I provide a user name with the agentSecName parameter, and I have definitely added one. As you may have noticed on the lists, I'

Re: Problems with Monitor

or and the variable needs to find its way into the various manual pages and readmes quickly. Thank you. James McKenzie -Original Message- >From: Dave Shield <[EMAIL PROTECTED]> >Sent: Oct 12, 2006 5:51 PM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: net-snmp-users &

Re: Problems with Monitor

On 12/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > This will only send out a Trap when the event fails, is that correct. With a Boolean Trigger monitor, then yes. This will send a mteTriggerFired notification whenever the monitored condition moves from false to true. > What I also need i

Re: Problems with Monitor

- >From: Dave Shield <[EMAIL PROTECTED]> >Sent: Oct 12, 2006 9:30 AM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: net-snmp-users >Subject: Re: Problems with Monitor > >On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: >> >Also try running "snmpwa

Re: Problems with Monitor

On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > >Also try running "snmpwalk ... extTable" while this is running, so we > >can see what these values actually are in between the various probes > >of the DisMan monitor. > > > Done. Files attached. A couple of things that I noticed from your

Re: Problems with Monitor

On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > >From: Dave Shield <[EMAIL PROTECTED]> > >Try running the agent with the option "-Ddisman". > >What debug output gets displayed? > > As the included text file shows. No changes for when xstatus is changed. > > monitor -u me -r 60 -e 'TestDn'

Re: Problems with Monitor

>From: Dave Shield <[EMAIL PROTECTED]> >Sent: Oct 11, 2006 8:25 AM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: NET SNMP List >Subject: Re: Problems with Monitor > >On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: >> You are correct with the mo

Re: Problems with Monitor

On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > >If you're using the 5.3.x line, then you ought to be able to merge the > >various monitor lines into a single entry: > > > >monitor -r 60 -o extName -o extOutput "status table" extResult != 0 > > Still no notifications when I change

Re: Problems with Monitor

>From: Dave Shield <[EMAIL PROTECTED]> >Sent: Oct 11, 2006 8:22 AM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: NET SNMP List >Subject: Re: Problems with Monitor > >On 10/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: >> Following the suggestions in

Re: Problems with Monitor

On 11/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > You are correct with the monitor line, with the exception that I HAVE to > specify a user > using the -u parameter. Yes - that's a problem that I need to look at. > When I change the value of the result from either 0 to 1 or 1 to 0 no >

Re: Problems with Monitor

-r 60 and the first -o entry. Is this necessary? James McKenzie -Original Message- >From: Dave Shield <[EMAIL PROTECTED]> >Sent: Oct 11, 2006 5:22 AM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: NET SNMP List >Subject: Re: Problems with Monitor > >On

Re: Problems with Monitor

On 10/10/06, James Mckenzie <[EMAIL PROTECTED]> wrote: > Following the suggestions in readme.solaris I created a tester1 file. The > monitor > appears to trigger, but no notification is send whenever the status is > changed from > success to failure or from failure to success. Is this a known p

RE: Problems with Monitor

Subject: Re: Problems with Monitor I have the similiar problem. no notification is sent until I send a "snmpget" command. why? - Original Message - From: James Mckenzie <[EMAIL PROTECTED]> Date: Tuesday, October 10, 2006 5:15 pm Subject: Problems with Monitor > Follow

Re: Problems with Monitor

lmSensors - Original Message - From: James Mckenzie <[EMAIL PROTECTED]> Date: Tuesday, October 10, 2006 6:14 pm Subject: Re: Problems with Monitor > Jing: > > I will try this tomorrow morning. I never thought of using the > snmpget command. However, what do you

Re: Problems with Monitor

]> >Sent: Oct 10, 2006 2:44 PM >To: James Mckenzie <[EMAIL PROTECTED]> >Cc: NET SNMP List >Subject: Re: Problems with Monitor > >I have the similiar problem. no notification is sent until I send a "snmpget" >command. why? > >- Original Message

Re: Problems with Monitor

I have the similiar problem. no notification is sent until I send a "snmpget" command. why? - Original Message - From: James Mckenzie <[EMAIL PROTECTED]> Date: Tuesday, October 10, 2006 5:15 pm Subject: Problems with Monitor > Following the suggestions in readme.

Problems with Monitor

Following the suggestions in readme.solaris I created a tester1 file. The monitor appears to trigger, but no notification is send whenever the status is changed from success to failure or from failure to success. Is this a known problem with 5.3.1? James McKenzie ---

Problems with Monitor on Solaris 9

Well, I followed the advice of a list member but I still cannot run monitors against the Apache httpd process and get a trap when the httpd process fails. Attached are the snmpd.conf (stripped of comments) and the snmpd.log file. Note: If I do not provide a valid user name with the noauth parame