On 5/16/08 9:16 AM, Saulo Augusto Silva wrote: > ... > proc db2sysc > proc snmpd > > the snmpwalk : > snmpwalk -v 2c -c public 127.0.0.1 .1.3.6.1.4.1.2021.2.1 > UCD-SNMP-MIB::prIndex.1 = INTEGER: 1 > UCD-SNMP-MIB::prIndex.2 = INTEGER: 2 > UCD-SNMP-MIB::prNames.1 = STRING: db2sysc > UCD-SNMP-MIB::prNames.2 = STRING: snmpd > UCD-SNMP-MIB::prMin.1 = INTEGER: 0 > UCD-SNMP-MIB::prMin.2 = INTEGER: 0 > UCD-SNMP-MIB::prMax.1 = INTEGER: 0 > UCD-SNMP-MIB::prMax.2 = INTEGER: 0 > UCD-SNMP-MIB::prCount.1 = INTEGER: 0 > UCD-SNMP-MIB::prCount.2 = INTEGER: 0 > UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: 1 > UCD-SNMP-MIB::prErrorFlag.2 = INTEGER: 1 > UCD-SNMP-MIB::prErrMessage.1 = STRING: No db2sysc process running. > UCD-SNMP-MIB::prErrMessage.2 = STRING: No snmpd process running. > UCD-SNMP-MIB::prErrFix.1 = INTEGER: 0 > UCD-SNMP-MIB::prErrFix.2 = INTEGER: 0 > UCD-SNMP-MIB::prErrFixCmd.1 = STRING: > UCD-SNMP-MIB::prErrFixCmd.2 = STRING: > > The ps -e > > ps -e |grep db2sysc > 9812 pts/0 00:00:00 db2syscr > 9814 pts/0 00:00:00 db2sysc > 9815 pts/0 00:00:00 db2syscr > 9816 pts/0 00:00:00 db2syscr > 9817 pts/0 00:00:00 db2syscr
Greetings Saulo, You didn't mention which OS or net-snmp version you're using.... Regardless, the default for recent vintages of net-snmp is to find process names by looking at the 'Name' line in /proc/$pid/status, so you'll need to make sure the names in there match the entry in your config. From what I'm seeing, though, you should at least be getting a match on the snmpd process - are you by chance running with SELinux enabled? -tt ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null