Check the following: Is the cmd file a socket and not a regular file? Is it writable? Does nagios receive the check result? (check nagios.log) Does the submitcheckresult script work? Test it from the command line
-- Wim Fournier Senior Technical Appl. Administrator | comScore, Inc. (NASDAQ:SCOR) t +31 (0)20 5195476 | f +31 (0)20 6953786 | wfourn...@comscore.com ....................................................................................... comScore Measuring the Digital World Nedstat is now part of comScore www.comscore.com www.nedstat.nl From: "firesk...@emailn.de<mailto:firesk...@emailn.de>" <firesk...@emailn.de<mailto:firesk...@emailn.de>> Reply-To: "firesk...@emailn.de<mailto:firesk...@emailn.de>" <firesk...@emailn.de<mailto:firesk...@emailn.de>>, Nagios Users List <nagios-users@lists.sourceforge.net<mailto:nagios-users@lists.sourceforge.net>> Date: Thursday, July 12, 2012 12:01 PM To: "nagios-users@lists.sourceforge.net<mailto:nagios-users@lists.sourceforge.net>" <nagios-users@lists.sourceforge.net<mailto:nagios-users@lists.sourceforge.net>> Subject: [Nagios-users] Help with creating an own trap Hello everybody i need help to create an own trap cause it' doesnt work with snmpttconvertmib the trap has non different oids but different enerptrise values tried to build the traps with the help of the trap log from our nagios server: The trap appears in the unknown trap log from snmptt. So the whole proccess from snmptt to nagios wont work. I think sth. is wrong on the config file which belongs to the trap trap.log: Mon Jul 9 11:28:33 2012: Unknown trap (.1.3.6.1.4.1.31440.0.6) received from 192.168.23.10 at: Value 0: 192.168.23.10 Value 1: 192.168.23.10 Value 2: 115:5:24:30.31 Value 3: .1.3.6.1.4.1.31440.0.6 Value 4: 192.168.23.10 Value 5: public Value 6: .1.3.6.1.4.1.31440 Value 7: Value 8: Value 9: Value 10: Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=1 Mon Jul 9 11:31:25 2012: Unknown trap (.1.3.6.1.4.1.31440.0.6) received from 192.168.23.10 at: Value 0: 192.168.23.10 Value 1: 192.168.23.10 Value 2: 121:10:59:44.32 Value 3: .1.3.6.1.4.1.31440.0.6 Value 4: 192.168.23.10 Value 5: public Value 6: .1.3.6.1.4.1.31440 Value 7: Value 8: Value 9: Value 10: Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=2 Here is the conf file: Event wateralertBOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" Critical FORMAT Bedieneingriff empfohlen EXEC /usr/local/nagios/libexec/submit_check_result localhost "Water Alert" 2 "Water $3 " MATCH $Ent Value 0: 1 Variables: Value 0: 192.168.23.10 Value 1: 192.168.23.10 Value 2: 15:2:45:35.36 Value 3: .1.3.6.1.4.1.31440.0.6 Value 4: 192.168.23.10 Value 5: public Value 6: .1.3.6.1.4.1.31440 Value 7: Value 8: Value 9: Value 10: Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=1 SDESC ow-server alert EDESC Event wateralertAOWSERVER .1.3.6.1.4.1.31440.0.6 "Status Events" INFORMATIONAL FORMAT alles ok EXEC /usr/local/nagios/libexec/submit_check_result localhost "Water Alert" 2 "Water $3 is ok" MATCH $Ent Value 0: 2 Variables: Value 0: 192.168.23.10 Value 1: 192.168.23.10 Value 2: 33:14:58:42.84 Value 3: .1.3.6.1.4.1.31440.0.6 Value 4: 192.168.23.10 Value 5: public Value 6: .1.3.6.1.4.1.31440 Value 7: Value 8: Value 9: Value 10: Ent Value 0: .1.3.6.1.4.1.31440.2.2.1.1.4=2 SDESC ow-server alert EDESC best regards john ________________________________ Versendet mit Emailn.de<http://www.emailn.de/> - Freemail * Unbegrenzt Speicherplatz * Eigenes Online-Büro * 24h besten Mailempfang * Spamschutz, Adressbuch Facebook: http://www.facebook.com/Emailn.de ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
