From borat.gunter at googlemail.com Fri Jul 9 10:39:48 2010 From: borat.gunter at googlemail.com (borat Gunter) Date: Fri, 9 Jul 2010 10:39:48 +0200 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? Message-ID: Dear all, I have found an interesting point as I test my switch-ports by so: *define service{ use router-service host_name switch1 service_description portstest check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.1,1.3.6.1.2.1.2.2.1.8.2,1.3.6.1.2.1.2.2.1.8.3,1.3.6.1.2.1.2.2.1.8.4,1.3.6.1.2.1.2.2.1.8.5,1.3.6.1.2.1.2.2.1.8.6,1.3.6.1.2.1.2.2.1.8.7,1.3.6.1.2.1.2.2.1.8.8,1.3.6.1.2.1.2.2.1.8.9,1.3.6.1.2.1.2.2.1.8.10,1.3.6.1.2.1.2.2.1.8.11,1.3.6.1.2.1.2.2.1.8.12,1.3.6.1.2.1.2.2.1.8.13,1.3.6.1.2.1.2.2.1.8.14,1.3.6.1.2.1.2.2.1.8.15,1.3.6.1.2.1.2.2.1.8.16,1.3.6.1.2.1.2.2.1.8.17,1.3.6.1.2.1.2.2.1.8.18,1.3.6.1.2.1.2.2.1.8.19,1.3.6.1.2.1.2.2.1.8.20,1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] } define command { command_name snmp_ports command_line $USER1$/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -r $ARG2$ -l 'snmp_ports' } *With this definition nagios shows *critical *status, but as I *reduced *the number of OIDs, *only from 1.3.6.1.2.1.2.2.1.8.21 to 1.3.6.1.2.1.2.2.1.8.48*, then nagios shows *OK*, after I add any of a OID from* *1.3.6.1.2.1.2.2.1.8.1 to 1.3.6.1.2.1.2.2.1.8.20, nagios gives out again the *critical *status. Although with snmpwalk have I all the 1 to 48 Ports with 1(Up) or 2(Down) status. Any Help? thanks very much in advance. best regards. ------------------------------ ------------------------------------------------------------------ Hallo Zusammen, Ich ?berwache gerade mein Switch-Ports, insg. 48 Ports, habe mit *define service{ use router-service host_name switch1 service_description portstest check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.1,1.3.6.1.2.1.2.2.1.8.2,1.3.6.1.2.1.2.2.1.8.3,1.3.6.1.2.1.2.2.1.8.4,1.3.6.1.2.1.2.2.1.8.5,1.3.6.1.2.1.2.2.1.8.6,1.3.6.1.2.1.2.2.1.8.7,1.3.6.1.2.1.2.2.1.8.8,1.3.6.1.2.1.2.2.1.8.9,1.3.6.1.2.1.2.2.1.8.10,1.3.6.1.2.1.2.2.1.8.11,1.3.6.1.2.1.2.2.1.8.12,1.3.6.1.2.1.2.2.1.8.13,1.3.6.1.2.1.2.2.1.8.14,1.3.6.1.2.1.2.2.1.8.15,1.3.6.1.2.1.2.2.1.8.16,1.3.6.1.2.1.2.2.1.8.17,1.3.6.1.2.1.2.2.1.8.18,1.3.6.1.2.1.2.2.1.8.19,1.3.6.1.2.1.2.2.1.8.20,1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] } define command { command_name snmp_ports command_line $USER1$/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -r $ARG2$ -l 'snmp_ports' } *probiert und bekomme ich Critical-Meldung, obwohl alle Ports antwortet mit entweder 1 oder 2. *Dann habe ich von OID 1.3.6.1.2.1.2.2.1.8.48 angefangen und Anzahl zunehmend getestet*, bis zu 1.3.6.1.2.1.2.2.1.8.21 (d.h.check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] ), meldet das Plugin immer *OK *Zustand, dann egal mit 1.3.6.1.2.1.2.2.1.8.20 oder 1.3.6.1.2.1.2.2.1.8.1 hinzugef?gt, nur *ein OID mehr*, dann meldet das Plugin *Critical*, obwohl per snmpwalk-Abfragen kriege ich ganz normale R?ckmeldung 1 oder 2. Kann Jemand mir weiter helfen? Vielen Dank im Voraus, -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bret_Cason at symantec.com Fri Jul 9 17:10:14 2010 From: Bret_Cason at symantec.com (Bret Cason) Date: Fri, 9 Jul 2010 08:10:14 -0700 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: References: Message-ID: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> >From the Nagios Plugins check_snmp documentation: Notes: - Multiple OIDs may be indicated by a comma- or space-delimited list (lists with internal spaces must be quoted) [max 8 OIDs] Related, I've also had some problems with MaxMessageSize truncating return data. Regards. From: borat Gunter [mailto:borat.gunter at googlemail.com] Sent: Friday, July 09, 2010 1:40 AM To: nagiosplug-devel at lists.sourceforge.net; nagios-users at lists.sourceforge.net Subject: [Nagiosplug-devel] check_snmp OID numbers limited? Dear all, I have found an interesting point as I test my switch-ports by so: define service{ use router-service host_name switch1 service_description portstest check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.1,1.3.6.1.2.1.2.2.1.8.2,1.3.6.1.2.1.2.2.1.8.3,1.3.6.1.2.1.2.2.1.8.4,1.3.6.1.2.1.2.2.1.8.5,1.3.6.1.2.1.2.2.1.8.6,1.3.6.1.2.1.2.2.1.8.7,1.3.6.1.2.1.2.2.1.8.8,1.3.6.1.2.1.2.2.1.8.9,1.3.6.1.2.1.2.2.1.8.10,1.3.6.1.2.1.2.2.1.8.11,1.3.6.1.2.1.2.2.1.8.12,1.3.6.1.2.1.2.2.1.8.13,1.3.6.1.2.1.2.2.1.8.14,1.3.6.1.2.1.2.2.1.8.15,1.3.6.1.2.1.2.2.1.8.16,1.3.6.1.2.1.2.2.1.8.17,1.3.6.1.2.1.2.2.1.8.18,1.3.6.1.2.1.2.2.1.8.19,1.3.6.1.2.1.2.2.1.8.20,1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] } define command { command_name snmp_ports command_line $USER1$/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -r $ARG2$ -l 'snmp_ports' } With this definition nagios shows critical status, but as I reduced the number of OIDs, only from 1.3.6.1.2.1.2.2.1.8.21 to 1.3.6.1.2.1.2.2.1.8.48, then nagios shows OK, after I add any of a OID from 1.3.6.1.2.1.2.2.1.8.1 to 1.3.6.1.2.1.2.2.1.8.20, nagios gives out again the critical status. Although with snmpwalk have I all the 1 to 48 Ports with 1(Up) or 2(Down) status. Any Help? thanks very much in advance. best regards. ------------------------------ ------------------------------------------------------------------ Hallo Zusammen, Ich ?berwache gerade mein Switch-Ports, insg. 48 Ports, habe mit define service{ use router-service host_name switch1 service_description portstest check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.1,1.3.6.1.2.1.2.2.1.8.2,1.3.6.1.2.1.2.2.1.8.3,1.3.6.1.2.1.2.2.1.8.4,1.3.6.1.2.1.2.2.1.8.5,1.3.6.1.2.1.2.2.1.8.6,1.3.6.1.2.1.2.2.1.8.7,1.3.6.1.2.1.2.2.1.8.8,1.3.6.1.2.1.2.2.1.8.9,1.3.6.1.2.1.2.2.1.8.10,1.3.6.1.2.1.2.2.1.8.11,1.3.6.1.2.1.2.2.1.8.12,1.3.6.1.2.1.2.2.1.8.13,1.3.6.1.2.1.2.2.1.8.14,1.3.6.1.2.1.2.2.1.8.15,1.3.6.1.2.1.2.2.1.8.16,1.3.6.1.2.1.2.2.1.8.17,1.3.6.1.2.1.2.2.1.8.18,1.3.6.1.2.1.2.2.1.8.19,1.3.6.1.2.1.2.2.1.8.20,1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] } define command { command_name snmp_ports command_line $USER1$/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -r $ARG2$ -l 'snmp_ports' } probiert und bekomme ich Critical-Meldung, obwohl alle Ports antwortet mit entweder 1 oder 2. Dann habe ich von OID 1.3.6.1.2.1.2.2.1.8.48 angefangen und Anzahl zunehmend getestet, bis zu 1.3.6.1.2.1.2.2.1.8.21 (d.h.check_command snmp_ports!1.3.6.1.2.1.2.2.1.8.21,1.3.6.1.2.1.2.2.1.8.22,1.3.6.1.2.1.2.2.1.8.23,1.3.6.1.2.1.2.2.1.8.24,1.3.6.1.2.1.2.2.1.8.25,1.3.6.1.2.1.2.2.1.8.26,1.3.6.1.2.1.2.2.1.8.27,1.3.6.1.2.1.2.2.1.8.28,1.3.6.1.2.1.2.2.1.8.29,1.3.6.1.2.1.2.2.1.8.30,1.3.6.1.2.1.2.2.1.8.31,1.3.6.1.2.1.2.2.1.8.32,1.3.6.1.2.1.2.2.1.8.33,1.3.6.1.2.1.2.2.1.8.34,1.3.6.1.2.1.2.2.1.8.35,1.3.6.1.2.1.2.2.1.8.36,1.3.6.1.2.1.2.2.1.8.37,1.3.6.1.2.1.2.2.1.8.38,1.3.6.1.2.1.2.2.1.8.39,1.3.6.1.2.1.2.2.1.8.40,1.3.6.1.2.1.2.2.1.8.41,1.3.6.1.2.1.2.2.1.8.42,1.3.6.1.2.1.2.2.1.8.43,1.3.6.1.2.1.2.2.1.8.44,1.3.6.1.2.1.2.2.1.8.45,1.3.6.1.2.1.2.2.1.8.46,1.3.6.1.2.1.2.2.1.8.47,1.3.6.1.2.1.2.2.1.8.48![12] ), meldet das Plugin immer OK Zustand, dann egal mit 1.3.6.1.2.1.2.2.1.8.20 oder 1.3.6.1.2.1.2.2.1.8.1 hinzugef?gt, nur ein OID mehr, dann meldet das Plugin Critical, obwohl per snmpwalk-Abfragen kriege ich ganz normale R?ckmeldung 1 oder 2. Kann Jemand mir weiter helfen? Vielen Dank im Voraus, -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Sat Jul 10 01:42:15 2010 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 09 Jul 2010 19:42:15 -0400 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> References: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> Message-ID: <4C37B3D7.9090209@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10-07-09 11:10 AM, Bret Cason wrote: > From the Nagios Plugins check_snmp documentation: > > > > Notes: > > - Multiple OIDs may be indicated by a comma- or space-delimited list > (lists with > > internal spaces must be quoted) [max 8 OIDs] > You can edit plugins/check_snmp.c. Near the beginning you will see: #define MAX_OIDS 8 You can change that to a bigger number and it should work ok. YMMV, please report any bug you get while modifying this. The --help output won't change though, I just fixed that for the next release. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw3s9EACgkQ6dZ+Kt5BchY8wgCeLV8WlVQzobLBnlUzMNiMvRk5 iyYAnjikxc2645MzZqbShL0lmKt5ok9w =Lux5 -----END PGP SIGNATURE----- From nagiosplug-devel at lusis.org Sat Jul 10 03:08:24 2010 From: nagiosplug-devel at lusis.org (John Vincent) Date: Fri, 9 Jul 2010 21:08:24 -0400 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: <4C37B3D7.9090209@aei.ca> References: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> <4C37B3D7.9090209@aei.ca> Message-ID: On Fri, Jul 9, 2010 at 7:42 PM, Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10-07-09 11:10 AM, Bret Cason wrote: >> From the Nagios Plugins check_snmp documentation: >> >> >> >> Notes: >> >> ?- Multiple OIDs may be indicated by a comma- or space-delimited list >> (lists with >> >> ? ?internal spaces must be quoted) [max 8 OIDs] >> > > You can edit plugins/check_snmp.c. Near the beginning you will see: > > #define MAX_OIDS 8 > > You can change that to a bigger number and it should work ok. YMMV, > please report any bug you get while modifying this. > > The --help output won't change though, I just fixed that for the next > release. > > - -- > Thomas To be fair, at the point you need that many OIDs you should really start using the MIB files. From dermoth at aei.ca Sat Jul 10 05:20:52 2010 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 09 Jul 2010 23:20:52 -0400 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: References: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> <4C37B3D7.9090209@aei.ca> Message-ID: <4C37E714.3060105@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10-07-09 09:08 PM, John Vincent wrote: > On Fri, Jul 9, 2010 at 7:42 PM, Thomas Guyot-Sionnest wrote: >> >> You can edit plugins/check_snmp.c. Near the beginning you will see: >> >> #define MAX_OIDS 8 >> >> You can change that to a bigger number and it should work ok. YMMV, >> please report any bug you get while modifying this. >> >> The --help output won't change though, I just fixed that for the next >> release. >> >> - -- >> Thomas > > To be fair, at the point you need that many OIDs you should really > start using the MIB files. What difference would it make? There would still be the same limit, and the performance when doing lots of snmp-based checks would be a lot worse, especially since Net-SNMP doesn't yet support pre-compiled MIBs so it has to parse and compile them all at each invocation. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw35w4ACgkQ6dZ+Kt5BchYqZACgz3hgtS6ia6BV6L4L5hB+gvFN oiEAn0aGXclfuxv956Sn7MFZznJoSofN =v72H -----END PGP SIGNATURE----- From william at leibzon.org Sat Jul 10 08:34:25 2010 From: william at leibzon.org (William Leibzon) Date: Fri, 9 Jul 2010 23:34:25 -0700 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: <4C37E714.3060105@aei.ca> References: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> <4C37B3D7.9090209@aei.ca> <4C37E714.3060105@aei.ca> Message-ID: On Fri, Jul 9, 2010 at 8:20 PM, Thomas Guyot-Sionnest wrote: >> To be fair, at the point you need that many OIDs you should really >> start using the MIB files. > > What difference would it make? There would still be the same limit, and > the performance when doing lots of snmp-based checks would be a lot > worse, especially since Net-SNMP doesn't yet support pre-compiled MIBs > so it has to parse and compile them all at each invocation. Thomas is right. Since chances of OID changing are close to none, you should use numbers or you can just assign oid number to some variable with proper name directly in your code. And for those who need better support there is snmptt: http://snmptt.sourceforge.net/ And perhaps we should increase default to 10 instead of 5, I've ran into that myself too. Would other people who want it and those who object please tell, so we could do a quick poll here. William From noreply at sourceforge.net Sat Jul 10 11:43:33 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 10 Jul 2010 09:43:33 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-3027760 ] check_sip problem Message-ID: Patches item #3027760, was opened at 2010-07-10 12:43 Message generated for change (Tracker Item Submitted) made by motiejusj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3027760&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Bugfix Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Motiejus Jak?tys (motiejusj) Assigned to: Nobody/Anonymous (nobody) Summary: check_sip problem Initial Comment: monitor:/usr/local/nagios/libexec# grep -r "use lib" . ./check_disk_smb:use lib "/usr/local/nagios/libexec" ; ./check_mailq:use lib "/usr/local/nagios/libexec" ; ./check_flexlm:use lib "/usr/local/nagios/libexec" ; ./check_ifstatus:use lib "/usr/local/nagios/libexec" ; ./check_breeze:use lib "/usr/local/nagios/libexec" ; ./check_file_age:use lib "/usr/local/nagios/libexec" ; ./check_sip:use lib "/usr/lib/nagios/plugins"; ////// This should be fixed ./check_snmp_storage.pl:use lib "/usr/local/nagios/libexec"; ./check_wave:use lib "/usr/local/nagios/libexec" ; ./check_rpc:use lib "/usr/local/nagios/libexec" ; ./check_ifoperstatus:use lib "/usr/local/nagios/libexec" ; ./check_ircd:use lib "/usr/local/nagios/libexec" ; When using check_sip, nagios returns (null).: Command: check_command check_sip! sip:nobody at 127.0.0.1 Output from capture.pl plugin using check_sip ------- 2010-6-10 12:2:48 ------ debugging cmd=[/usr/local/nagios/libexec/check_sip '-u' 'sip:nobody at 127.0.0.1' '-H' '192.168.41.6' '-w' '5'] output=[Can't locate utils.pm in @INC (@INC contains: /usr/lib/nagios/plugins /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/local/nagios/libexec/check_sip line 29. BEGIN failed--compilation aborted at /usr/local/nagios/libexec/check_sip line 29. ] retcode=2 Applying this trivial patch fixed the issue. Plugin version: 1.4.14 check_sip revision: 1.2 nagios version: 3.2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3027760&group_id=29880 From folkert at vanheusden.com Sat Jul 10 17:16:52 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 17:16:52 +0200 Subject: [Nagiosplug-devel] patch against check_procs Message-ID: <20100710151651.GI30421@belle.intranet.vanheusden.com> Hi, Here's a patch against check_procs. It makes it emit performancedata like other checks do. diff -uNrBbd nagios-plugins-1.4.14/plugins/check_procs.c nagios-plugins-1.4.14.new//plugins/check_procs.c --- nagios-plugins-1.4.14/plugins/check_procs.c 2009-02-20 00:55:23.000000000 +0100 +++ nagios-plugins-1.4.14.new//plugins/check_procs.c 2010-07-10 16:43:07.000000000 +0200 @@ -301,6 +301,8 @@ if ( verbose >= 1 && strcmp(fails,"") ) printf (" [%s]", fails); + printf ("|procs=%d", procs); + printf ("\n"); return result; } Folkert van Heusden p.s. check http://vanheusden.com/java/CoffeeSaint/ - a nagios status viewer for on large screens in your sysadmin room -- MultiTail ist eine flexible Applikation um Logfiles und Kommando Eingaben zu ?berpr?fen. Inkl. Filter, Farben, Zusammenf?hren, Ansichten etc. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From folkert at vanheusden.com Sat Jul 10 17:20:13 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 17:20:13 +0200 Subject: [Nagiosplug-devel] patch against check_ssh Message-ID: <20100710152013.GK30421@belle.intranet.vanheusden.com> Hi, Here's a patch against check_ssh. It makes it emit performancedata (latency) like other checks do. --- nagios-plugins-1.4.14/plugins/check_ssh.c 2008-11-30 22:23:18.000000000 +0100 +++ nagios-plugins-1.4.14.new/plugins/check_ssh.c 2010-07-10 17:14:01.000000000 +0200 @@ -198,6 +198,18 @@ } +double +get_ts (void) +{ + struct timeval ts; + struct timezone tz; + + gettimeofday(&ts, &tz); + + return (((double)ts.tv_sec) + ((double)ts.tv_usec)/1000000.0); +} + + /************************************************************************ * * Try to connect to SSH server at specified server and port @@ -215,6 +227,7 @@ char *ssh_proto = NULL; char *ssh_server = NULL; static char *rev_no = VERSION; + double start = get_ts(); result = my_tcp_connect (haddr, hport, &sd); @@ -251,8 +264,10 @@ } printf - (_("SSH OK - %s (protocol %s)\n"), + (_("SSH OK - %s (protocol %s)"), ssh_server, ssh_proto); + + printf ("|latency=%f\n", get_ts() - start); close(sd); exit (STATE_OK); } Folkert van Heusden -- Looking for a cheap but fast webhoster with an excellent helpdesk? http://keetweej.vanheusden.com/redir.php?id=1001 ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From dermoth at aei.ca Sat Jul 10 21:07:05 2010 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Sat, 10 Jul 2010 15:07:05 -0400 Subject: [Nagiosplug-devel] patch against check_ssh In-Reply-To: <20100710152013.GK30421@belle.intranet.vanheusden.com> References: <20100710152013.GK30421@belle.intranet.vanheusden.com> Message-ID: <4C38C4D9.2050209@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10-07-10 11:20 AM, folkert wrote: > Hi, > > Here's a patch against check_ssh. It makes it emit performancedata > (latency) like other checks do. Thanks, however it will have to use the exported perfdata functions, which won't be very hard to do anyway. See check_tcp as an example (look for fperfdata). You may want to use deltime too from utils.h. Using the provided functions helps keeping all plugins to a standard level and will greatly help conversion to a plugins library if/when we manage to code it :) Also I think "time=" would be a more appropriate label; most other plugins uses it for the latency and some tools might better recognise it. I will commit it if you can fix the above issue. Thanks! - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw4xM0ACgkQ6dZ+Kt5BchaFCQCgq9FAT4UyU5M5Qi6kewvcVOeG VcIAnjiHptqAI4Y4K6JBcyvAWiP8uAQ/ =Yc2R -----END PGP SIGNATURE----- From folkert at vanheusden.com Sat Jul 10 21:20:12 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 21:20:12 +0200 Subject: [Nagiosplug-devel] patch against check_ssh In-Reply-To: <4C38C4D9.2050209@aei.ca> References: <20100710152013.GK30421@belle.intranet.vanheusden.com> <4C38C4D9.2050209@aei.ca> Message-ID: <20100710192011.GO30421@belle.intranet.vanheusden.com> > > Here's a patch against check_ssh. It makes it emit performancedata > > (latency) like other checks do. > > Thanks, however it will have to use the exported perfdata functions, > which won't be very hard to do anyway. See check_tcp as an example (look > for fperfdata). You may want to use deltime too from utils.h. > Using the provided functions helps keeping all plugins to a standard > level and will greatly help conversion to a plugins library if/when we > manage to code it :) > Also I think "time=" would be a more appropriate label; most other > plugins uses it for the latency and some tools might better recognise it. > I will commit it if you can fix the above issue. Hi, Here's the patch again for check_ssh. check_procs will be in an other mail --- nagios-plugins-1.4.14/plugins/check_ssh.c 2008-11-30 22:23:18.000000000 +0100 +++ nagios-plugins-1.4.14.new/plugins/check_ssh.c 2010-07-10 21:18:12.000000000 +0200 @@ -215,6 +215,8 @@ char *ssh_proto = NULL; char *ssh_server = NULL; static char *rev_no = VERSION; + struct timeval start; + gettimeofday (&start, NULL); result = my_tcp_connect (haddr, hport, &sd); @@ -251,8 +253,16 @@ } printf - (_("SSH OK - %s (protocol %s)\n"), + (_("SSH OK - %s (protocol %s)"), ssh_server, ssh_proto); + + printf("|%s\n", + fperfdata ("time", delta_time(start), "s", + FALSE, 0, + FALSE, 0, + FALSE, 0, + FALSE, 0) + ); close(sd); exit (STATE_OK); } Folkert van Heusden -- MultiTail er et flexible tool for ? kontrolere Logfiles og commandoer. Med filtrer, farger, sammenf?ringer, forskeliger ansikter etc. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From folkert at vanheusden.com Sat Jul 10 21:22:11 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 21:22:11 +0200 Subject: [Nagiosplug-devel] patch against check_ssh In-Reply-To: <4C38C4D9.2050209@aei.ca> References: <20100710152013.GK30421@belle.intranet.vanheusden.com> <4C38C4D9.2050209@aei.ca> Message-ID: <20100710192210.GP30421@belle.intranet.vanheusden.com> check_procs patch --- nagios-plugins-1.4.14/plugins/check_procs.c 2009-02-20 00:55:23.000000000 +0100 +++ nagios-plugins-1.4.14.new/plugins/check_procs.c 2010-07-10 21:21:21.000000000 +0200 @@ -301,6 +301,14 @@ if ( verbose >= 1 && strcmp(fails,"") ) printf (" [%s]", fails); + printf("|%s", + fperfdata ("procs", procs, "", + FALSE, 0, + FALSE, 0, + FALSE, 0, + FALSE, 0) + ); + printf ("\n"); return result; } Folkert van Heusden -- MultiTail is een flexibele tool voor het volgen van logfiles en uitvoer van commando's. Filteren, van kleur voorzien, mergen, 'diff-view', etc. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From folkert at vanheusden.com Sat Jul 10 21:24:31 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 21:24:31 +0200 Subject: [Nagiosplug-devel] patch against check_ssh In-Reply-To: <20100710192210.GP30421@belle.intranet.vanheusden.com> References: <20100710152013.GK30421@belle.intranet.vanheusden.com> <4C38C4D9.2050209@aei.ca> <20100710192210.GP30421@belle.intranet.vanheusden.com> Message-ID: <20100710192431.GQ30421@belle.intranet.vanheusden.com> Wrong: using fperfdata, should be perfdata. Fixed: --- nagios-plugins-1.4.14/plugins/check_procs.c 2009-02-20 00:55:23.000000000 +0100 +++ nagios-plugins-1.4.14.new/plugins/check_procs.c 2010-07-10 21:23:48.000000000 +0200 @@ -301,6 +301,14 @@ if ( verbose >= 1 && strcmp(fails,"") ) printf (" [%s]", fails); + printf("|%s", + perfdata ("procs", procs, "", + FALSE, 0, + FALSE, 0, + FALSE, 0, + FALSE, 0) + ); + printf ("\n"); return result; } On Sat, Jul 10, 2010 at 09:22:10PM +0200, folkert wrote: > check_procs patch > > --- nagios-plugins-1.4.14/plugins/check_procs.c 2009-02-20 00:55:23.000000000 +0100 > +++ nagios-plugins-1.4.14.new/plugins/check_procs.c 2010-07-10 21:21:21.000000000 +0200 > @@ -301,6 +301,14 @@ > if ( verbose >= 1 && strcmp(fails,"") ) > printf (" [%s]", fails); > > + printf("|%s", > + fperfdata ("procs", procs, "", > + FALSE, 0, > + FALSE, 0, > + FALSE, 0, > + FALSE, 0) > + ); > + > printf ("\n"); > return result; > } > > Folkert van Heusden > > -- > MultiTail is een flexibele tool voor het volgen van logfiles en > uitvoer van commando's. Filteren, van kleur voorzien, mergen, > 'diff-view', etc. http://www.vanheusden.com/multitail/ > ---------------------------------------------------------------------- > Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com Folkert van Heusden -- MultiTail na wan makriki wrokosani fu tan luku den logfile nanga san den commando spiti puru. Piki puru spesrutu sani, wroko nanga difrenti kroru, tya kon makandra, nanga wan lo moro. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From folkert at vanheusden.com Sat Jul 10 21:24:58 2010 From: folkert at vanheusden.com (folkert) Date: Sat, 10 Jul 2010 21:24:58 +0200 Subject: [Nagiosplug-devel] patch against check_ssh In-Reply-To: <20100710192210.GP30421@belle.intranet.vanheusden.com> References: <20100710152013.GK30421@belle.intranet.vanheusden.com> <4C38C4D9.2050209@aei.ca> <20100710192210.GP30421@belle.intranet.vanheusden.com> Message-ID: <20100710192458.GR30421@belle.intranet.vanheusden.com> check_apt: --- nagios-plugins-1.4.14/plugins/check_apt.c 2008-11-30 22:23:18.000000000 +0100 +++ nagios-plugins-1.4.14.new/plugins/check_apt.c 2010-07-10 21:23:51.000000000 +0200 @@ -111,7 +111,7 @@ result = max_state(result, STATE_OK); } - printf(_("APT %s: %d packages available for %s (%d critical updates). %s%s%s%s\n"), + printf(_("APT %s: %d packages available for %s (%d critical updates). %s%s%s%s"), state_text(result), packages_available, (upgrade==DIST_UPGRADE)?"dist-upgrade":"upgrade", @@ -122,6 +122,19 @@ (stderr_warning||exec_warning)?". run with -v for information.":"" ); + printf("|%s %s\n", + perfdata ("available", packages_available, "", + FALSE, 0, + FALSE, 0, + FALSE, 0, + FALSE, 0), + perfdata ("critical", sec_count, "", + FALSE, 0, + FALSE, 0, + FALSE, 0, + FALSE, 0) + ); + return result; } Folkert van Heusden -- Feeling generous? -> http://www.vanheusden.com/wishlist.php ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From nagiosplug-devel at lusis.org Sun Jul 11 04:51:56 2010 From: nagiosplug-devel at lusis.org (John Vincent) Date: Sat, 10 Jul 2010 22:51:56 -0400 Subject: [Nagiosplug-devel] check_snmp OID numbers limited? In-Reply-To: References: <8076CB8628164B469C12FD2BF895579D09543864@TUS1XCHCLUPIN13.enterprise.veritas.com> <4C37B3D7.9090209@aei.ca> <4C37E714.3060105@aei.ca> Message-ID: On Sat, Jul 10, 2010 at 2:34 AM, William Leibzon wrote: > On Fri, Jul 9, 2010 at 8:20 PM, Thomas Guyot-Sionnest wrote: > >>> To be fair, at the point you need that many OIDs you should really >>> start using the MIB files. >> >> What difference would it make? There would still be the same limit, and >> the performance when doing lots of snmp-based checks would be a lot >> worse, especially since Net-SNMP doesn't yet support pre-compiled MIBs >> so it has to parse and compile them all at each invocation. > > Thomas is right. Since chances of OID changing are close to none, you > should use numbers or you can just assign oid number to some variable > with proper name directly in your code. And for those who need better > support there is snmptt: > ?http://snmptt.sourceforge.net/ > > And perhaps we should increase default to 10 instead of 5, I've ran > into that myself too. Would other people who want it and those who > object please tell, so we could do a quick poll here. > > William Those are fair statements. I was thinking more along the lines of readability and check command length. I can't remember if there was a maxlength issue anymore with a command object. I also second snmptt. From christian.masopust at siemens.com Sun Jul 11 16:25:17 2010 From: christian.masopust at siemens.com (Masopust, Christian) Date: Sun, 11 Jul 2010 16:25:17 +0200 Subject: [Nagiosplug-devel] check_disk Problem with Solaris Zones Message-ID: <60721B67EAF0994EAFFB561767B7001404C50B7B@nets13ha.ww300.siemens.net> > Hi, > > we have with a strange problem with check_disk combined with solaris zones. > > check_disk running on the global zone sees all the filesystems inside the > zones. if there are two equal mountpoints inside a zone and the global > zone, we run into this problem. > > check_disk thinks, that it has already seen the filesystem and overwrites > the one found first with the second one. without -A everything runs fine > and check_disk sees both filesystems. > > e.g. > > # df -h > Filesystem size used avail capacity Mounted on > ... > /dev/md/dsk/d5 62G 34G 27G 56% /zones > /dev/md/dsk/d30 134G 102G 32G 77% /abc > ... > > # zonecfg -z xyz info > ... > fs: > dir: /abc > special: /abc > raw not specified > type: lofs > options: [] > ... > > # /tmp/check_disk -w 20% -c 10% > DISK OK - free space: ... /zones 28134 MB (44% inode=87%); /abc 32768 MB > (23% inode=76%); ... /zones/xyz/root/abc 32768 MB (23% inode=76%); ... > > # /tmp/check_disk -w 20% -c 10% -A > DISK OK - free space: ... /zones 28134 MB (44% inode=87%); > /zones/xyz/root/abc 32736 MB (23% inode=76%); ... > > If i want to filter out the zone filesystems with "-i /zones/" i need -A > before to explicitly select all filesystems. that meens, that my > filesystem from the global zone is "overwritten" with my zone filesystem > and filtered out with "-i /zones/" :-( > > what's the right way to fix this problem? > > best regards, > michael Hi all, I have the same problem here on my Solaris 10. Is there any news about this problem? Or probably a solution? :-)) Thanks, Christian ___________________________________________________________ Christian Masopust SIEMENS AG SIS SDE SVI CON IPB Tel: +43 (0) 5 1707 26866 E-mail: christian.masopust at siemens.com Addr: Austria, 1210 Vienna, Siemensstra?e 90-92, B. 33, Rm. 243 Leader of the RUGA Firma: Siemens Aktiengesellschaft ?sterreich, Rechtsform: Aktiengesellschaft, Sitz: Wien, Firmenbuchnummer: FN 60562 m, Firmenbuchgericht: Handelsgericht Wien, DVR 0001708 ___________________________________________________________ From simeon_zaharici at yahoo.com Mon Jul 12 15:58:33 2010 From: simeon_zaharici at yahoo.com (Simeon Zaharici) Date: Mon, 12 Jul 2010 06:58:33 -0700 (PDT) Subject: [Nagiosplug-devel] check_procs and very long process names Message-ID: <769383.20153.qm@web55908.mail.re3.yahoo.com> Hi I have to monitor a few servers that have unusually long process names ranging between 30 and 46 characters. From what I see check_procs works with procs with up to 16 characters.I tried to edit the source code to allow for longer names but did not manage to do that correctly :D, can you guys help ? Thanks,Simeon? -------------- next part -------------- An HTML attachment was scrubbed... URL: From simeon_zaharici at yahoo.com Mon Jul 12 17:31:28 2010 From: simeon_zaharici at yahoo.com (Simeon Zaharici) Date: Mon, 12 Jul 2010 08:31:28 -0700 (PDT) Subject: [Nagiosplug-devel] check_procs and very long process names In-Reply-To: <769383.20153.qm@web55908.mail.re3.yahoo.com> Message-ID: <714218.94076.qm@web55906.mail.re3.yahoo.com> Hi I see that in fact the limit comes from the output of ps axwo 'stat uid pid ppid vsz rss pcpu comm args ' and got around it by monitoring the args field Thanks --- On Mon, 7/12/10, Simeon Zaharici wrote: From: Simeon Zaharici Subject: [Nagiosplug-devel] check_procs and very long process names To: nagiosplug-devel at lists.sourceforge.net Received: Monday, July 12, 2010, 6:28 PM Hi I have to monitor a few servers that have unusually long process names ranging between 30 and 46 characters. From what I see check_procs works with procs with up to 16 characters.I tried to edit the source code to allow for longer names but did not manage to do that correctly :D, can you guys help ? Thanks,Simeon? -----Inline Attachment Follows----- ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first -----Inline Attachment Follows----- _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Tue Jul 13 15:29:46 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 13 Jul 2010 13:29:46 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3028955 ] check_users 1.4.14 always reports 1user connected in french Message-ID: Bugs item #3028955, was opened at 2010-07-13 15:29 Message generated for change (Tracker Item Submitted) made by julien_leveque You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028955&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: julien_leveque (julien_leveque) Assigned to: Nobody/Anonymous (nobody) Summary: check_users 1.4.14 always reports 1user connected in french Initial Comment: When language is french , check_users always reports 1 user connected even if there's more or less than one user connected. Bug is at least for 1.4.14 and 1.4.12 on RHEL 5 x64 and debian lenny x64 (here with RHEL5 x64) servename:~# /usr/lib/nagios/plugins/check_users --help| grep nagios-plugins check_users v1.4.14 (nagios-plugins 1.4.14) servername]# file /usr/lib/nagios/plugins/check_users /usr/lib/nagios/plugins/check_users: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped servername:~# env| grep LANG LANG=fr_FR.UTF-8 servername:~# w|wc -l 12 servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 UTILISATEURS OK - 1 utilisateurs actuellement connect?s sur |users=1;500;600;0 servername:~# LANG=en servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 USERS OK - 10 users currently logged in |users=10;500;600;0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028955&group_id=29880 From noreply at sourceforge.net Tue Jul 13 16:05:27 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 13 Jul 2010 14:05:27 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3028969 ] check_users 1.4.14 always reports 1user connected in french Message-ID: Bugs item #3028969, was opened at 2010-07-13 16:05 Message generated for change (Tracker Item Submitted) made by julien_leveque You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028969&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: julien_leveque (julien_leveque) Assigned to: Nobody/Anonymous (nobody) Summary: check_users 1.4.14 always reports 1user connected in french Initial Comment: When language is french , check_users always reports 1 user connected even if there's more or less than one user connected. Bug is at least for 1.4.14 and 1.4.12 on RHEL 5 x64 and debian lenny x64 (here with RHEL5 x64) servename:~# /usr/lib/nagios/plugins/check_users --help| grep nagios-plugins check_users v1.4.14 (nagios-plugins 1.4.14) servername]# file /usr/lib/nagios/plugins/check_users /usr/lib/nagios/plugins/check_users: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped servername:~# env| grep LANG LANG=fr_FR.UTF-8 servername:~# w|wc -l 12 servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 UTILISATEURS OK - 1 utilisateurs actuellement connect?s sur |users=1;500;600;0 servername:~# LANG=en servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 USERS OK - 10 users currently logged in |users=10;500;600;0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028969&group_id=29880 From b_ibtihel at yahoo.fr Tue Jul 13 17:02:16 2010 From: b_ibtihel at yahoo.fr (ibtihel ben brahem) Date: Tue, 13 Jul 2010 15:02:16 +0000 (GMT) Subject: [Nagiosplug-devel] Tr : plugin check_squid.pl Message-ID: <445586.92778.qm@web28207.mail.ukl.yahoo.com> ----- Message transf?r? ---- De : ibtihel ben brahem ? : nagiosplug-devel at lists.sourceforge.net Envoy? le : Mar 13 juillet 2010, 16h 30min 23s Objet : plugin check_squid.pl Bonjour svp je vous ?crit en urgence car j'ai t?l?charg? le plugin check_squid.pl v0.1 (nagios-plugins 1.4.12) Mais lorsque je fais le test avec cette commande /usr/lib/nagios/plugins/check_squid.pl -u http://www.google.fr -p spar-proxy.domaine -l 800 il m'affiche l'erreur suivante :Use -h for more info J'ai beau cherch? mais vainement svp aidez moi est ce que il y a un bug avec cette version ou incompatibilit? avec la version de nagios que j'utilise ? J'attends votre r?ponse svp. Bien Cordialement Ibtihel -------------- next part -------------- An HTML attachment was scrubbed... URL: From gfilion at revolutionlinux.com Thu Jul 15 16:01:31 2010 From: gfilion at revolutionlinux.com (Gabriel Filion) Date: Thu, 15 Jul 2010 10:01:31 -0400 Subject: [Nagiosplug-devel] Tr : plugin check_squid.pl In-Reply-To: <445586.92778.qm@web28207.mail.ukl.yahoo.com> References: <445586.92778.qm@web28207.mail.ukl.yahoo.com> Message-ID: <4C3F14BB.3050001@revolutionlinux.com> Hello, If you don't have an answer yet, I guess it could mean that the official language on this list is English and that people didn't understand your message. I don't know much about this particular plugin but I'll translate it (inline) for you so that other people can help you out. For my first queue on this: the message you get means that you're probably using the wrong syntax for calling the command. Use only the -h option to see how exactly the plugin needs to be called. Also, if you're executing the command in a terminal, then you are not going though Nagios and the version of Nagios doesn't have a role in this. On 10-07-13 11:02 AM, ibtihel ben brahem wrote: > ----- Message transf?r? ---- > *De :* ibtihel ben brahem > *? :* nagiosplug-devel at lists.sourceforge.net > *Envoy? le :* Mar 13 juillet 2010, 16h 30min 23s > *Objet :* plugin check_squid.pl > > Bonjour > svp je vous ?crit en urgence car j'ai t?l?charg? le plugin > check_squid.pl v0.1 (nagios-plugins 1.4.12) > Hi I send a call for help on this list because I downloaded the plugin "check_squid.pl" v0.1 (from nagios-plugins version 1.4.12) > Mais lorsque je fais le test avec cette commande > /usr/lib/nagios/plugins/check_squid.pl -u http://www.google.fr -p > spar-proxy.domaine -l 800 > But when I test the following command: /usr/lib/nagios/plugins/check_squid.pl -u http://www.google.fr -p spar-proxy.domaine -l 800 > il m'affiche l'erreur suivante :Use -h for more info > I get the error: Use -h for more info > J'ai beau cherch? mais vainement > svp aidez moi est ce que il y a un bug avec cette version ou > incompatibilit? avec la version de nagios que j'utilise ? I searched but didn't find the cause of the problem. please help me out. is this a bug with the version I use or is it an incompatibility with the nagios version I use? > J'attends votre r?ponse svp. > > Bien Cordialement > Ibtihel > Si tu ne comprends pas ma r?ponse en anglais, r?ponds-moi personnellement et j'en ferai la traduction. Si tu as d'autres questions, assure-toi d'inclure la liste de diffusion et d'?crire les questions en anglais. -- Gabriel Filion From gfilion at revolutionlinux.com Thu Jul 15 16:55:00 2010 From: gfilion at revolutionlinux.com (Gabriel Filion) Date: Thu, 15 Jul 2010 10:55:00 -0400 Subject: [Nagiosplug-devel] Re : Tr : plugin check_squid.pl In-Reply-To: <594744.9597.qm@web28214.mail.ukl.yahoo.com> References: <445586.92778.qm@web28207.mail.ukl.yahoo.com> <4C3F14BB.3050001@revolutionlinux.com> <594744.9597.qm@web28214.mail.ukl.yahoo.com> Message-ID: <4C3F2144.3030505@revolutionlinux.com> [Restoring CC to the list so that the discussion can go on publicly] On 10-07-15 10:14 AM, ibtihel ben brahem wrote: > Hi Gabriel, > > Thank you very much for your answer.I have always the same problem and i > used -h to see how to do the check.I 'm sure that the problem is not > with the command itself because the syntaxe is all wright.I don't know > if there is a bug any way with the plugin?Can you help me pleaze? I need > your intervention ASAP. > I can't really help you further on this issue. I currently have access to nagios-plugins 1.4.11 packages only on the production servers I manage, so I don't even see the check_squid script :\ I'll try and install the plugins on my laptop later to check it out some more. In the meantime, maybe someone else with more knowledge of the script can give some advice? > Best regards > Ibtihel > > ------------------------------------------------------------------------ > *De :* Gabriel Filion > *? :* Nagios Plugin Development Mailing List > > *Cc :* ibtihel ben brahem > *Envoy? le :* Jeu 15 juillet 2010, 16h 01min 31s > *Objet :* Re: [Nagiosplug-devel] Tr : plugin check_squid.pl > > Hello, > > If you don't have an answer yet, I guess it could mean that the official > language on this list is English and that people didn't understand your > message. I don't know much about this particular plugin but I'll > translate it (inline) for you so that other people can help you out. > > For my first queue on this: the message you get means that you're > probably using the wrong syntax for calling the command. Use only the -h > option to see how exactly the plugin needs to be called. > Also, if you're executing the command in a terminal, then you are not > going though Nagios and the version of Nagios doesn't have a role in this. > > On 10-07-13 11:02 AM, ibtihel ben brahem wrote: >> ----- Message transf?r? ---- >> *De :* ibtihel ben brahem > >> *? :* nagiosplug-devel at lists.sourceforge.net > >> *Envoy? le :* Mar 13 juillet 2010, 16h 30min 23s >> *Objet :* plugin check_squid.pl >> >> Bonjour >> svp je vous ?crit en urgence car j'ai t?l?charg? le plugin >> check_squid.pl v0.1 (nagios-plugins 1.4.12) >> > > Hi > I send a call for help on this list because I downloaded the plugin > "check_squid.pl" v0.1 (from nagios-plugins version 1.4.12) > >> Mais lorsque je fais le test avec cette commande >> /usr/lib/nagios/plugins/check_squid.pl -u http://www.google.fr -p >> spar-proxy.domaine -l 800 >> > > But when I test the following command: > > /usr/lib/nagios/plugins/check_squid.pl -u http://www.google.fr -p > spar-proxy.domaine -l 800 > >> il m'affiche l'erreur suivante :Use -h for more info >> > > I get the error: Use -h for more info > >> J'ai beau cherch? mais vainement >> svp aidez moi est ce que il y a un bug avec cette version ou >> incompatibilit? avec la version de nagios que j'utilise ? > > I searched but didn't find the cause of the problem. > please help me out. is this a bug with the version I use or is it an > incompatibility with the nagios version I use? > >> J'attends votre r?ponse svp. >> >> Bien Cordialement >> Ibtihel >> > > Si tu ne comprends pas ma r?ponse en anglais, r?ponds-moi > personnellement et j'en ferai la traduction. Si tu as d'autres > questions, assure-toi d'inclure la liste de diffusion et d'?crire les > questions en anglais. > -- Gabriel Filion From noreply at sourceforge.net Mon Jul 19 01:22:44 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 18 Jul 2010 23:22:44 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-19 01:22 Message generated for change (Tracker Item Submitted) made by tarvin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From christian.masopust at siemens.com Wed Jul 21 17:53:16 2010 From: christian.masopust at siemens.com (Masopust, Christian) Date: Wed, 21 Jul 2010 17:53:16 +0200 Subject: [Nagiosplug-devel] check_disk Problem with Solaris Zones In-Reply-To: <60721B67EAF0994EAFFB561767B7001404C50B7B@nets13ha.ww300.siemens.net> References: <60721B67EAF0994EAFFB561767B7001404C50B7B@nets13ha.ww300.siemens.net> Message-ID: <60721B67EAF0994EAFFB561767B7001404C91686@nets13ha.ww300.siemens.net> probably noone else has already got this problem.... anyway, I found a solution (or workaround) for that... when running check_disk locally in such a configuration then I can simple use the "-M" to check_disk. but when using "-M" when running check_disk via nrpe it again fails.... so I solved this by changing owner of check_disk to root and set the s-bit christian > > Hi, > > > > we have with a strange problem with check_disk combined > with solaris zones. > > > > check_disk running on the global zone sees all the > filesystems inside the > > zones. if there are two equal mountpoints inside a zone and > the global > > zone, we run into this problem. > > > > check_disk thinks, that it has already seen the filesystem > and overwrites > > the one found first with the second one. without -A > everything runs fine > > and check_disk sees both filesystems. > > > > e.g. > > > > # df -h > > Filesystem size used avail capacity Mounted on > > ... > > /dev/md/dsk/d5 62G 34G 27G 56% /zones > > /dev/md/dsk/d30 134G 102G 32G 77% /abc > > ... > > > > # zonecfg -z xyz info > > ... > > fs: > > dir: /abc > > special: /abc > > raw not specified > > type: lofs > > options: [] > > ... > > > > # /tmp/check_disk -w 20% -c 10% > > DISK OK - free space: ... /zones 28134 MB (44% inode=87%); > /abc 32768 MB > > (23% inode=76%); ... /zones/xyz/root/abc 32768 MB (23% > inode=76%); ... > > > > # /tmp/check_disk -w 20% -c 10% -A > > DISK OK - free space: ... /zones 28134 MB (44% inode=87%); > > /zones/xyz/root/abc 32736 MB (23% inode=76%); ... > > > > If i want to filter out the zone filesystems with "-i > /zones/" i need -A > > before to explicitly select all filesystems. that meens, that my > > filesystem from the global zone is "overwritten" with my > zone filesystem > > and filtered out with "-i /zones/" :-( > > > > what's the right way to fix this problem? > > > > best regards, > > michael > > Hi all, > > I have the same problem here on my Solaris 10. Is there any news > about this problem? Or probably a solution? :-)) > > Thanks, > Christian > > > ___________________________________________________________ > > Christian Masopust > > SIEMENS AG SIS SDE SVI CON IPB > Tel: +43 (0) 5 1707 26866 > E-mail: christian.masopust at siemens.com > Addr: Austria, 1210 Vienna, Siemensstra?e 90-92, B. > 33, Rm. 243 > > Leader of the RUGA > > > Firma: Siemens Aktiengesellschaft ?sterreich, > Rechtsform: Aktiengesellschaft, > Sitz: Wien, Firmenbuchnummer: FN 60562 m, > Firmenbuchgericht: Handelsgericht Wien, DVR 0001708 > ___________________________________________________________ > > > > > -------------------------------------------------------------- > ---------------- > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > From noreply at sourceforge.net Wed Jul 21 18:32:08 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Jul 2010 16:32:08 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-19 01:22 Message generated for change (Comment added) made by thomas_gelf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-21 18:32 Message: Hi Troels, I stumbled over your bug report - and I guess your ntpdate is the one to blame for this. What ntpdate version are you currently using? It seems that this issue has been fixed somewhere by mid-2009. Before this those tools just checked whether you have IPv6 support - right now they also verify whether your IPv6-Connectivity will work. As a workaround you can pass "-4" as an additional parameter to your call to check_ntp_time, that should help. I'd therefore suggest to close this bug report - check_ntp_time is IMO not the right place to fix this. Regards, Thomas Gelf NB: If I'm wrong please feel free to correct me! As this is the very first time I ever gave a closer look to a a Nagios component, you shouldn't trust my words at all ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From noreply at sourceforge.net Wed Jul 21 22:23:05 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Jul 2010 20:23:05 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-19 01:22 Message generated for change (Comment added) made by tarvin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- >Comment By: Troels Arvin (tarvin) Date: 2010-07-21 22:23 Message: Thomas: check_ntp_time doesn't call my system's ntpdate. check_ntp_time is a binary - not a script. And it only links to the most basic libraries (i.e.: it doesn't link to any NTP-related libraries). The code for the plugin: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins/check_ntp_time.c ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-21 18:32 Message: Hi Troels, I stumbled over your bug report - and I guess your ntpdate is the one to blame for this. What ntpdate version are you currently using? It seems that this issue has been fixed somewhere by mid-2009. Before this those tools just checked whether you have IPv6 support - right now they also verify whether your IPv6-Connectivity will work. As a workaround you can pass "-4" as an additional parameter to your call to check_ntp_time, that should help. I'd therefore suggest to close this bug report - check_ntp_time is IMO not the right place to fix this. Regards, Thomas Gelf NB: If I'm wrong please feel free to correct me! As this is the very first time I ever gave a closer look to a a Nagios component, you shouldn't trust my words at all ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From noreply at sourceforge.net Wed Jul 21 23:34:44 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 21 Jul 2010 21:34:44 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-19 01:22 Message generated for change (Comment added) made by tarvin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- >Comment By: Troels Arvin (tarvin) Date: 2010-07-21 23:34 Message: By the way: I have observed this problem on Red Hat Enterprise Linux 5.5 and Fedora Linux 13. ---------------------------------------------------------------------- Comment By: Troels Arvin (tarvin) Date: 2010-07-21 22:23 Message: Thomas: check_ntp_time doesn't call my system's ntpdate. check_ntp_time is a binary - not a script. And it only links to the most basic libraries (i.e.: it doesn't link to any NTP-related libraries). The code for the plugin: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins/check_ntp_time.c ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-21 18:32 Message: Hi Troels, I stumbled over your bug report - and I guess your ntpdate is the one to blame for this. What ntpdate version are you currently using? It seems that this issue has been fixed somewhere by mid-2009. Before this those tools just checked whether you have IPv6 support - right now they also verify whether your IPv6-Connectivity will work. As a workaround you can pass "-4" as an additional parameter to your call to check_ntp_time, that should help. I'd therefore suggest to close this bug report - check_ntp_time is IMO not the right place to fix this. Regards, Thomas Gelf NB: If I'm wrong please feel free to correct me! As this is the very first time I ever gave a closer look to a a Nagios component, you shouldn't trust my words at all ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From noreply at sourceforge.net Thu Jul 22 10:06:19 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 22 Jul 2010 08:06:19 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-19 01:22 Message generated for change (Comment added) made by thomas_gelf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-22 10:06 Message: Sorry, I confused it with check_ntp.pl: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins-scripts/check_ntp.pl Using "-4" would probably help in your case too, but check_ntp_time.c should definitively be fixed. ---------------------------------------------------------------------- Comment By: Troels Arvin (tarvin) Date: 2010-07-21 23:34 Message: By the way: I have observed this problem on Red Hat Enterprise Linux 5.5 and Fedora Linux 13. ---------------------------------------------------------------------- Comment By: Troels Arvin (tarvin) Date: 2010-07-21 22:23 Message: Thomas: check_ntp_time doesn't call my system's ntpdate. check_ntp_time is a binary - not a script. And it only links to the most basic libraries (i.e.: it doesn't link to any NTP-related libraries). The code for the plugin: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins/check_ntp_time.c ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-21 18:32 Message: Hi Troels, I stumbled over your bug report - and I guess your ntpdate is the one to blame for this. What ntpdate version are you currently using? It seems that this issue has been fixed somewhere by mid-2009. Before this those tools just checked whether you have IPv6 support - right now they also verify whether your IPv6-Connectivity will work. As a workaround you can pass "-4" as an additional parameter to your call to check_ntp_time, that should help. I'd therefore suggest to close this bug report - check_ntp_time is IMO not the right place to fix this. Regards, Thomas Gelf NB: If I'm wrong please feel free to correct me! As this is the very first time I ever gave a closer look to a a Nagios component, you shouldn't trust my words at all ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From holger at CIS.FU-Berlin.DE Thu Jul 22 12:04:24 2010 From: holger at CIS.FU-Berlin.DE (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Thu, 22 Jul 2010 12:04:24 +0200 Subject: [Nagiosplug-devel] New release planned on Tuesday Message-ID: <20100722100423.GA7987078@CIS.FU-Berlin.DE> As there are lots of new bug fixes and enhancements in our Git repository, we thought it's time for a new release. The idea is to cut it on Tuesday. Let us know if there is anything that *must* go in before the release. Holger From noreply at sourceforge.net Tue Jul 27 22:17:53 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Jul 2010 20:17:53 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3028969 ] check_users 1.4.14 always reports 1user connected in french Message-ID: Bugs item #3028969, was opened at 2010-07-13 15:05 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028969&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: julien_leveque (julien_leveque) Assigned to: Nobody/Anonymous (nobody) Summary: check_users 1.4.14 always reports 1user connected in french Initial Comment: When language is french , check_users always reports 1 user connected even if there's more or less than one user connected. Bug is at least for 1.4.14 and 1.4.12 on RHEL 5 x64 and debian lenny x64 (here with RHEL5 x64) servename:~# /usr/lib/nagios/plugins/check_users --help| grep nagios-plugins check_users v1.4.14 (nagios-plugins 1.4.14) servername]# file /usr/lib/nagios/plugins/check_users /usr/lib/nagios/plugins/check_users: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped servername:~# env| grep LANG LANG=fr_FR.UTF-8 servername:~# w|wc -l 12 servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 UTILISATEURS OK - 1 utilisateurs actuellement connect?s sur |users=1;500;600;0 servername:~# LANG=en servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 USERS OK - 10 users currently logged in |users=10;500;600;0 ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2010-07-27 21:17 Message: Closing as a duplicate of 3028955 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028969&group_id=29880 From noreply at sourceforge.net Tue Jul 27 22:22:18 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Jul 2010 20:22:18 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3028955 ] check_users 1.4.14 always reports 1user connected in french Message-ID: Bugs item #3028955, was opened at 2010-07-13 14:29 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028955&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: julien_leveque (julien_leveque) Assigned to: Nobody/Anonymous (nobody) Summary: check_users 1.4.14 always reports 1user connected in french Initial Comment: When language is french , check_users always reports 1 user connected even if there's more or less than one user connected. Bug is at least for 1.4.14 and 1.4.12 on RHEL 5 x64 and debian lenny x64 (here with RHEL5 x64) servename:~# /usr/lib/nagios/plugins/check_users --help| grep nagios-plugins check_users v1.4.14 (nagios-plugins 1.4.14) servername]# file /usr/lib/nagios/plugins/check_users /usr/lib/nagios/plugins/check_users: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped servername:~# env| grep LANG LANG=fr_FR.UTF-8 servername:~# w|wc -l 12 servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 UTILISATEURS OK - 1 utilisateurs actuellement connect?s sur |users=1;500;600;0 servername:~# LANG=en servername:~# /usr/lib/nagios/plugins/check_users -w500 -c600 USERS OK - 10 users currently logged in |users=10;500;600;0 ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2010-07-27 21:22 Message: Julien, I'm assuming who is defined as /usr/bin/who by configure. What is the output of: LANG=fr_FR.UTF-8 /usr/bin/who LANG=en /usr/bin/who LANG=C /usr/bin/who ? Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3028955&group_id=29880 From noreply at sourceforge.net Tue Jul 27 22:28:32 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Jul 2010 20:28:32 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2982717 ] configure script doesn't have --disable-redhat-pthread Message-ID: Bugs item #2982717, was opened at 2010-04-06 17:00 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2982717&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Compilation Group: None >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: Martin Melin (martinmop5) Assigned to: Nobody/Anonymous (nobody) Summary: configure script doesn't have --disable-redhat-pthread Initial Comment: This FAQ http://nagiosplugins.org/faq/compile/configure_appears_to_hang refers to a --disable-redhat-pthread option to configure to disable the pthread test entirely, but configure's help output does not mention this option and as far as I can tell from the source the option does not have any effect. Version used for verification: nagios-plugins-HEAD.tar.gz today at 5 PM CEST -> nagios-plugins-1.4.14-69-gfe1c ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2010-07-27 21:28 Message: Martin, Thanks for report. Yes, there is no --disable-redhat-pthread option. I guess it should just either do the test or set the workaround, so I've just removed the test on that web page re: --disable-redhat-pthread. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2982717&group_id=29880 From noreply at sourceforge.net Tue Jul 27 22:32:44 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 27 Jul 2010 20:32:44 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2946553 ] check_dns returns incorrect state when specifying server Message-ID: Bugs item #2946553, was opened at 2010-02-05 13:59 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: dicko (dicko82) Assigned to: Nobody/Anonymous (nobody) Summary: check_dns returns incorrect state when specifying server Initial Comment: Plugin Version (-V output): check_dns v1992 (nagios-plugins 1.4.13) Plugin Name: check_dns Plugin Commandline showing issues: /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 Operating System: Red Hat Enterprise Linux Server release 5.4 (Tikanga) An incorrect state is returned when checking that the dns server ( 1.1.1.1 ) can resolve the host www.test.com when the dns server is down. The following command is used /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 If the DNS server is unavailable the check still returns OK. This worked correctly on RHEL 5.3 but not in Rhel 5.4 It appears that the behaviour of nslookup has changed between bind-utils-9.3.4-10.P1.el5 and bind-utils-9.3.6-4.P1.el5 On RHEL 5.3 bind-utils-9.3.4-10.P1.el5, nslookup timed out when querying against a server that was not working. [root at nagios nagios]# nslookup www.rm.com 194.238.49.43 ;; connection timed out; no servers could be reached On RHEL 5.4 bind-utils-9.3.6-4.P1.el5, the same query against a non existent dns server returns an ip address. [root at nagios ~]# nslookup www.rm.com 1.1.1.1 Server: 10.34.1.11 Address: 10.34.1.11#53 Non-authoritative answer: Name: www.rm.com Address: 2.2.2.2 It appears that nslookup now makes best efforts to resolve the query even if it cant resolve it against the server specified. This results in an incorrect state being returned when using check dns to ensure that a specific mail server is working correctly. ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2010-07-27 21:32 Message: Damn, that looks painful. It means we will have to parse the complete output to see if the answer section contains the IP address we originally requested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 From noreply at sourceforge.net Wed Jul 28 15:27:45 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 28 Jul 2010 13:27:45 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2946553 ] check_dns returns incorrect state when specifying server Message-ID: Bugs item #2946553, was opened at 2010-02-05 08:59 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: dicko (dicko82) Assigned to: Nobody/Anonymous (nobody) Summary: check_dns returns incorrect state when specifying server Initial Comment: Plugin Version (-V output): check_dns v1992 (nagios-plugins 1.4.13) Plugin Name: check_dns Plugin Commandline showing issues: /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 Operating System: Red Hat Enterprise Linux Server release 5.4 (Tikanga) An incorrect state is returned when checking that the dns server ( 1.1.1.1 ) can resolve the host www.test.com when the dns server is down. The following command is used /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 If the DNS server is unavailable the check still returns OK. This worked correctly on RHEL 5.3 but not in Rhel 5.4 It appears that the behaviour of nslookup has changed between bind-utils-9.3.4-10.P1.el5 and bind-utils-9.3.6-4.P1.el5 On RHEL 5.3 bind-utils-9.3.4-10.P1.el5, nslookup timed out when querying against a server that was not working. [root at nagios nagios]# nslookup www.rm.com 194.238.49.43 ;; connection timed out; no servers could be reached On RHEL 5.4 bind-utils-9.3.6-4.P1.el5, the same query against a non existent dns server returns an ip address. [root at nagios ~]# nslookup www.rm.com 1.1.1.1 Server: 10.34.1.11 Address: 10.34.1.11#53 Non-authoritative answer: Name: www.rm.com Address: 2.2.2.2 It appears that nslookup now makes best efforts to resolve the query even if it cant resolve it against the server specified. This results in an incorrect state being returned when using check dns to ensure that a specific mail server is working correctly. ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2010-07-28 09:27 Message: We'd really need a native dns check IMHO, shouldn't be very hard to do if we don't implement the TCP part of it or use an existing library.... ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2010-07-27 16:32 Message: Damn, that looks painful. It means we will have to parse the complete output to see if the answer section contains the IP address we originally requested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 From noreply at sourceforge.net Thu Jul 29 17:04:33 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 29 Jul 2010 15:04:33 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2946553 ] check_dns returns incorrect state when specifying server Message-ID: Bugs item #2946553, was opened at 2010-02-05 08:59 Message generated for change (Comment added) made by lelutin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: dicko (dicko82) Assigned to: Nobody/Anonymous (nobody) Summary: check_dns returns incorrect state when specifying server Initial Comment: Plugin Version (-V output): check_dns v1992 (nagios-plugins 1.4.13) Plugin Name: check_dns Plugin Commandline showing issues: /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 Operating System: Red Hat Enterprise Linux Server release 5.4 (Tikanga) An incorrect state is returned when checking that the dns server ( 1.1.1.1 ) can resolve the host www.test.com when the dns server is down. The following command is used /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 If the DNS server is unavailable the check still returns OK. This worked correctly on RHEL 5.3 but not in Rhel 5.4 It appears that the behaviour of nslookup has changed between bind-utils-9.3.4-10.P1.el5 and bind-utils-9.3.6-4.P1.el5 On RHEL 5.3 bind-utils-9.3.4-10.P1.el5, nslookup timed out when querying against a server that was not working. [root at nagios nagios]# nslookup www.rm.com 194.238.49.43 ;; connection timed out; no servers could be reached On RHEL 5.4 bind-utils-9.3.6-4.P1.el5, the same query against a non existent dns server returns an ip address. [root at nagios ~]# nslookup www.rm.com 1.1.1.1 Server: 10.34.1.11 Address: 10.34.1.11#53 Non-authoritative answer: Name: www.rm.com Address: 2.2.2.2 It appears that nslookup now makes best efforts to resolve the query even if it cant resolve it against the server specified. This results in an incorrect state being returned when using check dns to ensure that a specific mail server is working correctly. ---------------------------------------------------------------------- Comment By: lelutin (lelutin) Date: 2010-07-29 11:04 Message: On Ubuntu Lucid Lynx, the dnsutils package is version 9.7.0.dfsg.P1. If I try the nslookup command mentioned in the details of the bug, I don't get the same output: root at zaptop:~# nslookup www.rm.com 1.1.1.1 ;; connection timed out; no servers could be reached It seems like there could be a bug in the version shipped with RHEL 5.4. Maybe a patch didn't get backported or something. You should open a bug report against the RHEL package. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2010-07-28 09:27 Message: We'd really need a native dns check IMHO, shouldn't be very hard to do if we don't implement the TCP part of it or use an existing library.... ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2010-07-27 16:32 Message: Damn, that looks painful. It means we will have to parse the complete output to see if the answer section contains the IP address we originally requested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880