-- Forwarded message --
From: Osvaldo Alvarez Pozo [EMAIL PROTECTED]
Date: Fri, Aug 1, 2008 at 12:09 PM
Subject: Re: running a command when there is a problem with proces
To: Dave Shield [EMAIL PROTECTED]
I modified my snmpd.conf like this.
setEvent ProcessusError prErrFix = 1
Hi all
I continue with my problem of procfix.
IF I use snmpset to set UCD-SNMP-MIB::prErrFix.1 apache2 get started.
I putted this command in a cron job but I can take a minute before
starting apache2. That'is why I am interested on using SetEvent to
set prErrFix to 1.
I do not understand why a
Hi all.
Im am checking the apache2 proces but my procfix does not get executed
when I do snmpwalk I get this
UCD-SNMP-MIB::prErrMessage.1 = STRING: No apache2 process running.
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: error(1)
UCD-SNMP-MIB::prErrFix.1 = INTEGER: noError(0)
this my snmpd.conf:
2008/7/31 Osvaldo Alvarez Pozo [EMAIL PROTECTED]:
Im am checking the apache2 proces but my procfix does not get executed
You need to action this yourself - either directly:
$ snmpset prErrFix i 1
or via a suitable monitor/setEvent combination:
setEvent caniPressTheButtonAgain
