From ben at clewett.org.uk Tue Mar 1 00:26:32 2005 From: ben at clewett.org.uk (Ben Clewett) Date: Tue Mar 1 00:26:32 2005 Subject: [Nagiosplug-devel] Re: [Perfparse-users] zero values in database In-Reply-To: <12800.1109662629@www48.gmx.net> References: <4752.1109661898@www48.gmx.net> <12800.1109662629@www48.gmx.net> Message-ID: <42242669.7080303@clewett.org.uk> Jessica, These are known bugs in the plugins which are causing lots of users problems. I can suggest two solutions. 1. Recompile the plugins using: ./configure --disable-nls I have not tested this, but I believe this should work. 2. After the 'textdomain' call at the start of the plugin source code, add the line: setlocale(LC_NUMERIC, "POSIX"); Eg, with your problem plugin check_load. Edit plugins/check_load.c: -------------------check_load.c------------------- int main (int argc, char **argv) { int result = STATE_UNKNOWN; #if HAVE_GETLOADAVG==1 double la[3] = { 0.0, 0.0, 0.0 }; /* NetBSD complains about unitialized arrays */ #else # if HAVE_PROC_LOADAVG==1 FILE *fp; char input_buffer[MAX_INPUT_BUFFER]; char *tmp_ptr; # else char input_buffer[MAX_INPUT_BUFFER]; # endif #endif float la1, la5, la15; setlocale (LC_ALL, ""); bindtextdomain (PACKAGE, LOCALEDIR); textdomain (PACKAGE); setlocale(LC_NUMERIC, "POSIX"); <--- HERE!! -------------------check_load.c------------------- This should sort out your problems. Please let us know. Regards, Ben. Jessica Holle wrote: > Sorry, but I've forgotten another thing. > > First I tell you something, so it's better to understand I hope. > > I had problems with the check_load plugin: > > nagios at rzvlabwks:/usr/local/nagios/libexec> ./check_load -w 1.5,1.5,1.5 -c > 4.0,2.0,2.0 > Warning threshold must be float or float triplet! > > Usage: check_load -w WLOAD1,WLOAD5,WLOAD15 -c CLOAD1,CLOAD5,CLOAD15 > > > So I get this bad output, but I've found a solution: > > nagios at rzvlabwks:/usr/local/nagios/libexec> ./check_load -w 1,5:1,5:1,5 -c > 4,0:2,0:2,0 > OK - load average: 0,27, 0,30, > 0,29|load1=0,270000;1,500000;4,000000;0,000000 > load5=0,300000;1,500000;2,000000;0,000000 > load15=0,290000;1,500000;2,000000;0,000000 > > > So I think there is a problem with , and . !!! > > Some days before the first "version" of my check_load numbers worked but now > I do it with the second. > > > And now to my right problem... > > It's about the values in my database: > > 47020 | jholle | Ping | rta | 2005-02-28 15:51:39 | > 0 | 85 | 95 | 0 | > | 47021 | jholle | Ping | pl | 2005-02-28 15:51:39 | > 0 | 40 | 80 | 0 | > > > There are no values only a zero. > > nagios at rzvlabwks:/usr/local/nagios/libexec> ./check_icmp -H jholle > OK - jholle: rta 0.224ms, lost 0%|rta=0.224ms;200.000;500.000;0; > pl=0%;40;80;; > > > But here are values. When this value goes over 1 it is shown in database, > but only as a 1 not the float integers. > I think this is because of the . ! I think it is like my first problem. > there was a point which could not be interpreted and here is a point again. > I don't know but I think when there is a , and not a . the problem is > solved... > > Can I think right ??? > From ae at op5.se Tue Mar 1 00:49:02 2005 From: ae at op5.se (Andreas Ericsson) Date: Tue Mar 1 00:49:02 2005 Subject: [Nagiosplug-devel] Re: [Perfparse-users] zero values in database In-Reply-To: <42242669.7080303@clewett.org.uk> References: <4752.1109661898@www48.gmx.net> <12800.1109662629@www48.gmx.net> <42242669.7080303@clewett.org.uk> Message-ID: <42242BDC.5030900@op5.se> Ben Clewett wrote: > Jessica, > > These are known bugs in the plugins which are causing lots of users > problems. > > I can suggest two solutions. > > 1. Recompile the plugins using: > > ./configure --disable-nls > > I have not tested this, but I believe this should work. > It won't. It won't reset the textdomain of the apps it's running, only disable international output capabilities of the plugin she's running. > 2. After the 'textdomain' call at the start of the plugin source code, > add the line: > > setlocale(LC_NUMERIC, "POSIX"); > This will work, or LC_ALL=POSIX nagios nagios.cfg -d when starting nagios (although that would defeat localisation of plugins). -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Lead Developer From noreply at sourceforge.net Wed Mar 2 04:22:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 2 04:22:10 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1155027 ] check_hpjd (v1.4) unknown output Message-ID: Bugs item #1155027, was opened at 2005-03-02 13:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155027&group_id=29880 Category: Argument proccessing Group: Release (specify) Status: Open Resolution: None Priority: 5 Submitted By: Werner Flamme (wernerflamme) Assigned to: Nobody/Anonymous (nobody) Summary: check_hpjd (v1.4) unknown output Initial Comment: Hi there, I use check_hpjd with -H as only parameter. No problems with the 1.3.1 plugins. Today I installed version 1.4 and found out that ./check_hpjd -H 141.65.129.65 results in Unknown output option passed to -O: Q. : Timeout from host 141.65.129.65 So I renamed check_hpjd and copied the old one back again - this runs fine. What can I do to make check_hpjd 1.4 work again? Regards, \/\/erner ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155027&group_id=29880 From bclewett at perfparse.org Wed Mar 2 05:00:44 2005 From: bclewett at perfparse.org (Ben Clewett) Date: Wed Mar 2 05:00:44 2005 Subject: [Nagiosplug-devel] Multi-lingual performance data. Message-ID: <4223068A.7030800@perfparse.org> I have had a report from a user of PerfParse about problems with performance data on non-English setups. Eg, check_nt returns: | 'c:\ Used Space'=1,62Gb;1,80;1,90;0.00;2,00 To produce legal performance data, it should write: | 'c:\ Used Space'=1.62Gb;1.80;1.90;0.00;2.00 From experience with PerfParse, the following command needs to be added before the writing of the performance data: setlocale(LC_NUMERIC, "POSIX"); Then after writing: setlocale(LC_NUMERIC, ""); I hope this is of use to somebody. Regards, Ben Clewett. From ben at clewett.org.uk Wed Mar 2 05:11:30 2005 From: ben at clewett.org.uk (Ben Clewett) Date: Wed Mar 2 05:11:30 2005 Subject: [Nagiosplug-devel] Multi-lingual performance data. In-Reply-To: <4223068A.7030800@perfparse.org> References: <4223068A.7030800@perfparse.org> Message-ID: <4225BAF1.9030204@clewett.org.uk> Reply to my own posting: I posted this some time ago under a bad email address, which delayed posting by several days. I have already had an answer to this, please ignore! Regards, Ben Ben Clewett wrote: > I have had a report from a user of PerfParse about problems with > performance data on non-English setups. > > Eg, check_nt returns: > > | 'c:\ Used Space'=1,62Gb;1,80;1,90;0.00;2,00 > > To produce legal performance data, it should write: > > | 'c:\ Used Space'=1.62Gb;1.80;1.90;0.00;2.00 > > From experience with PerfParse, the following command needs to be added > before the writing of the performance data: > > setlocale(LC_NUMERIC, "POSIX"); > > Then after writing: > > setlocale(LC_NUMERIC, ""); > > I hope this is of use to somebody. > > Regards, > > Ben Clewett. > > > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________________ > 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 kvaes at vangenechten.com Wed Mar 2 07:44:06 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Wed Mar 2 07:44:06 2005 Subject: [Nagiosplug-devel] PluginHelp: php scripts give "Status: 404" Message-ID: Hi, I'm trying to write some additional scripts for nagios. The thing is that my own coding skills are limited to php. So I've written a few scripts that do what their supposed to do from commandline, yet when I configure them in nagios, I get a "Status: 404" in the status information. I did some research and found out that it's got something to do with the link between going from CGI to php. Does anyone have any experience with this, and could you give me some pointers on how I can get my php scripts working? Thanks in advance Karim Vaes Sys Admin Vangenechten Group Config (file path's are correct) # 'check_esx' command definition define command { command_name check_esx command_line /usr/bin/php /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ } -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From kvaes at vangenechten.com Wed Mar 2 07:46:36 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Wed Mar 2 07:46:36 2005 Subject: [Nagiosplug-devel] PluginHelp: php scripts give "Status: 404" Message-ID: Hi, I'm trying to write some additional scripts for nagios. The thing is that my own coding skills are limited to php. So I've written a few scripts that do what their supposed to do from commandline, yet when I configure them in nagios, I get a "Status: 404" in the status information. I did some research and found out that it's got something to do with the link between going from CGI to php. Does anyone have any experience with this, and could you give me some pointers on how I can get my php scripts working? Thanks in advance Karim Vaes Sys Admin Vangenechten Group Config (file path's are correct) # 'check_esx' command definition define command { command_name check_esx command_line /usr/bin/php /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ } -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From ae at op5.se Wed Mar 2 09:37:08 2005 From: ae at op5.se (Andreas Ericsson) Date: Wed Mar 2 09:37:08 2005 Subject: [Nagiosplug-devel] PluginHelp: php scripts give "Status: 404" In-Reply-To: References: Message-ID: <4225F98C.3040509@op5.se> Karim Vaes wrote: > Hi, > > I'm trying to write some additional scripts for nagios. The thing is > that my own coding skills are limited to php. So I've written a few > scripts that do what their supposed to do from commandline, yet when I > configure them in nagios, I get a "Status: 404" in the status > information. > > I did some research and found out that it's got something to do with > the link between going from CGI to php. Does anyone have any experience > with this, and could you give me some pointers on how I can get my php > scripts working? > Try /usr/bin/php -q, which will cause it not to print http and html headers. The CLI version of PHP also supports hashbang lines, so you can add it there #!/usr/bin/php -q > Thanks in advance > Cheers. > Karim Vaes > Sys Admin Vangenechten Group > > > > > Config (file path's are correct) > # 'check_esx' command definition > define command { > command_name check_esx > command_line /usr/bin/php > /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ > $ARG3$ > } > > > > ------------------------------------------------------------------------ > > Privileged Confidential Information may be contained in this message. > If you are not the addressee indicated in this message (or responsible for delivery of > the message to such person), you may not copy or deliver this message to anyone. > In such case, you should destroy this message and kindly notify the sender by reply > email. Please advise immediately if you or your employer does not consent to Internet > email for messages of this kind. Opinions, conclusions and other information in this > message that do not relate to the official business of my firm shall be understood > as neither given nor endorsed by it. > -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Lead Developer From noreply at sourceforge.net Wed Mar 2 19:36:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 2 19:36:44 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1155562 ] check_tcp doesn't support ssmtp Message-ID: Bugs item #1155562, was opened at 2005-03-02 19:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155562&group_id=29880 Category: None Group: CVS Status: Open Resolution: None Priority: 5 Submitted By: Quanah Gibson-Mount (mishikal) Assigned to: Nobody/Anonymous (nobody) Summary: check_tcp doesn't support ssmtp Initial Comment: check_tcp doesn't support check_ssmtp as a protocol check. Stanford has developed a patch allowing this: --- nagios-plugins-1.3.1/plugins/check_tcp.c.orig 2003-06-09 21:56:47.000001000 -0700 +++ nagios-plugins-1.3.1/plugins/check_tcp.c 2003-12-10 19:07:58.000001000 -0800 @@ -179,10 +179,34 @@ asprintf (&QUIT, "QUIT\r\n"); PROTOCOL=TCP_PROTOCOL; use_ssl=TRUE; PORT=995; } + else if (strstr(argv[0],"check_ssmtp")) { + asprintf (&progname, "check_ssmtp"); + asprintf (&SERVICE, "SSMTP"); + SEND=NULL; + asprintf (&EXPECT, "220"); + asprintf (&QUIT, "QUIT\r\n"); + PROTOCOL=TCP_PROTOCOL; + use_ssl=TRUE; + PORT=465; + } + else if (strstr (argv[0], "check_nntps")) { + asprintf (&progname, "check_nntps"); + asprintf (&SERVICE, "NNTPS"); + SEND = NULL; + EXPECT = NULL; + server_expect = realloc (server_expect, ++server_expect_count); + asprintf (&server_expect[server_expect_count - 1], "200"); + server_expect = realloc (server_expect, ++server_expect_count); + asprintf (&server_expect[server_expect_count - 1], "201"); + asprintf (&QUIT, "QUIT\r\n"); + PROTOCOL = TCP_PROTOCOL; + use_ssl=TRUE; + PORT = 563; + } #endif else if (strstr (argv[0], "check_nntp")) { asprintf (&progname, "check_nntp"); asprintf (&SERVICE, "NNTP"); SEND = NULL; --- nagios-plugins-1.3.1/configure.orig 2003-07-10 23:30:56.000001000 -0700 +++ nagios-plugins-1.3.1/configure 2003-12-10 18:55:57.000001000 -0800 @@ -8383,11 +8383,11 @@ LIBS="$_SAVEDLIBS" if test "$ac_cv_lib_crypto_CRYPTO_lock" = "yes"; then if test "$ac_cv_lib_ssl_main" = "yes"; then if test "$FOUNDINCLUDE" = "yes"; then - check_tcp_ssl="check_simap check_spop" + check_tcp_ssl="check_simap check_spop check_ssmtp check_nntps" cat >>confdefs.h <<\_ACEOF #define HAVE_SSL 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155562&group_id=29880 From noreply at sourceforge.net Wed Mar 2 19:40:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 2 19:40:14 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1155565 ] check_dig needs better check in if statement Message-ID: Bugs item #1155565, was opened at 2005-03-02 19:38 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155565&group_id=29880 Category: None Group: CVS Status: Open Resolution: None Priority: 5 Submitted By: Quanah Gibson-Mount (mishikal) Assigned to: Nobody/Anonymous (nobody) Summary: check_dig needs better check in if statement Initial Comment: This patch helps compensate for different DNS returns: --- nagios-plugins-1.3.1/plugins/check_dig.c.orig 2003-01-13 04:15:15.000001000 -0800 +++ nagios-plugins-1.3.1/plugins/check_dig.c 2003-12-12 07:48:30.000001000 -0800 @@ -76,11 +76,12 @@ printf ("Could not open stderr for %s\n", command_line); while (fgets (input_buffer, MAX_INPUT_BUFFER - 1, child_process)) { /* the server is responding, we just got the host name... */ - if (strstr (input_buffer, ";; ANSWER SECTION:")) { + if (strstr (input_buffer, ";; ANSWER SECTION:") || + strstr (input_buffer, ";; ANSWERS:")) { /* get the host address */ if (!fgets (input_buffer, MAX_INPUT_BUFFER - 1, child_process)) break; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1155565&group_id=29880 From kvaes at vangenechten.com Thu Mar 3 02:51:21 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Thu Mar 3 02:51:21 2005 Subject: [Nagiosplug-devel] Re: Re: PluginHelp: php scripts give "Status: 404" Message-ID: Thanks for the reply, but I already tried that part... Here are my configs: # 'check_esx' command definition define command { command_name check_esx command_line /usr/local/nagios/libexec/esx/test.php $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ } define service{ use generic-service hostgroup_name VMWARE service_description VMWARE-CPU check_command check_esx!CPU!85!90 contact_groups Helpdesk } /usr/local/nagios/libexec/esx/test.php #!/usr/bin/php -q and I still get: ESX1 VMWARE-CPU UNKNOWN 03-03-2005 11:43:45 0d 0h 1m 18s 1/3 Status: 404 ESX9 VMWARE-CPU UNKNOWN 03-03-2005 11:43:33 0d 0h 1m 28s 1/3 Status: 404 Regards Karim From: Andreas Ericsson Subject: Re: PluginHelp: php scripts give "Status: 404" Newsgroups: gmane.network.nagios.plugins.devel Date: Wed, 02 Mar 2005 18:36:12 +0100 Karim Vaes wrote: > Hi, > > I'm trying to write some additional scripts for nagios. The thing is > that my own coding skills are limited to php. So I've written a few > scripts that do what their supposed to do from commandline, yet when I > configure them in nagios, I get a "Status: 404" in the status > information. > > I did some research and found out that it's got something to do with > the link between going from CGI to php. Does anyone have any experience > with this, and could you give me some pointers on how I can get my php > scripts working? > Try /usr/bin/php -q, which will cause it not to print http and html headers. The CLI version of PHP also supports hashbang lines, so you can add it there #!/usr/bin/php -q > Thanks in advance > Cheers. > Karim Vaes > Sys Admin Vangenechten Group > > > > > Config (file path's are correct) > # 'check_esx' command definition > define command { > command_name check_esx > command_line /usr/bin/php > /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ > $ARG3$ > } > > > > ------------------------------------------------------------------------ > > Privileged Confidential Information may be contained in this message. > If you are not the addressee indicated in this message (or responsible for delivery of > the message to such person), you may not copy or deliver this message to anyone. > In such case, you should destroy this message and kindly notify the sender by reply > email. Please advise immediately if you or your employer does not consent to Internet > email for messages of this kind. Opinions, conclusions and other information in this > message that do not relate to the official business of my firm shall be understood > as neither given nor endorsed by it. > -- Andreas Ericsson andreas.ericsson at ... OP5 AB www.op5.se Lead Developer ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel at ... 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 embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From noreply at sourceforge.net Thu Mar 3 03:41:06 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 3 03:41:06 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1155754 ] added support SNMPv2c Message-ID: Patches item #1155754, was opened at 2005-03-03 14:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1155754&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: KonstantinK (koka_atvc) Assigned to: Nobody/Anonymous (nobody) Summary: added support SNMPv2c Initial Comment: patch added support SNMPv2c in check_snmp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1155754&group_id=29880 From sghosh at sghosh.org Thu Mar 3 05:00:34 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Thu Mar 3 05:00:34 2005 Subject: [Nagiosplug-devel] Re: Re: PluginHelp: php scripts give "Status: 404" In-Reply-To: References: Message-ID: Before coding - might want to see if there is an existing VmWare ESX plugin ;) http://www.nagiosexchange.org/Linux.55.0.html?&tx_netnagext_pi1[p_view]=148 On Thu, 3 Mar 2005, Karim Vaes wrote: > Thanks for the reply, but I already tried that part... > > Here are my configs: > > # 'check_esx' command definition > define command { > command_name check_esx > command_line /usr/local/nagios/libexec/esx/test.php > $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ > } > > define service{ > use generic-service > hostgroup_name VMWARE > service_description VMWARE-CPU > check_command check_esx!CPU!85!90 > contact_groups Helpdesk > } > > /usr/local/nagios/libexec/esx/test.php > #!/usr/bin/php -q > echo "Hello World\n"; > ?> > > > and I still get: > > ESX1 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:45 0d 0h 1m 18s 1/3 Status: > 404 > > ESX9 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:33 0d 0h 1m 28s 1/3 Status: > 404 > > Regards > > Karim > > From: Andreas Ericsson > Subject: Re: PluginHelp: php scripts give "Status: 404" > Newsgroups: gmane.network.nagios.plugins.devel > Date: Wed, 02 Mar 2005 18:36:12 +0100 > > Karim Vaes wrote: >> Hi, >> >> I'm trying to write some additional scripts for nagios. The thing > is >> that my own coding skills are limited to php. So I've written a few >> scripts that do what their supposed to do from commandline, yet when > I >> configure them in nagios, I get a "Status: 404" in the status >> information. >> >> I did some research and found out that it's got something to do with >> the link between going from CGI to php. Does anyone have any > experience >> with this, and could you give me some pointers on how I can get my > php >> scripts working? >> > > Try /usr/bin/php -q, which will cause it not to print http and html > headers. > The CLI version of PHP also supports hashbang lines, so you can add it > there > #!/usr/bin/php -q > script(doing, cool, things); > ?> > >> Thanks in advance >> > > Cheers. > >> Karim Vaes >> Sys Admin Vangenechten Group >> >> >> >> >> Config (file path's are correct) >> # 'check_esx' command definition >> define command { >> command_name check_esx >> command_line /usr/bin/php >> /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ >> $ARG3$ >> } >> >> >> >> > ------------------------------------------------------------------------ >> >> Privileged Confidential Information may be contained in this > message. >> If you are not the addressee indicated in this message (or > responsible for delivery of >> the message to such person), you may not copy or deliver this message > to anyone. >> In such case, you should destroy this message and kindly notify the > sender by reply >> email. Please advise immediately if you or your employer does not > consent to Internet >> email for messages of this kind. Opinions, conclusions and other > information in this >> message that do not relate to the official business of my firm shall > be understood >> as neither given nor endorsed by it. >> > > -- From kvaes at vangenechten.com Thu Mar 3 06:13:29 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Thu Mar 3 06:13:29 2005 Subject: [Nagiosplug-devel] Re: Re: PluginHelp: php scripts give "Status:404" Message-ID: I know that check exist, but the check I'm making combines more things than that check, plus the problem propagtes itself on other checks (business specific) too... (like the test.php). Thanks for the reply, but this one is an example to get all my php scripts on track :) Regards Karim >>> Subhendu Ghosh 3/03/2005 13:57:56 >>> Before coding - might want to see if there is an existing VmWare ESX plugin ;) http://www.nagiosexchange.org/Linux.55.0.html?&tx_netnagext_pi1[p_view]=148 On Thu, 3 Mar 2005, Karim Vaes wrote: > Thanks for the reply, but I already tried that part... > > Here are my configs: > > # 'check_esx' command definition > define command { > command_name check_esx > command_line /usr/local/nagios/libexec/esx/test.php > $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ > } > > define service{ > use generic-service > hostgroup_name VMWARE > service_description VMWARE-CPU > check_command check_esx!CPU!85!90 > contact_groups Helpdesk > } > > /usr/local/nagios/libexec/esx/test.php > #!/usr/bin/php -q > echo "Hello World\n"; > ?> > > > and I still get: > > ESX1 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:45 0d 0h 1m 18s 1/3 Status: > 404 > > ESX9 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:33 0d 0h 1m 28s 1/3 Status: > 404 > > Regards > > Karim > > From: Andreas Ericsson > Subject: Re: PluginHelp: php scripts give "Status: 404" > Newsgroups: gmane.network.nagios.plugins.devel > Date: Wed, 02 Mar 2005 18:36:12 +0100 > > Karim Vaes wrote: >> Hi, >> >> I'm trying to write some additional scripts for nagios. The thing > is >> that my own coding skills are limited to php. So I've written a few >> scripts that do what their supposed to do from commandline, yet when > I >> configure them in nagios, I get a "Status: 404" in the status >> information. >> >> I did some research and found out that it's got something to do with >> the link between going from CGI to php. Does anyone have any > experience >> with this, and could you give me some pointers on how I can get my > php >> scripts working? >> > > Try /usr/bin/php -q, which will cause it not to print http and html > headers. > The CLI version of PHP also supports hashbang lines, so you can add it > there > #!/usr/bin/php -q > script(doing, cool, things); > ?> > >> Thanks in advance >> > > Cheers. > >> Karim Vaes >> Sys Admin Vangenechten Group >> >> >> >> >> Config (file path's are correct) >> # 'check_esx' command definition >> define command { >> command_name check_esx >> command_line /usr/bin/php >> /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ >> $ARG3$ >> } >> >> >> >> > ------------------------------------------------------------------------ >> >> Privileged Confidential Information may be contained in this > message. >> If you are not the addressee indicated in this message (or > responsible for delivery of >> the message to such person), you may not copy or deliver this message > to anyone. >> In such case, you should destroy this message and kindly notify the > sender by reply >> email. Please advise immediately if you or your employer does not > consent to Internet >> email for messages of this kind. Opinions, conclusions and other > information in this >> message that do not relate to the official business of my firm shall > be understood >> as neither given nor endorsed by it. >> > > -- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From nachopablo33 at yahoo.com Thu Mar 3 19:01:48 2005 From: nachopablo33 at yahoo.com (nacho pablo) Date: Thu Mar 3 19:01:48 2005 Subject: [Nagiosplug-devel] nagios plugins for oracle 10g... Message-ID: <20050304025954.14145.qmail@web61301.mail.yahoo.com> Hi there, I'm on a quest for nagios plugins for oracle 10g. Here is what I've found so far: mathias-kettner.com/download/check_oracle_writeaccess -- good nagios-plugins-1.4/contrib/check_ora_table_space.pl -- useless for 10g nagios-plugins-1.4/plugins-scripts/check_oracle.sh -- useless for 10g nagios-plugins-1.4/contrib/check_oracle_tbs -- good nagios-plugins-1.4/contrib/check_oracle_instance.pl -- not sure yet Where might I find more nagios plugins for oracle? Once I find them, I'll be nice and post my findings here! Thanks, Nacho nachopablo33 at yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From kvaes at vangenechten.com Thu Mar 3 20:21:05 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Thu Mar 3 20:21:05 2005 Subject: [Nagiosplug-devel] Re: Nagiosplug-devel digest, Vol 1 #861 - 7 msgs (Ouf of Office (Auto Reply)) Message-ID: Dear Sir/Madam, I'm currently out of the office, I'll be back on the 7th of March. For urgent matters, don't hesitate to contact my colleagues (helpdesk at vangenechten.com or +32(0)14/403720). Kind regards Karim Vaes IMAS NV (part of the Vangenechten Group) Raadsherenstraat 2 - BE-2300 TURNHOUT Tel: +32(0)14 403730 fax: +32(0)14 403715 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From tonvoon at mac.com Fri Mar 4 13:00:28 2005 From: tonvoon at mac.com (Ton Voon) Date: Fri Mar 4 13:00:28 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 Message-ID: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> Hi! I've taken a break from the plugins, but I can put some time back in now. There looks to be little development, but lots of bug reports coming in, so that's more stuff to get on with! I've had a think about the discussions that Andreas Ericsson and Terje Bless had about version levels (thread "Hooray - 1.4 is out! What next?") and I think they make sense. So what I've done now is branch at the current CVS to 1_4-patches. Please commit to HEAD for the 1.5 release. If you come across a bug that should be applied to 1.4 as well as to HEAD, please fix HEAD and 1_4-patches. Please shout up if you think there should be a 1.4.1 release (does the check_icmp fix in makefile warrant it right now?). I'll also change the SF snapshot to only include CVS HEAD and the 1.4 branch now, so 1.3 is truly dead. I've also updated doc/RELEASING to include these instructions, so they don't get lost next time. So, what do people want to see for 1.5? My first thoughts are: - more translations - ps checks in configure.in to base on OS first, then "figuring it out" - a better web site at http://nagiosplug.sf.net - move more plugins from contrib into core I'm looking for volunteers as well as wish lists. :) Ton From noreply at sourceforge.net Fri Mar 4 13:52:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 13:52:35 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1119917 ] Added ipv4/ipv6 options to check_ntp Message-ID: Patches item #1119917, was opened at 2005-02-10 09:46 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 Category: Enhancement Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Seaworthy (mrseaworthy) >Assigned to: Ton Voon (tonvoon) Summary: Added ipv4/ipv6 options to check_ntp Initial Comment: The options -4 and -6 now specify the protocol to use. This addition was made because the script failed in the original version when contacting a server over ipv6. The enhancement makes use of the -46 options of ntpdate and ntpq. The original version of check_ntp I used was 1.20 and I made this version 1.30. Also i made some minor adjustments, like newlines and comments on the new options in the help output. ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-04 21:51 Message: Logged In: YES user_id=664364 Merijn, Thanks for the patch. This is useful, so it is now committed to CVS HEAD. I've made a change where the default is not to add either -4 nor -6 for backward compatibility, but I can't test this from my home system. Can you confirm this works correctly. Also, I've removed your copyright. As a rule, we don't put copyright into plugins, but we credit you in the CVS comments and in our list of contributors. BTW, a unified diff (-u) or contextual diff (-c) is more helpful than the default line by line. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 From noreply at sourceforge.net Fri Mar 4 13:55:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 13:55:36 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1119142 ] Solrais9: make abort with Error 2 Message-ID: Bugs item #1119142, was opened at 2005-02-09 07:43 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1119142&group_id=29880 Category: None Group: Release (specify) >Status: Closed Resolution: None Priority: 5 Submitted By: KlausW (osumok) Assigned to: Stanley Hopcroft (stanleyhopcroft) Summary: Solrais9: make abort with Error 2 Initial Comment: nagios-plugins-1.4 Using Solaris 9/Sparc make exits with Error2: nagios-plugins-1.3.1 works well .....make...: ...depmode=gcc /bin/bash ../depcomp gcc -DLOCALEDIR=\/usr/local/nagios/share/locale\ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib -I../intl -g -O2 -c check_icmp.c gcc -g -O2 -L. -o check_icmp check_icmp.o ../intl/libintl.a -lgen -lsocket Undefined first referenced symbol in file gethostbyname check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) inet_addr check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) inet_ntoa check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) ld: fatal: Symbol referencing errors. No output written to check_icmp collect2: ld returned 1 exit status make[2]: *** [check_icmp] Error 1 make[2]: Leaving directory `/tmp2/NAGIOS/nagios-plugins-1.4/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp2/NAGIOS/nagios-plugins-1.4' make: *** [all] Error 2 ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-04 21:54 Message: Logged In: YES user_id=664364 This appears to be fixed, so closing this now. Ton ---------------------------------------------------------------------- Comment By: KlausW (osumok) Date: 2005-02-14 11:22 Message: Logged In: YES user_id=1214509 Dear Stanley Hopcroft, everthing works fine! Thank You! Yours sincerely Klaus Wissmath ---------------------------------------------------------------------- Comment By: Stanley Hopcroft (stanleyhopcroft) Date: 2005-02-11 11:57 Message: Logged In: YES user_id=395628 Should have added this to the last update bash-2.05$ uname -a SunOS sparc-solaris2 5.9 Generic_112233-03 sun4u sparc SUNW,Ultra-60 bash-2.05$ cd nagiosplug/plugins bash-2.05$ rm check_icmp bash-2.05$ make check_icmp gcc -g -O2 -L. -o check_icmp check_icmp.o -lnsl -lsocket -lresolv ../intl/libintl.a -liconv -lgen -lsocket bash-2.05$ The formerly missing -lnsl from $SOCKETLIBS was what was killing it. HTH. ---------------------------------------------------------------------- Comment By: Stanley Hopcroft (stanleyhopcroft) Date: 2005-02-11 11:54 Message: Logged In: YES user_id=395628 Dear KlausW & zxr750, The problem may be fixed in the CVS (I was able to compile check_icmp on the SF Compile Farm Sparc/Sol 9 #1). Fix from Andreas Ericsson . Let me know if it helps or brealks something else (I don't think it will). Yours sincerely. ---------------------------------------------------------------------- Comment By: Stanley Hopcroft (stanleyhopcroft) Date: 2005-02-11 08:15 Message: Logged In: YES user_id=395628 Dear Folks, You can also work around this problem by manually compiling check_icmp by 1 copy the existing gcc line 2 add to it -lnsl -lsocket The plugin author made it clear that these libs are needed on Solaris but unfortch they are not in the (autoiconf) generated Makefile. Sorry. ---------------------------------------------------------------------- Comment By: Alex Peeters (zxr750) Date: 2005-02-11 08:06 Message: Logged In: YES user_id=590764 When you remove alle the references to check_icmp from the nagios-plugins-1.4/plugins/makefile then you can already compile the other plugins. -- Alex Peeters ---------------------------------------------------------------------- Comment By: Alex Peeters (zxr750) Date: 2005-02-11 08:00 Message: Logged In: YES user_id=590764 I have the same problem!!! # make make all-recursive make[1]: Entering directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4' Making all in intl make[2]: Entering directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/intl' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/intl' Making all in lib make[2]: Entering directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/lib' make all-am make[3]: Entering directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/lib' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/lib' make[2]: Leaving directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/lib' Making all in plugins make[2]: Entering directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/plugins' gcc -g -O2 -L. -o check_icmp check_icmp.o ../intl/libintl.a -liconv -lgen -lsocket Undefined first referenced symbol in file gethostbyname check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) inet_addr check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) inet_ntoa check_icmp.o (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) ld: fatal: Symbol referencing errors. No output written to check_icmp collect2: ld returned 1 exit status make[2]: *** [check_icmp] Error 1 make[2]: Leaving directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/nagios/nagios- plugins/nagios-plugins-1.4' make: *** [all] Error 2 Alex Peeters ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1119142&group_id=29880 From noreply at sourceforge.net Fri Mar 4 14:01:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 14:01:33 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1143836 ] three plugins contain c++ comments Message-ID: Bugs item #1143836, was opened at 2005-02-18 14:58 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1143836&group_id=29880 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Steve Greenland (vmole) >Assigned to: Ton Voon (tonvoon) Summary: three plugins contain c++ comments Initial Comment: The following plugins use '//' for a few comments, which isn't valid C89. This causes build failures on non-gcc, non-c99 platforms. check_disk.c check_smtp.c check_ups.c Thanks, Steve ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-04 22:00 Message: Logged In: YES user_id=664364 Steve, Thanks for the bug report. This is in the developer guidelines, but obviously missed. I'd be interested to know of any way to automate this check in a gcc environment. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1143836&group_id=29880 From noreply at sourceforge.net Fri Mar 4 14:21:32 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 14:21:32 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1150777 ] check_ntp.pl offset boundary condition fix Message-ID: Patches item #1150777, was opened at 2005-02-24 05:26 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 Category: Enhancement Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: John Warburton (johnwarburton) >Assigned to: Ton Voon (tonvoon) Summary: check_ntp.pl offset boundary condition fix Initial Comment: Version 1.20 of check_ntp.pl from nagios-plugins-HEAD-200502231747 According to the code: "An offset of 0.000000 with an error is probably bogus. Actually, it's probably always bogus, but let's be paranoid here." Well, in the 3 weeks of running check_ntp.pl here, I have received this error twice, on different servers: [02-24-2005 16:04:05] SERVICE ALERT: dory;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02588 [02-13-2005 17:37:51] SERVICE ALERT: plod;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02599 I suggest we remove this check as an offset of 0.000000 is not bogus. It happens. Patch attached. John ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-04 22:20 Message: Logged In: YES user_id=664364 John, I am happy to apply the changes on CVS HEAD, but not on the patches for 1.4 yet as I do not know why it this check was added. Instead of your patch of removing comments, I've added in extra ones to reference this call. Can you state your OS and ntp version please as the offset result maybe a problem to a specific level of software. I'll add that into the comments. Thanks for the bug report. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 From noreply at sourceforge.net Fri Mar 4 14:28:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 4 14:28:23 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1153148 ] long long support for check_swap on release 1.3 Message-ID: Patches item #1153148, was opened at 2005-02-28 00:05 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1153148&group_id=29880 Category: Bugfix Group: None Status: Open Resolution: None Priority: 5 Submitted By: Carlo Marcelo Arenas Belon (carenas) >Assigned to: Ton Voon (tonvoon) Summary: long long support for check_swap on release 1.3 Initial Comment: using an unsigned long int and therefore overflowing for swap bigger than 2^32 bytes. still is_intnonneg util function could wrongly assume that the parameter is not in the right range but my guess is that it is better to fix the parametrized parameter to also allow KB, MB and such instead of forcing the user to fit it as an integer so i left it untouched. ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-04 22:26 Message: Logged In: YES user_id=664364 Carlo, I'm very interested in this patch. Two things: - could you provide a patch against CVS HEAD? 1.9 is a very old version - is there a reason to prefer long long against float, other than performance reasons? My feeling is to "keep it simple" if preferable Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1153148&group_id=29880 From seanius at seanius.net Fri Mar 4 14:38:23 2005 From: seanius at seanius.net (sean finney) Date: Fri Mar 4 14:38:23 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> Message-ID: <20050304223746.GA28563@seanius.net> hi ton, On Fri, Mar 04, 2005 at 08:59:27PM +0000, Ton Voon wrote: > So, what do people want to see for 1.5? My first thoughts are: > - more translations > - ps checks in configure.in to base on OS first, then "figuring it out" > - a better web site at http://nagiosplug.sf.net > - move more plugins from contrib into core i've been lurking around for the past few months, focusing more of my time on nagios itself (i maintain the debian nagios packages), but i've been watching developments as they unfold. congratulations on finally making it to 1.4, btw! what would be a big plus for me would be a more integrated inclusion of snmp-based checks. much of what we do now at the installations where i use nagios is via ssh based checks, which unfortunately doesn't scale very well. much of what we monitor on these hosts is also exported via snmp (and graphed via cacti), and there already exist a bunch of snmp-based checks in contrib, but with a lot of redundant code and not really a consistant feel from what i remember. so, to both add something to your list and also offer myself as a volunteer, that's something i'd be interested in helping out with, as well as with whatever proofreading qa checking you'd like to do on some of the other plugins as well. sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From kvaes at vangenechten.com Fri Mar 4 20:16:26 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Fri Mar 4 20:16:26 2005 Subject: [Nagiosplug-devel] Re: Nagiosplug-devel digest, Vol 1 #862 - 9 msgs (Ouf of Office (Auto Reply)) Message-ID: Dear Sir/Madam, I'm currently out of the office, I'll be back on the 7th of March. For urgent matters, don't hesitate to contact my colleagues (helpdesk at vangenechten.com or +32(0)14/403720). Kind regards Karim Vaes IMAS NV (part of the Vangenechten Group) Raadsherenstraat 2 - BE-2300 TURNHOUT Tel: +32(0)14 403730 fax: +32(0)14 403715 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From wildcat at centaure-network.net Sat Mar 5 06:47:50 2005 From: wildcat at centaure-network.net (Alain Gachet) Date: Sat Mar 5 06:47:50 2005 Subject: [Nagiosplug-devel] Nagios : plugins - check_mrtgtraf Message-ID: Hi, I've read on the plugin's help that " The calculated i/o rates are a little off from what MRTG actually reports" I've had that issue, BUT to solve it i have modified kilo[myrouter]: 1024 The default value is 1000. i don t know why the don t use the real size. But now i/o rates are exactly the same . Best regards And thanks for this great tool. Alain From ae at op5.se Sat Mar 5 08:52:21 2005 From: ae at op5.se (Andreas Ericsson) Date: Sat Mar 5 08:52:21 2005 Subject: [Nagiosplug-devel] Nagios : plugins - check_mrtgtraf In-Reply-To: References: Message-ID: <4229E384.1000906@op5.se> Alain Gachet wrote: > Hi, > > I've read on the plugin's help that " The calculated i/o rates are a little > off from what MRTG actually reports" > > I've had that issue, BUT to solve it i have modified > > kilo[myrouter]: 1024 > > The default value is 1000. i don t know why the don t use the real size. > Because bandwidth usage is often measured in bits, not bytes. The proper formula would be (octets * 8) / 1000 to get the value in kbits. > But now i/o rates are exactly the same . > And both are in the same, wonky uom. -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Lead Developer From kvaes at vangenechten.com Sat Mar 5 20:19:07 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Sat Mar 5 20:19:07 2005 Subject: [Nagiosplug-devel] Re: Nagiosplug-devel digest, Vol 1 #863 - 4 msgs (Ouf of Office (Auto Reply)) Message-ID: Dear Sir/Madam, I'm currently out of the office, I'll be back on the 7th of March. For urgent matters, don't hesitate to contact my colleagues (helpdesk at vangenechten.com or +32(0)14/403720). Kind regards Karim Vaes IMAS NV (part of the Vangenechten Group) Raadsherenstraat 2 - BE-2300 TURNHOUT Tel: +32(0)14 403730 fax: +32(0)14 403715 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From kvaes at vangenechten.com Sun Mar 6 20:20:04 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Sun Mar 6 20:20:04 2005 Subject: [Nagiosplug-devel] Re: Nagiosplug-devel digest, Vol 1 #864 - 2 msgs (Ouf of Office (Auto Reply)) Message-ID: Dear Sir/Madam, I'm currently out of the office, I'll be back on the 7th of March. For urgent matters, don't hesitate to contact my colleagues (helpdesk at vangenechten.com or +32(0)14/403720). Kind regards Karim Vaes IMAS NV (part of the Vangenechten Group) Raadsherenstraat 2 - BE-2300 TURNHOUT Tel: +32(0)14 403730 fax: +32(0)14 403715 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From kvaes at vangenechten.com Mon Mar 7 01:01:17 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Mon Mar 7 01:01:17 2005 Subject: [Nagiosplug-devel] Re: Re: PluginHelp: php scripts give "Status:404" Message-ID: Anybody an idea how to get php checks working with nagios? Regards Karim >>> Subhendu Ghosh 3/03/2005 13:57:56 >>> Before coding - might want to see if there is an existing VmWare ESX plugin ;) http://www.nagiosexchange.org/Linux.55.0.html?&tx_netnagext_pi1[p_view]=148 On Thu, 3 Mar 2005, Karim Vaes wrote: > Thanks for the reply, but I already tried that part... > > Here are my configs: > > # 'check_esx' command definition > define command { > command_name check_esx > command_line /usr/local/nagios/libexec/esx/test.php > $HOSTADDRESS$ $ARG1$ $ARG2$ $ARG3$ > } > > define service{ > use generic-service > hostgroup_name VMWARE > service_description VMWARE-CPU > check_command check_esx!CPU!85!90 > contact_groups Helpdesk > } > > /usr/local/nagios/libexec/esx/test.php > #!/usr/bin/php -q > echo "Hello World\n"; > ?> > > > and I still get: > > ESX1 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:45 0d 0h 1m 18s 1/3 Status: > 404 > > ESX9 VMWARE-CPU > UNKNOWN 03-03-2005 11:43:33 0d 0h 1m 28s 1/3 Status: > 404 > > Regards > > Karim > > From: Andreas Ericsson > Subject: Re: PluginHelp: php scripts give "Status: 404" > Newsgroups: gmane.network.nagios.plugins.devel > Date: Wed, 02 Mar 2005 18:36:12 +0100 > > Karim Vaes wrote: >> Hi, >> >> I'm trying to write some additional scripts for nagios. The thing > is >> that my own coding skills are limited to php. So I've written a few >> scripts that do what their supposed to do from commandline, yet when > I >> configure them in nagios, I get a "Status: 404" in the status >> information. >> >> I did some research and found out that it's got something to do with >> the link between going from CGI to php. Does anyone have any > experience >> with this, and could you give me some pointers on how I can get my > php >> scripts working? >> > > Try /usr/bin/php -q, which will cause it not to print http and html > headers. > The CLI version of PHP also supports hashbang lines, so you can add it > there > #!/usr/bin/php -q > script(doing, cool, things); > ?> > >> Thanks in advance >> > > Cheers. > >> Karim Vaes >> Sys Admin Vangenechten Group >> >> >> >> >> Config (file path's are correct) >> # 'check_esx' command definition >> define command { >> command_name check_esx >> command_line /usr/bin/php >> /usr/local/nagios/libexec/esx/esx.php $HOSTADDRESS$ $ARG1$ $ARG2$ >> $ARG3$ >> } >> >> >> >> > ------------------------------------------------------------------------ >> >> Privileged Confidential Information may be contained in this > message. >> If you are not the addressee indicated in this message (or > responsible for delivery of >> the message to such person), you may not copy or deliver this message > to anyone. >> In such case, you should destroy this message and kindly notify the > sender by reply >> email. Please advise immediately if you or your employer does not > consent to Internet >> email for messages of this kind. Opinions, conclusions and other > information in this >> message that do not relate to the official business of my firm shall > be understood >> as neither given nor endorsed by it. >> > > -- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From Stanley.Hopcroft at IPAustralia.Gov.AU Mon Mar 7 01:41:05 2005 From: Stanley.Hopcroft at IPAustralia.Gov.AU (Stanley Hopcroft) Date: Mon Mar 7 01:41:05 2005 Subject: [Nagiosplug-devel] Re: Re: PluginHelp: php scripts give "Status:404" In-Reply-To: References: Message-ID: <20050307093957.GB248@IPAustralia.Gov.AU> Dear Sir, I am writing to thank you for your letter and say, On Mon, Mar 07, 2005 at 09:58:51AM +0100, Karim Vaes wrote: > Anybody an idea how to get php checks working with nagios? > Service checks can be written in any language capable of 1 writing to stdout 2 calling the POSIX exit function. Have you had a look at the plugin developers guide on the plugins page on SourceForge ? All your plugin needs do is 1 check the service somehow 2 report its conclusions to 2.1 Nagios by calling exit() with the appropriate return code 2.2 People by outputting some text. Plugins only really have two problems 1 they don't work from the CLI (check $? and the message) - they just plain don't work. 2 they don't work when Nagios runs them since the Path is wrong, Perms are wrong etc I expect I could write a plugin in MIX or on a (1003.1 compliant) Turing Machine Simulator; PHP _must_ be easier than these and if it isn't there are lots of good alternatives. >From what you have posted, your problem looks like prob 2. UNKNOWN is the status if 1 your plugin died somehow (eg raised a SEGV, was looping [killed by Nag]) 2 your plugin exited with return code 1 or 3. Yours sincerely. -- Stanley Hopcroft IP Australia Ph: (02) 6283 3189 Fax: (02) 6281 1353 PO Box 200 Woden ACT 2606 http://www.ipaustralia.gov.au -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: disclaimer.txt URL: From noreply at sourceforge.net Mon Mar 7 02:02:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 7 02:02:24 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1119917 ] Added ipv4/ipv6 options to check_ntp Message-ID: Patches item #1119917, was opened at 2005-02-10 10:46 Message generated for change (Comment added) made by mrseaworthy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 Category: Enhancement Group: None Status: Closed Resolution: Accepted Priority: 5 Submitted By: Seaworthy (mrseaworthy) Assigned to: Ton Voon (tonvoon) Summary: Added ipv4/ipv6 options to check_ntp Initial Comment: The options -4 and -6 now specify the protocol to use. This addition was made because the script failed in the original version when contacting a server over ipv6. The enhancement makes use of the -46 options of ntpdate and ntpq. The original version of check_ntp I used was 1.20 and I made this version 1.30. Also i made some minor adjustments, like newlines and comments on the new options in the help output. ---------------------------------------------------------------------- >Comment By: Seaworthy (mrseaworthy) Date: 2005-03-07 11:01 Message: Logged In: YES user_id=1178781 The reason I added the default for ipv4 is that without anuy parameters the default for ntpdate and ntpq is ipv6 which caused my servers to show errors (because Windows does not support IPv6 NTP :|) ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-04 22:51 Message: Logged In: YES user_id=664364 Merijn, Thanks for the patch. This is useful, so it is now committed to CVS HEAD. I've made a change where the default is not to add either -4 nor -6 for backward compatibility, but I can't test this from my home system. Can you confirm this works correctly. Also, I've removed your copyright. As a rule, we don't put copyright into plugins, but we credit you in the CVS comments and in our list of contributors. BTW, a unified diff (-u) or contextual diff (-c) is more helpful than the default line by line. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 From noreply at sourceforge.net Mon Mar 7 15:39:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 7 15:39:04 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1150777 ] check_ntp.pl offset boundary condition fix Message-ID: Patches item #1150777, was opened at 2005-02-24 16:26 Message generated for change (Comment added) made by johnwarburton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 Category: Enhancement Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: John Warburton (johnwarburton) Assigned to: Ton Voon (tonvoon) Summary: check_ntp.pl offset boundary condition fix Initial Comment: Version 1.20 of check_ntp.pl from nagios-plugins-HEAD-200502231747 According to the code: "An offset of 0.000000 with an error is probably bogus. Actually, it's probably always bogus, but let's be paranoid here." Well, in the 3 weeks of running check_ntp.pl here, I have received this error twice, on different servers: [02-24-2005 16:04:05] SERVICE ALERT: dory;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02588 [02-13-2005 17:37:51] SERVICE ALERT: plod;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02599 I suggest we remove this check as an offset of 0.000000 is not bogus. It happens. Patch attached. John ---------------------------------------------------------------------- >Comment By: John Warburton (johnwarburton) Date: 2005-03-08 10:38 Message: Logged In: YES user_id=1192023 Sorry about the delay - has been a busy week. This is all running on Solaris 8 with the Solaris NTP daemon - xntpd John ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-05 09:20 Message: Logged In: YES user_id=664364 John, I am happy to apply the changes on CVS HEAD, but not on the patches for 1.4 yet as I do not know why it this check was added. Instead of your patch of removing comments, I've added in extra ones to reference this call. Can you state your OS and ntp version please as the offset result maybe a problem to a specific level of software. I'll add that into the comments. Thanks for the bug report. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 From noreply at sourceforge.net Mon Mar 7 22:21:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 7 22:21:41 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1150777 ] check_ntp.pl offset boundary condition fix Message-ID: Patches item #1150777, was opened at 2005-02-24 05:26 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 Category: Enhancement Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: John Warburton (johnwarburton) Assigned to: Ton Voon (tonvoon) Summary: check_ntp.pl offset boundary condition fix Initial Comment: Version 1.20 of check_ntp.pl from nagios-plugins-HEAD-200502231747 According to the code: "An offset of 0.000000 with an error is probably bogus. Actually, it's probably always bogus, but let's be paranoid here." Well, in the 3 weeks of running check_ntp.pl here, I have received this error twice, on different servers: [02-24-2005 16:04:05] SERVICE ALERT: dory;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02588 [02-13-2005 17:37:51] SERVICE ALERT: plod;Check NTP;CRITICAL;SOFT;1;NTP CRITICAL: server 1.2.3.4, stratum 2, offset 0.000000, delay 0.02599 I suggest we remove this check as an offset of 0.000000 is not bogus. It happens. Patch attached. John ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-08 06:20 Message: Logged In: YES user_id=664364 Thanks John. I've added a comment in to the code. ---------------------------------------------------------------------- Comment By: John Warburton (johnwarburton) Date: 2005-03-07 23:38 Message: Logged In: YES user_id=1192023 Sorry about the delay - has been a busy week. This is all running on Solaris 8 with the Solaris NTP daemon - xntpd John ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-04 22:20 Message: Logged In: YES user_id=664364 John, I am happy to apply the changes on CVS HEAD, but not on the patches for 1.4 yet as I do not know why it this check was added. Instead of your patch of removing comments, I've added in extra ones to reference this call. Can you state your OS and ntp version please as the offset result maybe a problem to a specific level of software. I'll add that into the comments. Thanks for the bug report. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150777&group_id=29880 From noreply at sourceforge.net Mon Mar 7 22:22:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 7 22:22:35 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1119917 ] Added ipv4/ipv6 options to check_ntp Message-ID: Patches item #1119917, was opened at 2005-02-10 09:46 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 Category: Enhancement Group: None Status: Closed Resolution: Accepted Priority: 5 Submitted By: Seaworthy (mrseaworthy) Assigned to: Ton Voon (tonvoon) Summary: Added ipv4/ipv6 options to check_ntp Initial Comment: The options -4 and -6 now specify the protocol to use. This addition was made because the script failed in the original version when contacting a server over ipv6. The enhancement makes use of the -46 options of ntpdate and ntpq. The original version of check_ntp I used was 1.20 and I made this version 1.30. Also i made some minor adjustments, like newlines and comments on the new options in the help output. ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-08 06:21 Message: Logged In: YES user_id=664364 Merijn, Is this still an issue then? Does the CVS version work correctly? Ton ---------------------------------------------------------------------- Comment By: Seaworthy (mrseaworthy) Date: 2005-03-07 10:01 Message: Logged In: YES user_id=1178781 The reason I added the default for ipv4 is that without anuy parameters the default for ntpdate and ntpq is ipv6 which caused my servers to show errors (because Windows does not support IPv6 NTP :|) ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-04 21:51 Message: Logged In: YES user_id=664364 Merijn, Thanks for the patch. This is useful, so it is now committed to CVS HEAD. I've made a change where the default is not to add either -4 nor -6 for backward compatibility, but I can't test this from my home system. Can you confirm this works correctly. Also, I've removed your copyright. As a rule, we don't put copyright into plugins, but we credit you in the CVS comments and in our list of contributors. BTW, a unified diff (-u) or contextual diff (-c) is more helpful than the default line by line. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1119917&group_id=29880 From noreply at sourceforge.net Tue Mar 8 11:56:07 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 8 11:56:07 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-1159317 ] Patch for check_ntp to work with zero offsets Message-ID: Feature Requests item #1159317, was opened at 2005-03-08 11:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=1159317&group_id=29880 Category: None Group: None Status: Open Priority: 5 Submitted By: W Sanders (wsanders1) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for check_ntp to work with zero offsets Initial Comment: In some (mine) LANS with "perfectly" synchronized clocks the offset can be zero even though the ntp daemon is all synced up. "Check_ntp" assumes a zero offset is an unsynchronized ntpd. The way I got it to work was to also check for stratum 16, which is also a sign of zero offset. No need to be paranoid unless you are sure they are out to get you! Diff -c below: $ diff -c ../../libexec/check_ntp.0 ../../libexec/check_ntp *** ../../libexec/check_ntp.0 2005-02-04 13:59:50.000000000 -0800 --- ../../libexec/check_ntp 2005-02-04 14:18:24.000000000 -0800 *************** *** 194,200 **** # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; --- 194,200 ---- # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0 and $stratum == 16) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=1159317&group_id=29880 From tonvoon at mac.com Tue Mar 8 12:04:29 2005 From: tonvoon at mac.com (Ton Voon) Date: Tue Mar 8 12:04:29 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050304223746.GA28563@seanius.net> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> Message-ID: <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> On 4 Mar 2005, at 22:37, sean finney wrote: > what would be a big plus for me would be a more integrated inclusion > of snmp-based checks. much of what we do now at the installations > where i use nagios is via ssh based checks, which unfortunately doesn't > scale very well. much of what we monitor on these hosts is also > exported via snmp (and graphed via cacti), and there already exist a > bunch of snmp-based checks in contrib, but with a lot of redundant > code and not really a consistant feel from what i remember. > I don't personally use SNMP, but it does feel like there are a lot of redundant pieces. There probably needs to be a bit of thought in how it hangs together. What exactly do you think needs doing? Subendu is the resident expert in SNMP, so I'll leave him to decide the direction here. > so, to both add something to your list and also offer myself as a > volunteer, that's something i'd be interested in helping out with, > as well as with whatever proofreading qa checking you'd like to do > on some of the other plugins as well. > I think that's why I want to get a "wish list", so then we can have people jump in with help on any particular areas. I don't think there is anything around proofreading or QA that is required. Some work on the test suite would be very helpful. Ton From noreply at sourceforge.net Tue Mar 8 12:45:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 8 12:45:29 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-1159317 ] Patch for check_ntp to work with zero offsets Message-ID: Feature Requests item #1159317, was opened at 2005-03-08 10:55 Message generated for change (Comment added) made by jhmartin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=1159317&group_id=29880 Category: None Group: None Status: Open Priority: 5 Submitted By: W Sanders (wsanders1) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for check_ntp to work with zero offsets Initial Comment: In some (mine) LANS with "perfectly" synchronized clocks the offset can be zero even though the ntp daemon is all synced up. "Check_ntp" assumes a zero offset is an unsynchronized ntpd. The way I got it to work was to also check for stratum 16, which is also a sign of zero offset. No need to be paranoid unless you are sure they are out to get you! Diff -c below: $ diff -c ../../libexec/check_ntp.0 ../../libexec/check_ntp *** ../../libexec/check_ntp.0 2005-02-04 13:59:50.000000000 -0800 --- ../../libexec/check_ntp 2005-02-04 14:18:24.000000000 -0800 *************** *** 194,200 **** # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; --- 194,200 ---- # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0 and $stratum == 16) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; ---------------------------------------------------------------------- Comment By: Jason Martin (jhmartin) Date: 2005-03-08 11:44 Message: Logged In: YES user_id=589094 This would probably be better implemented as a command-line flag with the default behavior remaining as '0 = bad'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=1159317&group_id=29880 From noreply at sourceforge.net Tue Mar 8 14:28:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 8 14:28:31 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1159317 ] Patch for check_ntp to work with zero offsets Message-ID: Patches item #1159317, was opened at 2005-03-08 19:55 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1159317&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: W Sanders (wsanders1) >Assigned to: Ton Voon (tonvoon) Summary: Patch for check_ntp to work with zero offsets Initial Comment: In some (mine) LANS with "perfectly" synchronized clocks the offset can be zero even though the ntp daemon is all synced up. "Check_ntp" assumes a zero offset is an unsynchronized ntpd. The way I got it to work was to also check for stratum 16, which is also a sign of zero offset. No need to be paranoid unless you are sure they are out to get you! Diff -c below: $ diff -c ../../libexec/check_ntp.0 ../../libexec/check_ntp *** ../../libexec/check_ntp.0 2005-02-04 13:59:50.000000000 -0800 --- ../../libexec/check_ntp 2005-02-04 14:18:24.000000000 -0800 *************** *** 194,200 **** # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; --- 194,200 ---- # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0 and $stratum == 16) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-08 22:27 Message: Logged In: YES user_id=664364 I've applied a patch to check_ntp to remove this 0 test, but have to admit I'm not exactly sure what is happening here. Can you say why an offset of 0.000 is good/bad? ---------------------------------------------------------------------- Comment By: Jason Martin (jhmartin) Date: 2005-03-08 20:44 Message: Logged In: YES user_id=589094 This would probably be better implemented as a command-line flag with the default behavior remaining as '0 = bad'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1159317&group_id=29880 From noreply at sourceforge.net Tue Mar 8 16:07:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 8 16:07:29 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1159317 ] Patch for check_ntp to work with zero offsets Message-ID: Patches item #1159317, was opened at 2005-03-08 11:55 Message generated for change (Comment added) made by wsanders1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1159317&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: W Sanders (wsanders1) Assigned to: Ton Voon (tonvoon) Summary: Patch for check_ntp to work with zero offsets Initial Comment: In some (mine) LANS with "perfectly" synchronized clocks the offset can be zero even though the ntp daemon is all synced up. "Check_ntp" assumes a zero offset is an unsynchronized ntpd. The way I got it to work was to also check for stratum 16, which is also a sign of zero offset. No need to be paranoid unless you are sure they are out to get you! Diff -c below: $ diff -c ../../libexec/check_ntp.0 ../../libexec/check_ntp *** ../../libexec/check_ntp.0 2005-02-04 13:59:50.000000000 -0800 --- ../../libexec/check_ntp 2005-02-04 14:18:24.000000000 -0800 *************** *** 194,200 **** # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; --- 194,200 ---- # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. ! if ($offset == 0 and $stratum == 16) { undef $offset;} $ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"}; print "ntperr = $ntpdate_error \n" if $verbose; ---------------------------------------------------------------------- >Comment By: W Sanders (wsanders1) Date: 2005-03-08 16:06 Message: Logged In: YES user_id=609888 I don't know if iit would be right to remove the check for 0 offset. When offset is 0 and stratum is 16 this will indeed usually be accompanied by the "no server suitable for synchronization" in the ntpdate -q output, which is checked for in line 204. My logic will still allow the script to reset $ERRORS to the right value if the string is found in line 204. I dunno, maybe the case where offset=0 and stratum=16 and the string is not present never happens. Still the fact that Ian was being paranoid about it signifies be probably got burned once or twice by it. I tried to contact Ian via email and could not find a valid address for him. The "offset" is AFAIK the difference between the system time and the local NTPD's idea of what the time is supposed to be based on estimates of delays and stuff in the network. My particular LAN is highly accurate since I have GPS time receivers within one or two hops. So on my LAN the offset is frequently zero since the time sources are very stable and local and the network delays are very short and consistent. "Stratum" is the number of hops (0..15) between the local ntpd and the authoritative time source. (My stratum is 1 since I directly reference the servers with the GPS receivers attached.). The offset rarely stays zero for one than one check - so with "max_check_attempts" set to more than 1 this will not result in bogus alarms, the single isolated alerts show up in the logs and bug PHBs and anal-retentive sysadmins. HTH... ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-08 14:27 Message: Logged In: YES user_id=664364 I've applied a patch to check_ntp to remove this 0 test, but have to admit I'm not exactly sure what is happening here. Can you say why an offset of 0.000 is good/bad? ---------------------------------------------------------------------- Comment By: Jason Martin (jhmartin) Date: 2005-03-08 12:44 Message: Logged In: YES user_id=589094 This would probably be better implemented as a command-line flag with the default behavior remaining as '0 = bad'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1159317&group_id=29880 From seanius at seanius.net Tue Mar 8 21:20:02 2005 From: seanius at seanius.net (sean finney) Date: Tue Mar 8 21:20:02 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> Message-ID: <20050309051848.GA8436@seanius.net> hi ton, On Tue, Mar 08, 2005 at 08:03:27PM +0000, Ton Voon wrote: > I don't personally use SNMP, but it does feel like there are a lot of > redundant pieces. There probably needs to be a bit of thought in how it > hangs together. my thoughts exactly. i don't claim to know the best way to proceed with this, but would like to help find out :) > What exactly do you think needs doing? Subendu is the resident expert > in SNMP, so I'll leave him to decide the direction here. i think there are a few facets to this: - availability/selection of snmp plugins bringing in as many snmp-like checks as possible. for unix hosts there's all kinds of stuff in the ucd/net and host mibs. i could build a list if it'd be helpful. - consistancy of snmp plugin interface common cmdline interface, normalized cmd naming scheme. there'll be some cmdline options that will be common to every plugin (community, snmp version, host, port), and some that aren't. - consolidation of duplicate code depending on what we learn from the above two, it might make sense to develop a common code base to reduce code redundancy. some thoughts, anyway sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From noreply at sourceforge.net Tue Mar 8 23:07:09 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 8 23:07:09 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159624 ] Compile and Link Error on Solaris 2.6 Message-ID: Bugs item #1159624, was opened at 2005-03-09 07:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) Assigned to: Nobody/Anonymous (nobody) Summary: Compile and Link Error on Solaris 2.6 Initial Comment: With Sun WorkShop Compiler C++ 4.2: My Workaround get the Plugins Running: - The old kompiler does not understand the C++- Comment // in C files. Take /* ... */ e.g. const char *program_name = "check_disk"; /* Required for coreutils libs */ The list of found C++ comments in 1.4 check_disk.c : Line 22 check_smtp.c lines 185,257,258,613 check_ups.c line 411 - unresolved symbols (also Solaris 8 with Forte 6 Update 2 !!) (e.g. gethostbyname) in Makefile the correct List of LIBS: LIBS = -lgen -lsocket -lnsl 73 de DF7BE ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 From ae at op5.se Wed Mar 9 00:39:12 2005 From: ae at op5.se (Andreas Ericsson) Date: Wed Mar 9 00:39:12 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050309051848.GA8436@seanius.net> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> Message-ID: <422EB5F5.3040208@op5.se> sean finney wrote: > hi ton, > > On Tue, Mar 08, 2005 at 08:03:27PM +0000, Ton Voon wrote: > >>I don't personally use SNMP, but it does feel like there are a lot of >>redundant pieces. There probably needs to be a bit of thought in how it >>hangs together. > > > my thoughts exactly. i don't claim to know the best way to proceed > with this, but would like to help find out :) > > >>What exactly do you think needs doing? Subendu is the resident expert >>in SNMP, so I'll leave him to decide the direction here. > > > i think there are a few facets to this: > > - availability/selection of snmp plugins > > bringing in as many snmp-like checks as possible. for unix hosts > there's all kinds of stuff in the ucd/net and host mibs. i could > build a list if it'd be helpful. > It most likely would. If it's standardized things it would be most useful to have the OID's. It's faster to use and doesn't require the MIB to be installed. > - consistancy of snmp plugin interface > > common cmdline interface, normalized cmd naming scheme. there'll be > some cmdline options that will be common to every plugin (community, > snmp version, host, port), and some that aren't. > Naturally. I was thinking -C to mean credentials and supply username,password for snmp v3. SNMP v3 would be marked with the inclusion of the authentication method (authpriv and that sort of thing). > - consolidation of duplicate code > > depending on what we learn from the above two, it might make > sense to develop a common code base to reduce code redundancy. > This is an area where much can be gained. The plugin devel api today isn't very useful. For spawning commands, there should be a function that takes as input the command line, and returns the output and return code of the command. This would accomplish much and get rid of a LOT of duplicate code in the plugins. For snmp, there should be a function that takes a snmp_auth struct (which needs to be invented) and a list of oid's to fetch, and then returns the values of those oid's in an array. For argument validation, many of the functions just check to see if another function can be used to retrieve a value, when it in fact could retrieve the value all by itself and just let it go at that. is_int_nonneg() and the likes are just plain dumb. Why they made it into the plugin distro in the first place is more than I understand. For argument parsing, the getopt_long function might be all good and well, but it's behaviour on various systems is undocumented (some break parsing on first non-option argument, other reorder nonopts to be last and just keep going). I've written a function which takes identical input and is fully compatible in simple parsing but handles non-option arguments identically on all systems (by populating a linked list of strings). It also has support for obscuring sensitive arguments, such as usernames and passwords. Lately I've become fed up with the official plugin distribution. The number of distributed bugs in allegedly stable releases is just too much work to sort out, so I've started hacking up my own framework into which I'll import the current plugins whith changes as necessary. -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Lead Developer From noreply at sourceforge.net Wed Mar 9 05:58:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 9 05:58:29 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159828 ] CRITICAL check_ping on FC3 Message-ID: Bugs item #1159828, was opened at 2005-03-09 13:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: PiTsA (pitsa) Assigned to: Nobody/Anonymous (nobody) Summary: CRITICAL check_ping on FC3 Initial Comment: The ping verification its not working... [root at infoandre libexec]# ./check_ping -H 192.168.1.4 -w 100.0,0,20% -c 500.0,0,60% /bin/ping -n -U -w 10 -c 5 192.168.1.4 CRITICAL - Could not interpret output from ping command [root at infoandre libexec]# /bin/ping -n -U -w 10 -c 5 192.168.1.4 PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. 64 bytes from 192.168.1.4: icmp_seq=0 ttl=128 time=0.249 ms 64 bytes from 192.168.1.4: icmp_seq=1 ttl=128 time=0.255 ms 64 bytes from 192.168.1.4: icmp_seq=2 ttl=128 time=0.198 ms 64 bytes from 192.168.1.4: icmp_seq=3 ttl=128 time=0.738 ms 64 bytes from 192.168.1.4: icmp_seq=4 ttl=128 time=0.187 ms --- 192.168.1.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.187/0.325/0.738/0.208 ms, pipe 2 [root at infoandre libexec]# ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 From noreply at sourceforge.net Wed Mar 9 06:01:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 9 06:01:33 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159828 ] CRITICAL check_ping on FC3 Message-ID: Bugs item #1159828, was opened at 2005-03-09 13:57 Message generated for change (Comment added) made by pitsa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 Category: None Group: None Status: Open Resolution: None >Priority: 9 Submitted By: PiTsA (pitsa) Assigned to: Nobody/Anonymous (nobody) Summary: CRITICAL check_ping on FC3 Initial Comment: The ping verification its not working... [root at infoandre libexec]# ./check_ping -H 192.168.1.4 -w 100.0,0,20% -c 500.0,0,60% /bin/ping -n -U -w 10 -c 5 192.168.1.4 CRITICAL - Could not interpret output from ping command [root at infoandre libexec]# /bin/ping -n -U -w 10 -c 5 192.168.1.4 PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. 64 bytes from 192.168.1.4: icmp_seq=0 ttl=128 time=0.249 ms 64 bytes from 192.168.1.4: icmp_seq=1 ttl=128 time=0.255 ms 64 bytes from 192.168.1.4: icmp_seq=2 ttl=128 time=0.198 ms 64 bytes from 192.168.1.4: icmp_seq=3 ttl=128 time=0.738 ms 64 bytes from 192.168.1.4: icmp_seq=4 ttl=128 time=0.187 ms --- 192.168.1.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.187/0.325/0.738/0.208 ms, pipe 2 [root at infoandre libexec]# ---------------------------------------------------------------------- >Comment By: PiTsA (pitsa) Date: 2005-03-09 14:00 Message: Logged In: YES user_id=1235741 nagios-plugins Version 1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 From seanius at seanius.net Wed Mar 9 06:55:34 2005 From: seanius at seanius.net (sean finney) Date: Wed Mar 9 06:55:34 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <422EB5F5.3040208@op5.se> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> Message-ID: <20050309145432.GA18072@seanius.net> On Wed, Mar 09, 2005 at 09:38:13AM +0100, Andreas Ericsson wrote: > > bringing in as many snmp-like checks as possible. for unix hosts > > there's all kinds of stuff in the ucd/net and host mibs. i could > > build a list if it'd be helpful. > > It most likely would. If it's standardized things it would be most > useful to have the OID's. It's faster to use and doesn't require the MIB > to be installed. yeah, i wasn't planning on using the actual mibs, since there isn't a point and like you said it requires more stuff to be around. below is a basic rundown of what you can monitor. things marked with a '+' are stand-alone entries. things marked with a '*' are indexed entries. ucd/net mib: * processes (by name, like "httpd") - built in minimum / maximum threshold (server side configured) - total count + virtual memory - total / used / free * disks (not automatically exported, configured server side) - total / used / free - built in minimum free space threshold (server side configured) + load average - 1, 5, 10 minute averages - built in maximum threshold (server side configured) + cpu usage - user, system, nice there's more in there, but that's what i think is monitorable for practical usage. mib-2/host mib: * interfaces - all the interface stuff (traffic, errors) + tcp connections - num active connections - max connection threshold - traffic / errors * tcp connections - individual src,sport,dst,dport connections (could maybe detect dos) + udp (same as non-indexed tcp, minus connections) + number logged in users + total number processes * disks (same as ucd/net, but automatically exported and no threshold) * per process cpu / mem usage and again, there's more, but this is what i found queryable for practical purposes on a default linux/net-snmp install. > >- consistancy of snmp plugin interface > > > > common cmdline interface, normalized cmd naming scheme. there'll be > > some cmdline options that will be common to every plugin (community, > > snmp version, host, port), and some that aren't. > > > > Naturally. I was thinking -C to mean credentials and supply > username,password for snmp v3. SNMP v3 would be marked with the > inclusion of the authentication method (authpriv and that sort of thing). this brings up something i've been thinking about... the one tricky thing about snmp community / user / pass credentials is that this is something likely to be different between groups of hosts (or even host-by-host). so, setting up a generic template for checking such things in a hostgroup isn't too easy. istr hearing something on nagios-devel about the inclusion of an "snmp community" host object setting / macro in nagios 2, is that true? otherwise (or maybe in addition) it might be wise to provide a way to supply the authentication data outside of the cmdline. > >- consolidation of duplicate code > > This is an area where much can be gained. The plugin devel api today > isn't very useful. > > For spawning commands, there should be a function that takes as input > the command line, and returns the output and return code of the command. > This would accomplish much and get rid of a LOT of duplicate code in the > plugins. in this particular case i don't know that it would be helpful, as i wouldn't want to have to execute an snmpwalk command for every check, but i could see how it might be helpful in other situations. > For snmp, there should be a function that takes a snmp_auth struct > (which needs to be invented) and a list of oid's to fetch, and then > returns the values of those oid's in an array. i was kind of thinking this would be a lot simpler using perl scripts for the snmp checks, in which case we could design more easily extendable functions to do the work. > For argument parsing, the getopt_long function might be all good and > well, but it's behaviour on various systems is undocumented (some break > parsing on first non-option argument, other reorder nonopts to be last > and just keep going). I've written a function which takes identical > input and is fully compatible in simple parsing but handles non-option > arguments identically on all systems (by populating a linked list of > strings). It also has support for obscuring sensitive arguments, such as > usernames and passwords. yet another reason to standardize on perl :) note that i actually prefer c to perl, but in this case i think perl would be the best thing to go with. if we had a consistant cmdline interface, there's nothing that would prevent the underlying code from changing later anyway. sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From noreply at sourceforge.net Wed Mar 9 10:34:25 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 9 10:34:25 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1107524 ] check_ping, segfault, popen problems Message-ID: Bugs item #1107524, was opened at 2005-01-22 22:39 Message generated for change (Comment added) made by dael You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1107524&group_id=29880 Category: Parsing problem Group: CVS Status: Open Resolution: None Priority: 7 Submitted By: gprosser (gprosser) Assigned to: Nobody/Anonymous (nobody) Summary: check_ping, segfault, popen problems Initial Comment: check_ping.c, including the current version in CVS, installs a signal handler for SIGALRM called popen_timeout_alarm_handler on startup, and sets an alarm to interrupt it later so the plugin doesn't run forever. However, the popen handler is set to kill the processes that was opened when an ALRM hits, and in certain circumstances (DNS timeouts) the plugin is still resolving the hostname of the target and has not yet opened a command. This leads to SIGSEGV when popen_timeout_(etc) tries to dereference a null pointer looking for what process to kill. I would suggest a safer benign signal handler to handle DNS timeouts be installed in the first case, and then changed just before the process is actually popened to the current handler. Thanks. -gnp ---------------------------------------------------------------------- Comment By: Daniel Graupner (dael) Date: 2005-03-09 18:33 Message: Logged In: YES user_id=577827 I have a similar problem, maybe it is related to this one. I have a lot of lines like pid xxxxx (check_ping), uid 1002: exited on signal 11 in my /var/log/messages. My notes on that: We have Laserlink between our gateway and the "world", everytime it is raining or snowing the connection is really slow or temporarily crashes. We have some pings that "go" over this line. The time of the crashes seems to be at the same time the laserlink is down. ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-02-04 00:05 Message: Logged In: YES user_id=664364 Raising priority on this one. Cannot reproduce myself. Any test cases available? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1107524&group_id=29880 From tonvoon at mac.com Wed Mar 9 13:01:23 2005 From: tonvoon at mac.com (Ton Voon) Date: Wed Mar 9 13:01:23 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <422EB5F5.3040208@op5.se> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> Message-ID: <3EBD258A-90DE-11D9-B22A-000A95D47298@mac.com> Hmmmm. On 9 Mar 2005, at 08:38, Andreas Ericsson wrote: >> - consolidation of duplicate code >> depending on what we learn from the above two, it might make >> sense to develop a common code base to reduce code redundancy. > > This is an area where much can be gained. The plugin devel api today > isn't very useful. > > For spawning commands, there should be a function that takes as input > the command line, and returns the output and return code of the > command. This would accomplish much and get rid of a LOT of duplicate > code in the plugins. > > For snmp, there should be a function that takes a snmp_auth struct > (which needs to be invented) and a list of oid's to fetch, and then > returns the values of those oid's in an array. Good idea. In the general case, common code base is a good goal. > For argument parsing, the getopt_long function might be all good and > well, but it's behaviour on various systems is undocumented (some > break parsing on first non-option argument, other reorder nonopts to > be last and just keep going). This is just plain wrong. We use getopt.c from the GNNU coreutils project. We ignore any system implementations of getopt. If you find something wrong, I'll be happy to accept a patch and I will also push it upstream to the GNU coreutils project. But, without a patch or an accurate bug report, I am taking your opinions with a huge pinch of salt. > I've written a function which takes identical input and is fully > compatible in simple parsing but handles non-option arguments > identically on all systems (by populating a linked list of strings). > It also has support for obscuring sensitive arguments, such as > usernames and passwords. Interesting idea, especially obscuring sensitive arguments. Patch? I'm sure GNU coreutils may be interested. > Lately I've become fed up with the official plugin distribution. The > number of distributed bugs in allegedly stable releases is just too > much work to sort out, so I've started hacking up my own framework > into which I'll import the current plugins whith changes as necessary. I don't think this is a very productive comment. You work in a company that sells Nagios so you can spend all your company time on our software. The rest of us do it while we get on with life. Ton From noreply at sourceforge.net Wed Mar 9 13:06:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 9 13:06:20 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159624 ] Compile and Link Error on Solaris 2.6 Message-ID: Bugs item #1159624, was opened at 2005-03-09 07:06 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 Category: None Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) >Assigned to: Ton Voon (tonvoon) Summary: Compile and Link Error on Solaris 2.6 Initial Comment: With Sun WorkShop Compiler C++ 4.2: My Workaround get the Plugins Running: - The old kompiler does not understand the C++- Comment // in C files. Take /* ... */ e.g. const char *program_name = "check_disk"; /* Required for coreutils libs */ The list of found C++ comments in 1.4 check_disk.c : Line 22 check_smtp.c lines 185,257,258,613 check_ups.c line 411 - unresolved symbols (also Solaris 8 with Forte 6 Update 2 !!) (e.g. gethostbyname) in Makefile the correct List of LIBS: LIBS = -lgen -lsocket -lnsl 73 de DF7BE ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2005-03-09 21:05 Message: Logged In: YES user_id=664364 Wilfried, Thanks for the bug report. This has been fixed in CVS HEAD. Please try the snapshot to confirm. http://nagiosplug.sf.net/snapshot Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 From sghosh at sghosh.org Wed Mar 9 13:53:45 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Wed Mar 9 13:53:45 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050309145432.GA18072@seanius.net> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> <20050309145432.GA18072@seanius.net> Message-ID: inline On Wed, 9 Mar 2005, sean finney wrote: > On Wed, Mar 09, 2005 at 09:38:13AM +0100, Andreas Ericsson wrote: >>> bringing in as many snmp-like checks as possible. for unix hosts >>> there's all kinds of stuff in the ucd/net and host mibs. i could >>> build a list if it'd be helpful. >> >> It most likely would. If it's standardized things it would be most >> useful to have the OID's. It's faster to use and doesn't require the MIB >> to be installed. > > yeah, i wasn't planning on using the actual mibs, since there isn't a > point and like you said it requires more stuff to be around. below > is a basic rundown of what you can monitor. things marked with a '+' > are stand-alone entries. things marked with a '*' are indexed entries. > > ucd/net mib: > > * processes (by name, like "httpd") > - built in minimum / maximum threshold (server side configured) > - total count > + virtual memory > - total / used / free > * disks (not automatically exported, configured server side) > - total / used / free > - built in minimum free space threshold (server side configured) > + load average > - 1, 5, 10 minute averages > - built in maximum threshold (server side configured) > + cpu usage > - user, system, nice > > there's more in there, but that's what i think is monitorable for > practical usage. > > mib-2/host mib: > > * interfaces > - all the interface stuff (traffic, errors) > + tcp connections > - num active connections > - max connection threshold > - traffic / errors > * tcp connections > - individual src,sport,dst,dport connections (could maybe detect dos) > + udp (same as non-indexed tcp, minus connections) > + number logged in users > + total number processes > * disks (same as ucd/net, but automatically exported and no threshold) > * per process cpu / mem usage This is a good start. - Feel like refining them some more. I don't know if all the data is necessarily useful. Also a list of snmp-plugins in the wild that cover some of these would be useful. It would also be a "good thing" to get some feedback from PerfParse folks about perfdata formats and possibility of feeding them raw counters for somethings like traffic and errors so the plugins does not have to calc rate. For plugins returning raw counters - we would not want to provide any status changes other than unknown or ok. check_rrd_data would be used for threshold monitoring. > > and again, there's more, but this is what i found queryable for > practical purposes on a default linux/net-snmp install. > >>> - consistancy of snmp plugin interface >>> >>> common cmdline interface, normalized cmd naming scheme. there'll be >>> some cmdline options that will be common to every plugin (community, >>> snmp version, host, port), and some that aren't. >>> >> >> Naturally. I was thinking -C to mean credentials and supply >> username,password for snmp v3. SNMP v3 would be marked with the >> inclusion of the authentication method (authpriv and that sort of thing). The snmp plugins in the dist have common cli options. We had decided on -C for community only and additional options for v3 auth/encrypt. While there has been some requests to turn community into a standard macro, I am not necessarily in favor of it. Additional multi-purpose USERx macros would be preferable if folks are bumping up against the number of macro limit. > > this brings up something i've been thinking about... the one tricky thing > about snmp community / user / pass credentials is that this is something > likely to be different between groups of hosts (or even host-by-host). > so, setting up a generic template for checking such things in a > hostgroup isn't too easy. istr hearing something on nagios-devel about > the inclusion of an "snmp community" host object setting / macro in > nagios 2, is that true? otherwise (or maybe in addition) it might > be wise to provide a way to supply the authentication data outside > of the cmdline. > >>> - consolidation of duplicate code >> >> This is an area where much can be gained. The plugin devel api today >> isn't very useful. >> >> For spawning commands, there should be a function that takes as input >> the command line, and returns the output and return code of the command. >> This would accomplish much and get rid of a LOT of duplicate code in the >> plugins. spopen does that I think... > > in this particular case i don't know that it would be helpful, as i > wouldn't want to have to execute an snmpwalk command for every check, > but i could see how it might be helpful in other situations. > >> For snmp, there should be a function that takes a snmp_auth struct >> (which needs to be invented) and a list of oid's to fetch, and then >> returns the values of those oid's in an array. > for snmp - I would like to see a framework around the net-snmp libs rather than depending on forking a shell. > i was kind of thinking this would be a lot simpler using perl scripts > for the snmp checks, in which case we could design more easily > extendable functions to do the work. > >> For argument parsing, the getopt_long function might be all good and >> well, but it's behaviour on various systems is undocumented (some break >> parsing on first non-option argument, other reorder nonopts to be last >> and just keep going). I've written a function which takes identical >> input and is fully compatible in simple parsing but handles non-option >> arguments identically on all systems (by populating a linked list of >> strings). It also has support for obscuring sensitive arguments, such as >> usernames and passwords. If there is a need to obscure stuff on the management server - there are bigger issues than monitoring... > > yet another reason to standardize on perl :) note that i actually > prefer c to perl, but in this case i think perl would be the best > thing to go with. if we had a consistant cmdline interface, there's > nothing that would prevent the underlying code from changing later > anyway. > perl is always a good language for a quick solution - hence the number of perl plugins. But some of these have been around for a few years know and are pretty stable; a C implementation would speed up the execution cycle for the larger installs. -- -sg From sghosh at sghosh.org Wed Mar 9 14:04:14 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Wed Mar 9 14:04:14 2005 Subject: 8Re: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> Message-ID: On Fri, 4 Mar 2005, Ton Voon wrote: > Hi! > > I've taken a break from the plugins, but I can put some time back in now. > There looks to be little development, but lots of bug reports coming in, so > that's more stuff to get on with! > > I've had a think about the discussions that Andreas Ericsson and Terje Bless > had about version levels (thread "Hooray - 1.4 is out! What next?") and I > think they make sense. So what I've done now is branch at the current CVS to > 1_4-patches. Please commit to HEAD for the 1.5 release. > > If you come across a bug that should be applied to 1.4 as well as to HEAD, > please fix HEAD and 1_4-patches. Please shout up if you think there should be > a 1.4.1 release (does the check_icmp fix in makefile warrant it right now?). > > I'll also change the SF snapshot to only include CVS HEAD and the 1.4 branch > now, so 1.3 is truly dead. > > I've also updated doc/RELEASING to include these instructions, so they don't > get lost next time. > > So, what do people want to see for 1.5? My first thoughts are: > - more translations > - ps checks in configure.in to base on OS first, then "figuring it out" > - a better web site at http://nagiosplug.sf.net > - move more plugins from contrib into core > > I'm looking for volunteers as well as wish lists. :) > > Ton > Agree with the list Additions: - documentations/howtos/examples (I think that this fell off the list in '03) - some platform specific directories and non-portable plugins (win32) - perhaps a separate CVS module for the CPAN Nagios::* modules - CVS module or dir for report generation scripts and notification scripts -- -sg From ae at op5.se Wed Mar 9 15:24:31 2005 From: ae at op5.se (Andreas Ericsson) Date: Wed Mar 9 15:24:31 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <3EBD258A-90DE-11D9-B22A-000A95D47298@mac.com> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> <3EBD258A-90DE-11D9-B22A-000A95D47298@mac.com> Message-ID: <422F854C.5090809@op5.se> Ton Voon wrote: > Hmmmm. > > On 9 Mar 2005, at 08:38, Andreas Ericsson wrote: > >>> - consolidation of duplicate code >>> depending on what we learn from the above two, it might make >>> sense to develop a common code base to reduce code redundancy. >> >> >> This is an area where much can be gained. The plugin devel api today >> isn't very useful. >> >> For spawning commands, there should be a function that takes as input >> the command line, and returns the output and return code of the >> command. This would accomplish much and get rid of a LOT of duplicate >> code in the plugins. >> >> For snmp, there should be a function that takes a snmp_auth struct >> (which needs to be invented) and a list of oid's to fetch, and then >> returns the values of those oid's in an array. > > > Good idea. In the general case, common code base is a good goal. > >> For argument parsing, the getopt_long function might be all good and >> well, but it's behaviour on various systems is undocumented (some >> break parsing on first non-option argument, other reorder nonopts to >> be last and just keep going). > > > This is just plain wrong. We use getopt.c from the GNNU coreutils > project. We ignore any system implementations of getopt. If you find > something wrong, I'll be happy to accept a patch and I will also push it > upstream to the GNU coreutils project. But, without a patch or an > accurate bug report, I am taking your opinions with a huge pinch of salt. > Didn't notice you were using an imported version, so my point is probably moot. I'll still go with my version though. It's about 1/3 of the code in getopt.c. >> I've written a function which takes identical input and is fully >> compatible in simple parsing but handles non-option arguments >> identically on all systems (by populating a linked list of strings). >> It also has support for obscuring sensitive arguments, such as >> usernames and passwords. > > > Interesting idea, especially obscuring sensitive arguments. Patch? I'm > sure GNU coreutils may be interested. > I doubt it. For them it's more about API compatibility. I worry more about code quality and "the user never knows". Also, my approach uses malloc() which is forbidden (for some reason) for getopt(). >> Lately I've become fed up with the official plugin distribution. The >> number of distributed bugs in allegedly stable releases is just too >> much work to sort out, so I've started hacking up my own framework >> into which I'll import the current plugins whith changes as necessary. > > > I don't think this is a very productive comment. You work in a company > that sells Nagios so you can spend all your company time on our > software. The rest of us do it while we get on with life. > You misunderstood. I'm not saying I'll deny the official distribution any work I do. I'm just saying that I won't put in the extra effort to submit patches upstream. Besides the initial four days of patching the last time we released a plugin package I'll have to work extra in the future for each of those patches that doesn't get accepted. That extra work is lost over and over for each patch we need to have that doesn't get in. In the end it turns out to a big, fat, frustrating waste of time. I'll put up our distro for download as soon as most of the work is done. It'll be GPL ofcourse so you can borrow whatever snippets you like. It's the method of contribution I'm fed up with. Not contributing as such. -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Lead Developer From nagios at proy.org Wed Mar 9 15:49:41 2005 From: nagios at proy.org (Patrick Proy) Date: Wed Mar 9 15:49:41 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050309145432.GA18072@seanius.net> Message-ID: <20050309234848.76A7BAC486@www.manubulon.com> Hi, > -----Message d'origine----- > De : nagiosplug-devel-admin at lists.sourceforge.net > [mailto:nagiosplug-devel-admin at lists.sourceforge.net] De la part de > sean finney Objet : Re: [Nagiosplug-devel] Kickoff for 1.5 > [...] > > yeah, i wasn't planning on using the actual mibs, since there isn't a > point and like you said it requires more stuff to be around. below is > a basic rundown of what you can monitor. > things marked with a '+' > are stand-alone entries. things marked with a '*' are indexed > entries. > > ucd/net mib: > > * processes (by name, like "httpd") > - built in minimum / maximum threshold (server side configured) > - total count > + virtual memory > - total / used / free > * disks (not automatically exported, configured server side) > - total / used / free > - built in minimum free space threshold (server side configured) > + load average > - 1, 5, 10 minute averages > - built in maximum threshold (server side configured) > + cpu usage > - user, system, nice > [....] I wrote some perl plugins for (nearly) all this, but i mainly use MIB II for compatibility and so nothing is configured server side. I also tried to export data to performance data when it was possible. When I asked a few months ago, nobody seemed to be willing to group the multiple perl snmp plugins, but it would be a VERY good idea. Patrick nagios at proy.org http://www.manubulon.com/nagios/ From seanius at seanius.net Wed Mar 9 17:24:45 2005 From: seanius at seanius.net (sean finney) Date: Wed Mar 9 17:24:45 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> <20050309145432.GA18072@seanius.net> Message-ID: <20050310012252.GA27785@seanius.net> hi subhendu, i'm going to go ahead and cc nagios-devel on this, as it touches some topics pertinent outside of nagios plugins. sorry to those who start getting double-whammies... background: we're talking about a better integration of snmp based checks in the nagios-plugins. On Wed, Mar 09, 2005 at 04:52:43PM -0500, Subhendu Ghosh wrote: > > (sean produces list of what could be monitored via standard mibs) > This is a good start. - Feel like refining them some more. I don't know if > all the data is necessarily useful. Also a list of snmp-plugins in the > wild that cover some of these would be useful. i'll see about refining them as well as building a list of effort already spent (including the scripts mentioned by patrick in the next mail). > It would also be a "good thing" to get some feedback from PerfParse folks > about perfdata formats and possibility of feeding them raw counters for > somethings like traffic and errors so the plugins does not have to calc > rate. For plugins returning raw counters - we would not want to provide > any status changes other than unknown or ok. check_rrd_data would be used > for threshold monitoring. for most counter-based metrics i'm probably going to be producing the rrd's from cacti's snmp poller to begin with, though using nagios to monitor thresholds via check_rrd_data would be a major plus for me[1]. then again, cacti can work on externally produced rrd's, so if nagios made the snmp polling easier i'd probably follow the path of least resistance. in any case i agree that it's not the business of the plugin itself to attempt to keep any kind of state. > The snmp plugins in the dist have common cli options. We had decided on > -C for community only and additional options for v3 auth/encrypt. cool. > While there has been some requests to turn community into a standard > macro, I am not necessarily in favor of it. Additional multi-purpose USERx > macros would be preferable if folks are bumping up against the number of > macro limit. i don't think you could use the USERx macros in many situations. here's an example, similar to the one i'm currently in: let's say you have 3 groups of 10 unix hosts. each group belongs to a different department and has a different snmp community. now lets say you have a common "unix host" template which includes among other things a check command that uses an snmp plugin. how can this check command know which community to use for which host, even with USERx? now i'm not saying that a snmp_community setting + a macro would not be a bit of a hack, but then again, that's what the USERx stuff is too. what's *really* needed (and what could maybe be helpful in a more generalized sense) is either context-based macros, or an ability to override pre-existing macros on a per-object basis. > for snmp - I would like to see a framework around the net-snmp libs rather > than depending on forking a shell. agreed. all that forking can get really expensive, and relying on the existence/function/execution of cmdline apps brings in other complications too. sean [1] there's actually an effort within cacti to produce threshold monitoring and event handling, which i think is totally pointless. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From sghosh at sghosh.org Wed Mar 9 17:35:12 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Wed Mar 9 17:35:12 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050310012252.GA27785@seanius.net> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> <20050309145432.GA18072@seanius.net> <20050310012252.GA27785@seanius.net> Message-ID: On Wed, 9 Mar 2005, sean finney wrote: > hi subhendu, > > i'm going to go ahead and cc nagios-devel on this, as it touches some > topics pertinent outside of nagios plugins. sorry to those who start > getting double-whammies... > > background: we're talking about a better integration of snmp based > checks in the nagios-plugins. > > On Wed, Mar 09, 2005 at 04:52:43PM -0500, Subhendu Ghosh wrote: >>> (sean produces list of what could be monitored via standard mibs) >> This is a good start. - Feel like refining them some more. I don't know if >> all the data is necessarily useful. Also a list of snmp-plugins in the >> wild that cover some of these would be useful. > > i'll see about refining them as well as building a list of effort > already spent (including the scripts mentioned by patrick in the > next mail). > >> It would also be a "good thing" to get some feedback from PerfParse folks >> about perfdata formats and possibility of feeding them raw counters for >> somethings like traffic and errors so the plugins does not have to calc >> rate. For plugins returning raw counters - we would not want to provide >> any status changes other than unknown or ok. check_rrd_data would be used >> for threshold monitoring. > > for most counter-based metrics i'm probably going to be producing the > rrd's from cacti's snmp poller to begin with, though using nagios to > monitor thresholds via check_rrd_data would be a major plus for me[1]. > then again, cacti can work on externally produced rrd's, so if nagios > made the snmp polling easier i'd probably follow the path of least > resistance. in an2y case i agree that it's not the business of the plugin > itself to attempt to keep any kind of state. > >> The snmp plugins in the dist have common cli options. We had decided on >> -C for community only and additional options for v3 auth/encrypt. > > cool. > >> While there has been some requests to turn community into a standard >> macro, I am not necessarily in favor of it. Additional multi-purpose USERx >> macros would be preferable if folks are bumping up against the number of >> macro limit. > > i don't think you could use the USERx macros in many situations. here's > an example, similar to the one i'm currently in: > > let's say you have 3 groups of 10 unix hosts. each group belongs to a > different department and has a different snmp community. now lets say > you have a common "unix host" template which includes among other things > a check command that uses an snmp plugin. how can this check command > know which community to use for which host, even with USERx? > > now i'm not saying that a snmp_community setting + a macro would not be > a bit of a hack, but then again, that's what the USERx stuff is too. > what's *really* needed (and what could maybe be helpful in a more > generalized sense) is either context-based macros, or an ability > to override pre-existing macros on a per-object basis. > Templates allow for over-ride - but in your above example, you would have to have a different "unix host" template for each group. Context macros and templates would get really convoluted real fast. >> for snmp - I would like to see a framework around the net-snmp libs rather >> than depending on forking a shell. > > agreed. all that forking can get really expensive, and relying on > the existence/function/execution of cmdline apps brings in other complications > too. > > > sean > > [1] there's actually an effort within cacti to produce threshold > monitoring and event handling, which i think is totally pointless. Cricket already does this - snmp traps based on thresholds - feed them back to Nagios... -- -sg From sghosh at sghosh.org Wed Mar 9 17:40:59 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Wed Mar 9 17:40:59 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 (SNMP traps) In-Reply-To: <20050310012252.GA27785@seanius.net> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> <20050304223746.GA28563@seanius.net> <22FB13BC-900D-11D9-B22A-000A95D47298@mac.com> <20050309051848.GA8436@seanius.net> <422EB5F5.3040208@op5.se> <20050309145432.GA18072@seanius.net> <20050310012252.GA27785@seanius.net> Message-ID: An FYI- I have been working on defining some SNMP objects for Nagios to allow feeding to other NMS. Currently have a ROOT and NOTIFY mibs defined. Have a working but not ready for release notification script that sends out a trap based on these objects. Use v2b macros. The Nagios tree is officially registered under IANA's enterprises namespace. -- -sg -------------- next part -------------- NAGIOS-ROOT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, enterprises FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC; nagios MODULE-IDENTITY LAST-UPDATED "200501200000Z" -- January 20, 2005 ORGANIZATION "Nagios" CONTACT-INFO " Subhendu Ghosh Telephone: +1 201 232 2851 Email: sghosh at users.sourceforge.net Nagios Information: http://www.nagios.org " DESCRIPTION "Objects for Nagion(tm) NMS" REVISION "200501200000Z" --January 20, 2005 DESCRIPTION "Initial Version" ::= {enterprises 20006} -- -- Textual Conventions -- NotifyType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A string identifying the type of notification that is being sent (PROBLEM, RECOVERY, ACKNOWLEDGEMENT, FLAPPINGSTART or FLAPPINGSTOP). " SYNTAX INTEGER { problem(0), recovery(1), acknowledgement(2), flappingstart(3), flappingstop(4) } HostStateID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A number that corresponds to the current state of the host: 0=UP, 1=DOWN, 2=UNREACHABLE." SYNTAX INTEGER { up(0), down(1), unreachable(3) } HostStateType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A string indicating the state type for the current host check (HARD or SOFT). Soft states occur when host checks return a non-OK (non-UP) state and are in the process of being retried. Hard states result when host checks have been checked a specified maximum number of times." SYNTAX INTEGER { hard(0), soft(1) } ServiceStateID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A number that corresponds to the current state of the service: 0=OK, 1=WARNING, 2=CRITICAL, 3=UNKNOWN. " SYNTAX INTEGER{ ok(0), warning(1), critical(2), unknown(3) } END -------------- next part -------------- NAGIOS-NOTIFY-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32 FROM SNMPv2-SMI nagios,NotifyType,HostStateID,HostStateType,ServiceStateID FROM NAGIOS-ROOT-MIB; nagiosNotify MODULE-IDENTITY LAST-UPDATED "200501200000Z" -- January 20, 2005 ORGANIZATION "Nagios" CONTACT-INFO " Subhendu Ghosh Telephone: +1 201 232 2851 Email: sghosh at users.sourceforge.net Nagios Information: http://www.nagios.org " DESCRIPTION "Objects for Nagion(tm) events. There are 2 primary table reflecting the division in Nagios for Host events and Service events. The 2 tables are extended the HostNotifyTable and the ServiceNotifyTable to keep track of the notifications based on events. The tables entries themselves are not accessible but are used for OID entries for TRAP/INFORM notifications. These objects are based on the macros defined in Nagios v2.0 " REVISION "200501200000Z" --January 20, 2005 DESCRIPTION "Initial Version" ::= { nagios 1 } nagiosHostEventTable OBJECT-TYPE SYNTAX SEQUENCE OF HostEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Nagios host events" ::= { nagiosNotify 1 } HostEventEntry ::= SEQUENCE { nHostEventIndex Integer32, nHostname OCTET STRING, nHostAlias OCTET STRING, nHostStateID HostStateID, nHostStateType HostStateType, nHostAttempt Integer32, nHostDurationSec Integer32, nHostGroupName OCTET STRING, nHostLastCheck INTEGER, nHostLastChange INTEGER, nHostLastUp INTEGER, nHostLastDown INTEGER, nHostLastUnreachable INTEGER, nHostOutput OCTET STRING, nHostPerfData OCTET STRING } nagiosHostEventEntry OBJECT-TYPE SYNTAX HostEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each notification event" INDEX { nHostEventIndex } ::= { nagiosHostEventTable 1 } nHostEventIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object uniquely identifies this host event entry" ::= { nagiosHostEventEntry 1 } nHostname OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Hostname as specified in the Nagios configuration file." ::= { nagiosHostEventEntry 2 } nHostAlias OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The host alias as specified in the Nagios configuration file" ::= { nagiosHostEventEntry 3 } nHostStateID OBJECT-TYPE SYNTAX HostStateID MAX-ACCESS read-only STATUS current DESCRIPTION "The host state as defined by the HOSTSTATEID macro" ::= { nagiosHostEventEntry 4 } nHostStateType OBJECT-TYPE SYNTAX HostStateType MAX-ACCESS read-only STATUS current DESCRIPTION "The host state as defined by the HOSTSTATETYPE macro" ::= { nagiosHostEventEntry 5 } nHostAttempt OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of the current host check retry. For instance, if this is the second time that the host is being rechecked, this will be the number two. Current attempt number is really only useful when writing host event handlers for soft states that take a specific action based on the host retry number. The host state as defined by the HOSTSTATEID macro" ::= { nagiosHostEventEntry 6 } nHostDurationSec OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number indicating the number of seconds that the host has spent in its current state" ::= { nagiosHostEventEntry 7 } nHostGroupName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The short name of the hostgroup that this host belongs to. This value is taken from the hostgroup_name directive in the hostgroup definition. If the host belongs to more than one hostgroup this macro will contain the name of just one of them." ::= { nagiosHostEventEntry 8 } nHostLastCheck OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which a check of the host was last performed." ::= { nagiosHostEventEntry 9 } nHostLastChange OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time the host last changed state." ::= { nagiosHostEventEntry 10 } nHostLastUp OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the host was last detected as being in an UP state." ::= { nagiosHostEventEntry 11 } nHostLastDown OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the host was last detected as being in an DOWN state." ::= { nagiosHostEventEntry 12 } nHostLastUnreachable OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the host was last detected as being in an UNREACHABLE state." ::= { nagiosHostEventEntry 13 } nHostOutput OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The text output from the last host check (i.e. Ping OK)." ::= { nagiosHostEventEntry 14 } nHostPerfData OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains any performance data that may have been returned by the last host check." ::= { nagiosHostEventEntry 15 } -- -- Host Notifications nagiosHostNotifyTable OBJECT-TYPE SYNTAX SEQUENCE OF HostNotifyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Nagios host notifications" ::= {nagiosNotify 2} HostNotifyEntry ::= SEQUENCE { nHostNotifyType NotifyType, nHostNotifyNum Integer32, nHostAckAuthor OCTET STRING, nHostAckComment OCTET STRING } nagiosHostNotifyEntry OBJECT-TYPE SYNTAX HostNotifyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Nagios host notifications extends the nagiosHostEventTable when a notification is generated for an event." INDEX { nHostEventIndex } ::= { nagiosHostNotifyTable 1 } nHostNotifyType OBJECT-TYPE SYNTAX NotifyType MAX-ACCESS read-only STATUS current DESCRIPTION "This identifies the type of " ::= { nagiosHostNotifyEntry 1 } nHostNotifyNum OBJECT-TYPE SYNTAX NotifyType MAX-ACCESS read-only STATUS current DESCRIPTION "This identifies the type of " ::= { nagiosHostNotifyEntry 2 } nHostAckAuthor OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "A string containing the name of the user who acknowledged the host problem. This macro is only valid in notifications where the $NOTIFICATIONTYPE$ macro is set to ACKNOWLEDGEMENT." ::= { nagiosHostNotifyEntry 3 } nHostAckComment OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "A string containing the acknowledgement comment that was entered by the user who acknowledged the host problem. This macro is only valid in notifications where the $NOTIFICATIONTYPE$ macro is set to ACKNOWLEDGEMENT" ::= { nagiosHostNotifyEntry 4 } -- -- Service Events -- nagiosSvcEventTable OBJECT-TYPE SYNTAX SEQUENCE OF SvcEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Nagios service notifications" ::= { nagiosNotify 3 } SvcEventEntry ::= SEQUENCE { nSvcEventIndex Integer32, nSvcHostname OCTET STRING, nSvcHostAlias OCTET STRING, nSvcHostStateID HostStateID, nSvcHostStateType HostStateType, nSvcDesc OCTET STRING, nSvcStateID ServiceStateID, nSvcAttempt Integer32, nSvcDurationSec Integer32, nSvcGroupName OCTET STRING, nSvcLastCheck INTEGER, nSvcLastChange INTEGER, nSvcLastOK INTEGER, nSvcLastWarn INTEGER, nSvcLastCrit INTEGER, nSvcLastUnkn INTEGER, nSvcOutput OCTET STRING, nSvcPerfData OCTET STRING } nagiosSvcEventEntry OBJECT-TYPE SYNTAX SvcEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Nagios service events." INDEX { nSvcEventIndex } ::= { nagiosSvcEventTable 1 } nSvcEventIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object uniquely identifies this service event entry" ::= { nagiosSvcEventEntry 1 } nSvcHostname OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "Hostname as specified in the Nagios configuration file." ::= { nagiosSvcEventEntry 2 } nSvcHostAlias OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The host alias as specified in the Nagios configuration file" ::= { nagiosSvcEventEntry 3 } nSvcHostStateID OBJECT-TYPE SYNTAX HostStateID MAX-ACCESS read-only STATUS current DESCRIPTION "A number that corresponds to the current state of the service: 0=OK, 1=WARNING, 2=CRITICAL, 3=UNKNOWN." ::= { nagiosSvcEventEntry 4 } nSvcHostStateType OBJECT-TYPE SYNTAX HostStateType MAX-ACCESS read-only STATUS current DESCRIPTION "Whether the host is in a hard or soft state." ::= { nagiosSvcEventEntry 5 } nSvcDesc OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "This value is taken from the description directive of the service definition." ::= { nagiosSvcEventEntry 6 } nSvcStateID OBJECT-TYPE SYNTAX ServiceStateID MAX-ACCESS read-only STATUS current DESCRIPTION " A number that corresponds to the current state of the service: 0=OK, 1=WARNING, 2=CRITICAL, 3=UNKNOWN" ::= { nagiosSvcEventEntry 7 } nSvcAttempt OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of the current service check retry. For instance, if this is the second time that the service is being rechecked, this will be the number two. Current attempt number is really only useful when writing service event handlers for soft states that take a specific action based on the service retry number." ::= { nagiosSvcEventEntry 8 } nSvcDurationSec OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number indicating the number of seconds that the service has spent in its current state." ::= { nagiosSvcEventEntry 9 } nSvcGroupName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The short name of the servicegroup that this service belongs to. This value is taken from the servicegroup_name directive in the servicegroup definition. If the service belongs to more than one servicegroup this object will contain the name of just one of them." ::= { nagiosSvcEventEntry 10 } nSvcLastCheck OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which a check of the service was last performed." ::= { nagiosSvcEventEntry 11 } nSvcLastChange OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time the service last changed state." ::= { nagiosSvcEventEntry 12 } nSvcLastOK OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the service was last detected as being in an OK state." ::= { nagiosSvcEventEntry 13 } nSvcLastWarn OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the service was last detected as being in a WARNING state." ::= { nagiosSvcEventEntry 14 } nSvcLastCrit OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the service was last detected as being in a CRITICAL state." ::= { nagiosSvcEventEntry 15 } nSvcLastUnkn OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a timestamp in time_t format (seconds since the UNIX epoch) indicating the time at which the service was last detected as being in an UNKNOWN state." ::= { nagiosSvcEventEntry 16 } nSvcOutput OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "The text output from the last service check (i.e. Ping OK)." ::= { nagiosSvcEventEntry 17 } nSvcPerfData OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains any performance data that may have been returned by the last service check." ::= { nagiosSvcEventEntry 18 } -- -- Service Notifications -- nagiosSvcNotifyTable OBJECT-TYPE SYNTAX SEQUENCE OF SvcNotifyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Nagios service notifications." ::= { nagiosNotify 4 } SvcNotifyEntry ::= SEQUENCE { nSvcNotifyType NotifyType, nSvcNotifyNum Integer32, nSvcAckAuthor OCTET STRING, nSvcAckComment OCTET STRING } nagiosSvcNotifyEntry OBJECT-TYPE SYNTAX SvcNotifyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Nagios service notifications extends the nagiosSvcEnevtsTable when a notification is generated for an event." INDEX { nSvcEventIndex } ::= { nagiosSvcNotifyTable 1} nSvcNotifyType OBJECT-TYPE SYNTAX NotifyType MAX-ACCESS read-only STATUS current DESCRIPTION "A string identifying the type of notification that is being sent (PROBLEM, RECOVERY, ACKNOWLEDGEMENT, FLAPPINGSTART or FLAPPINGSTOP)." ::= { nagiosSvcNotifyEntry 1 } nSvcNotifyNum OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The current notification number for the service or host. The notification number increases by one (1) each time a new notification is sent out for a host or service (except for acknowledgements). The notification number is reset to 0 when the host or service recovers (after the recovery notification has gone out). Acknowledgements do not cause the notification number to increase." ::= { nagiosSvcNotifyEntry 2 } nSvcAckAuthor OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "A string containing the name of the user who acknowledged the service problem. This object is only valid in notifications where the nSvcNotifyType object is set to ACKNOWLEDGEMENT." ::= { nagiosSvcNotifyEntry 3 } nSvcAckComment OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "A string containing the acknowledgement comment that was entered by the user who acknowledged the service problem. This object is only valid in notifications where the nSvcNotifyType object is set to ACKNOWLEDGEMENT." ::= { nagiosSvcNotifyEntry 4 } -- -- Events and Notifications -- nHostEvent NOTIFICATION-TYPE OBJECTS { nHostname, nHostStateID, nHostStateType, nHostAttempt, nHostDurationSec, nHostGroupName, nHostLastCheck, nHostLastChange, nHostOutput } STATUS current DESCRIPTION "The SNMP trap that is generated as a result of an event with the host in Nagios." ::= { nagiosNotify 5 } nHostNotify NOTIFICATION-TYPE OBJECTS { nHostNotifyType, nHostNotifyNum, nHostAckAuthor, nHostAckComment, nHostname, nHostStateID, nHostStateType, nHostAttempt, nHostDurationSec, nHostGroupName, nHostLastCheck, nHostLastChange, nHostOutput } STATUS current DESCRIPTION "The SNMP trap that is generated as a result of an event requiring notification for a host in Nagios." ::= { nagiosNotify 6 } nSvcEvent NOTIFICATION-TYPE OBJECTS { nHostname, nHostStateID, nSvcDesc, nSvcStateID, nSvcAttempt, nSvcDurationSec, nSvcGroupName, nSvcLastCheck, nSvcLastChange, nSvcOutput } STATUS current DESCRIPTION "The SNMP trap that is generated as a result of an event with the service in Nagios." ::= { nagiosNotify 7 } nSvcNotify NOTIFICATION-TYPE OBJECTS { nSvcNotifyType, nSvcNotifyNum, nSvcAckAuthor, nSvcAckComment, nHostname, nHostStateID, nSvcDesc, nSvcStateID, nSvcAttempt, nSvcDurationSec, nSvcGroupName, nSvcLastCheck, nSvcLastChange, nSvcOutput } STATUS current DESCRIPTION "The SNMP trap that is generated as a result of an event requiring notification for a service in Nagios." ::= { nagiosNotify 8 } END From hmann at itgroundwork.com Wed Mar 9 18:00:04 2005 From: hmann at itgroundwork.com (Harper Mann) Date: Wed Mar 9 18:00:04 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050309234848.76A7BAC486@www.manubulon.com> Message-ID: Hi Everyone, There are several items in an SNMP plugin discussion we're interested in and are working on. What I can remember off the top of my head is: 1) How to manage and alarm on counter data like interface traffic, etc. We use check_rrd, which was mentioned earlier in this thread, and perhaps that's sufficient since we customarily store and graph, but standardizing this would be good. We're not sure RRDTool will scale to sufficient size installations. 2) We've had a request to collect 3-4 SNMP values (in, out, errors) from more than 10,000 interfaces every 15 minutes so we're looking into how to scale to such a large installation. Aside from how to get plugins to keep up with collecting, what's the best way to store so much performance data? 3) Fix the performance data so it conforms to the project standards and manages OIDs and Symbolic names well for multiple requests. This should be good! Regards, - Harper Harper Mann Groundwork Open Source Solutions 510-599-2075 (cell) http://itgroundwork.com > -----Original Message----- > From: nagiosplug-devel-admin at lists.sourceforge.net [mailto:nagiosplug- > devel-admin at lists.sourceforge.net] On Behalf Of Patrick Proy > Sent: Wednesday, March 09, 2005 3:49 PM > To: 'NagiosPlug Devel' > Subject: RE: [Nagiosplug-devel] Kickoff for 1.5 > > Hi, > > > -----Message d'origine----- > > De : nagiosplug-devel-admin at lists.sourceforge.net > > [mailto:nagiosplug-devel-admin at lists.sourceforge.net] De la part de > > sean finney Objet : Re: [Nagiosplug-devel] Kickoff for 1.5 > > > [...] > > > > yeah, i wasn't planning on using the actual mibs, since there isn't a > > point and like you said it requires more stuff to be around. below is > > a basic rundown of what you can monitor. > > things marked with a '+' > > are stand-alone entries. things marked with a '*' are indexed > > entries. > > > > ucd/net mib: > > > > * processes (by name, like "httpd") > > - built in minimum / maximum threshold (server side configured) > > - total count > > + virtual memory > > - total / used / free > > * disks (not automatically exported, configured server side) > > - total / used / free > > - built in minimum free space threshold (server side configured) > > + load average > > - 1, 5, 10 minute averages > > - built in maximum threshold (server side configured) > > + cpu usage > > - user, system, nice > > > [....] > > I wrote some perl plugins for (nearly) all this, but i mainly use MIB II > for > compatibility and so nothing is configured server side. > I also tried to export data to performance data when it was possible. > > When I asked a few months ago, nobody seemed to be willing to group the > multiple perl snmp plugins, but it would be a VERY good idea. > > Patrick > nagios at proy.org > http://www.manubulon.com/nagios/ > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________________ > 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 sghosh at sghosh.org Wed Mar 9 18:22:21 2005 From: sghosh at sghosh.org (Subhendu Ghosh) Date: Wed Mar 9 18:22:21 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: References: Message-ID: On Wed, 9 Mar 2005, Harper Mann wrote: > Hi Everyone, > > There are several items in an SNMP plugin discussion we're interested in and > are working on. What I can remember off the top of my head is: > > 1) How to manage and alarm on counter data like interface traffic, etc. We > use check_rrd, which was mentioned earlier in this thread, and perhaps > that's sufficient since we customarily store and graph, but standardizing > this would be good. We're not sure RRDTool will scale to sufficient size > installations. > > 2) We've had a request to collect 3-4 SNMP values (in, out, errors) from > more than 10,000 interfaces every 15 minutes so we're looking into how to > scale to such a large installation. Aside from how to get plugins to keep > up with collecting, what's the best way to store so much performance data? > > 3) Fix the performance data so it conforms to the project standards and > manages OIDs and Symbolic names well for multiple requests. > Separate out the functionality - Nagios is primarily a fault management tool. For 10k interface performance choose a performance management(monitor) tool. I've been partial to Cricket to snmp data collection - the snmp engine is pretty well designed so that each device is only contacted once and all the different oids are requested together. (cricket.sf.net) I've seen it scale quite well so long as you can stagger the the hosts groups (ie. not everything runs at the same 15 min interval) and you can use snmp v2 and get-bulk For alarms - either check_rrd or snmptraps from Cricket (and possibly 2Cacti in the near future). By forcing Nagios to do traffic measurements from snmp - the scalability is not present based on the plugin architecture. You need something else to do the active monitor and check the results. For small installs that don't want multiple tools, it would work, but large installs like yours should definitely use separate tools. I used to monitor about the same number of interfaces with mrtg arounf '98-'00. disk i/o was the biggest issue. (ram disk to the rescue). RRDtool scales as well as the underlying hardware (disk i/o) and file layout. -- -sg From seanius at seanius.net Wed Mar 9 19:24:25 2005 From: seanius at seanius.net (sean finney) Date: Wed Mar 9 19:24:25 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <20050309234848.76A7BAC486@www.manubulon.com> References: <20050309145432.GA18072@seanius.net> <20050309234848.76A7BAC486@www.manubulon.com> Message-ID: <20050310032331.GA32467@seanius.net> hi patrick, On Thu, Mar 10, 2005 at 12:48:47AM +0100, Patrick Proy wrote: > I wrote some perl plugins for (nearly) all this, but i mainly use MIB II for > compatibility and so nothing is configured server side. > I also tried to export data to performance data when it was possible. > > When I asked a few months ago, nobody seemed to be willing to group the > multiple perl snmp plugins, but it would be a VERY good idea. i haven't looked closely, but it looks like you've done quite a bit of work on these! i'll definitely spend some time looking at these. sean -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From naoki at valuecommerce.com Wed Mar 9 21:06:06 2005 From: naoki at valuecommerce.com (Naoki) Date: Wed Mar 9 21:06:06 2005 Subject: [Nagiosplug-devel] 1110374 - Patch to check_http.c to enable SSL certificate verification Message-ID: <1110431137.5762.67.camel@dragon.sys.intra> Any chance of this making it into 1.5 ? https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1110374&group_id=29880 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stanley.Hopcroft at IPAustralia.Gov.AU Thu Mar 10 03:30:01 2005 From: Stanley.Hopcroft at IPAustralia.Gov.AU (Stanley Hopcroft) Date: Thu Mar 10 03:30:01 2005 Subject: [Nagiosplug-devel] Re: SNMP + Nag Was: Kickoff for 1.5 In-Reply-To: References: Message-ID: <20050310112854.GA448@IPAustralia.Gov.AU> Dear Folks, Not much here but, On Wed, Mar 09, 2005 at 09:21:23PM -0500, Subhendu Ghosh wrote: > On Wed, 9 Mar 2005, Harper Mann wrote: > > >Hi Everyone, > > > >There are several items in an SNMP plugin discussion we're interested in > >and > >are working on. What I can remember off the top of my head is: > > > >1) How to manage and alarm on counter data like interface traffic, etc. We > >use check_rrd, which was mentioned earlier in this thread, and perhaps > >that's sufficient since we customarily store and graph, but standardizing > >this would be good. We're not sure RRDTool will scale to sufficient size > >installations. > > If the devices support RMON (and most do), then the alarm group transforms the problem into one of trap harvesting (ie define alarm thresholds on trunks in the switch/router) and have it send traps when the threshold is exceeded. Only con is static, non adapatives, thresholds. See below if you want to allow for diurnal/seasonal variation. > >2) We've had a request to collect 3-4 SNMP values (in, out, errors) from > >more than 10,000 interfaces every 15 minutes so we're looking into how to > >scale to such a large installation. Aside from how to get plugins to keep > >up with collecting, what's the best way to store so much performance data? > > > >3) Fix the performance data so it conforms to the project standards and > >manages OIDs and Symbolic names well for multiple requests. > > > > Separate out the functionality - Nagios is primarily a fault management > tool. For 10k interface performance choose a performance > management(monitor) tool. > Absolutely. I think the nomenclature is 1 a poller/collector - interrogates the thingys and saves the data 2 an analyser/presenter - summarise the saved data and report by various means. These are best implemented as separate processes so they can perform without tradeoffs. Non blocking IO with Net::SNMP out performs forking an Net::SNMP::get. Storing data in RRDs has the advantages that 1 Lots of third party applications know and love RRDs (orca, cricket) 2 The Holt-Winters time series prediction algorithm can let the analyser distinguish a daily surge from an anomaly/problem NB Toby the RRD man haa got funding from a client to bring the dev branch RRD - with the HW stuff - into supported production form. 3 the RRDs are self maintaining. Except in exceptional cases there is no need to unload and resize databases when the db fills up (it never does) 4 the storage of an RRD never exceeds what is allocated when the RRD is created. > I've been partial to Cricket to snmp data collection - the snmp engine is > pretty well designed so that each device is only contacted once and all > the different oids are requested together. (cricket.sf.net) > I've seen it scale quite well so long as you can stagger the the hosts > groups (ie. not everything runs at the same 15 min interval) and you can > use snmp v2 and get-bulk > > For alarms - either check_rrd or snmptraps from Cricket (and possibly > 2Cacti in the near future). Sounds good to me if you can't get RMON (or don't/can't configure your devices - although that were the case, you prob couldn't poll them). > > By forcing Nagios to do traffic measurements from snmp - the scalability > is not present based on the plugin architecture. You need something else > to do the active monitor and check the results. Here Here. Let Nag present part of the conclusions - its neat to have the plugin output return a hyperlink to an RRDtool or other CGI that allows the Nag viewer to display the RRDtool graphs. > For small installs that > don't want multiple tools, it would work, but large installs like yours > should definitely use separate tools. Amen brother. > > I used to monitor about the same number of interfaces with mrtg arounf > '98-'00. disk i/o was the biggest issue. (ram disk to the rescue). > > RRDtool scales as well as the underlying hardware (disk i/o) and file > layout. The bottle neck is more likely to be in the poller than RRDtool in my view (that's why there are fpings and so on). > > -- > -sg > Does this adequately sum up what's been presented that's relevant to Nag SNMP plugins ? 1 the plugins should probably confine themselves to checking state rather than collecting/storing performance data (leaving this to a standalone poller that may or may not interact with Nag directly) 2 traffic thresholds are best dealt with by 2.1 standalone poller + analyser submitting passive service check results to Nag (possibly via traps to a trap collector), or 2.2 device specific means (RMON) 3 The probs of dealing with large numbers of communitys remain although it seems to me that the -C option should go a long way to help (maybe in conjunction with a heap of included files defining different arguments for commands. 4 Plugins that save/store state probably don't scale and should thereby be excluded from developer focus 5 It may be worth recognising that SNMP pollers/managers are a good supplement to Nag; the poller is getting close to peak development and therefore effort is only needed in exploiting synergy rather than seeking to do it again with plugins. Yours sincerely. -- Stanley Hopcroft IP Australia Ph: (02) 6283 3189 Fax: (02) 6281 1353 PO Box 200 Woden ACT 2606 http://www.ipaustralia.gov.au -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: disclaimer.txt URL: From dan.hopkins at uk.easynet.net Thu Mar 10 06:38:34 2005 From: dan.hopkins at uk.easynet.net (Dan Hopkins) Date: Thu Mar 10 06:38:34 2005 Subject: [Nagiosplug-devel] check_http longoptions Message-ID: <13E80BCA327C4D43AC2EFCE6B06E53140567D5@exch0-tmshm.uk.easynet.corp> I've been meaning to mention this since the 1.3 release, but as afaics it's still not corrected in the latest 1.4 snapshot, here's a patch diff for the missing longoption support in check_http diff -u check_http.still.broken.c check_http.c --- check_http.still.broken.c Thu Mar 10 10:59:56 2005 +++ check_http.c Thu Mar 10 10:57:08 2005 @@ -226,6 +226,9 @@ {"pagesize", required_argument, 0, 'm'}, {"use-ipv4", no_argument, 0, '4'}, {"use-ipv6", no_argument, 0, '6'}, + {"port", required_argument, 0, 'p'}, + {"authorization", required_argument, 0, 'a'}, + {"expect", required_argument, 0, 'e'}, {0, 0, 0, 0} }; -- Dan Hopkins Systems Developer, easynet Ltd. e: dan.hopkins at uk.easynet.net t: +44(0) 1749 333305 From noreply at sourceforge.net Thu Mar 10 23:21:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 10 23:21:26 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1161156 ] Check tcp with binary data Message-ID: Patches item #1161156, was opened at 2005-03-11 08:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1161156&group_id=29880 Category: Enhancement Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jiri Netolicky (netolish) Assigned to: Nobody/Anonymous (nobody) Summary: Check tcp with binary data Initial Comment: This small patch enhance check_tcp plugin to be able send and receive (and of course compare) binary data to/from tcp server. Binary data to send are read from "input file". Recevied data can be compared with data erad from "output file". File names are arguments of tcp_plugin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1161156&group_id=29880 From kvaes at vangenechten.com Thu Mar 10 23:28:44 2005 From: kvaes at vangenechten.com (Karim Vaes) Date: Thu Mar 10 23:28:44 2005 Subject: [Nagiosplug-devel] Re: Nagiosplug-devel digest, Vol 1 #870 - 4 msgs (Ouf of Office (Auto Reply)) Message-ID: Dear Sir/Madam, I'm currently out of the office, I'll be back on the 15th of March. For urgent matters, don't hesitate to contact my colleagues (helpdesk at vangenechten.com or +32(0)14/403720). Kind regards Karim Vaes IMAS NV (part of the Vangenechten Group) Raadsherenstraat 2 - BE-2300 TURNHOUT Tel: +32(0)14 403730 fax: +32(0)14 403715 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: From noreply at sourceforge.net Fri Mar 11 02:05:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 11 02:05:14 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1145413 ] This patche allow to use unix sockets in nagios plugins. Message-ID: Patches item #1145413, was opened at 2005-02-21 15:20 Message generated for change (Comment added) made by samm2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1145413&group_id=29880 Category: Enhancement Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alex Samorukov (samm2) Assigned to: Nobody/Anonymous (nobody) Summary: This patche allow to use unix sockets in nagios plugins. Initial Comment: With this patch user can specify unix socket as -H argument. This allow to check tcp services which are bind to unix sockets only. I use this for checking clamav-clamd. Alsi, i added check_clamd prototype to check status of the CLAMAV daemon (clamav.net). ---------------------------------------------------------------------- >Comment By: Alex Samorukov (samm2) Date: 2005-03-11 12:04 Message: Logged In: YES user_id=891004 Hi. Will nagios-plugins use this code? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1145413&group_id=29880 From noreply at sourceforge.net Fri Mar 11 02:30:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 11 02:30:02 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159828 ] CRITICAL check_ping on FC3 Message-ID: Bugs item #1159828, was opened at 2005-03-09 14:57 Message generated for change (Comment added) made by dro0p You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 9 Submitted By: PiTsA (pitsa) Assigned to: Nobody/Anonymous (nobody) Summary: CRITICAL check_ping on FC3 Initial Comment: The ping verification its not working... [root at infoandre libexec]# ./check_ping -H 192.168.1.4 -w 100.0,0,20% -c 500.0,0,60% /bin/ping -n -U -w 10 -c 5 192.168.1.4 CRITICAL - Could not interpret output from ping command [root at infoandre libexec]# /bin/ping -n -U -w 10 -c 5 192.168.1.4 PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. 64 bytes from 192.168.1.4: icmp_seq=0 ttl=128 time=0.249 ms 64 bytes from 192.168.1.4: icmp_seq=1 ttl=128 time=0.255 ms 64 bytes from 192.168.1.4: icmp_seq=2 ttl=128 time=0.198 ms 64 bytes from 192.168.1.4: icmp_seq=3 ttl=128 time=0.738 ms 64 bytes from 192.168.1.4: icmp_seq=4 ttl=128 time=0.187 ms --- 192.168.1.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.187/0.325/0.738/0.208 ms, pipe 2 [root at infoandre libexec]# ---------------------------------------------------------------------- Comment By: Bastien (dro0p) Date: 2005-03-11 11:29 Message: Logged In: YES user_id=1237097 Hi, Same problem here on a redhat 7.3. For me this problem is due to the local used. In fact my local (french) used , as float separator instead of . (us or english local). So the scanf function is unable to read float from the command ping (wich sort float using .). I made a small patch (it has a bad quality but it works). I post it here : ----- --- check_ping.c Fri Mar 11 10:13:08 2005 +++ check_ping.c Fri Mar 11 10:09:50 2005 @@ -401,6 +401,7 @@ { char buf[MAX_INPUT_BUFFER]; int result = STATE_UNKNOWN; + int i; if ((child_process = spopen (cmd)) == NULL) die (STATE_UNKNOWN, _("Could not open pipe: %s\n"), cmd); @@ -421,9 +422,19 @@ sscanf(buf,"%*d packets transmitted, %*d received, %d%% packet loss, time", &pl)==1 || sscanf(buf,"%*d packets transmitted, %*d received, +%*d errors, %d%% packet loss", &pl) == 1) continue; - /* get the round trip average */ else + { + if ((buf[0] == 'r') && (buf[1] == 't') && (buf[2] == 't')) + { + //fix for locales who uses , as float delimiter + for (i = 3 ; buf[i] != 0 ; i++) + { + if (buf[i] == '.') + buf[i] = ','; + } + } + if(sscanf(buf,"round-trip min/avg/max = %*f/%f/%*f",&rta)==1 || sscanf(buf,"round-trip min/avg/max/mdev = %*f/%f/%*f/%*f",&rta)==1 || sscanf(buf,"round-trip min/avg/max/sdev = %*f/%f/%*f/%*f",&rta)==1 || @@ -432,7 +443,8 @@ sscanf(buf,"round-trip (ms) min/avg/max = %*f/%f/%*f",&rta)==1 || sscanf(buf,"round-trip (ms) min/avg/max/stddev = %*f/%f/%*f/%*f",&rta)==1 || sscanf(buf,"rtt min/avg/max/mdev = %*f/%f/%*f/%*f ms",&rta)==1) - continue; + continue; + } } /* this is needed because there is no rta if all packets are lost */ ---- ---------------------------------------------------------------------- Comment By: PiTsA (pitsa) Date: 2005-03-09 15:00 Message: Logged In: YES user_id=1235741 nagios-plugins Version 1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 From noreply at sourceforge.net Mon Mar 14 19:09:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 14 19:09:35 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1163442 ] Email Delay Check Message-ID: New Plugins item #1163442, was opened at 2005-03-15 14:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1163442&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ryan Williams (ryanwilliams) Assigned to: Nobody/Anonymous (nobody) Summary: Email Delay Check Initial Comment: Connects to specified SMTP server and sends an email, waits for specified length of time then connects to a POP3 server to retreive the same email. Alerts if the email is not waiting in the pop3 account after the specified time. Similar to an IPSentry Mail-Loop ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1163442&group_id=29880 From noreply at sourceforge.net Mon Mar 14 22:02:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 14 22:02:39 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159624 ] Compile and Link Error on Solaris 2.6 Message-ID: Bugs item #1159624, was opened at 2005-03-09 07:06 Message generated for change (Comment added) made by df7be You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 Category: None Group: None >Status: Open Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) Assigned to: Ton Voon (tonvoon) Summary: Compile and Link Error on Solaris 2.6 Initial Comment: With Sun WorkShop Compiler C++ 4.2: My Workaround get the Plugins Running: - The old kompiler does not understand the C++- Comment // in C files. Take /* ... */ e.g. const char *program_name = "check_disk"; /* Required for coreutils libs */ The list of found C++ comments in 1.4 check_disk.c : Line 22 check_smtp.c lines 185,257,258,613 check_ups.c line 411 - unresolved symbols (also Solaris 8 with Forte 6 Update 2 !!) (e.g. gethostbyname) in Makefile the correct List of LIBS: LIBS = -lgen -lsocket -lnsl 73 de DF7BE ---------------------------------------------------------------------- >Comment By: Wilfried Brunken (df7be) Date: 2005-03-15 06:01 Message: Logged In: YES user_id=69405 Trying to open for test: nagios-plugins-HEAD-200503121747.tar.gz get: gunzip: nagios-plugins-HEAD-200503121747.tar.gz: unexpected end of file also with WINZIP ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2005-03-09 21:05 Message: Logged In: YES user_id=664364 Wilfried, Thanks for the bug report. This has been fixed in CVS HEAD. Please try the snapshot to confirm. http://nagiosplug.sf.net/snapshot Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159624&group_id=29880 From noreply at sourceforge.net Tue Mar 15 02:55:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 15 02:55:04 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1163624 ] check_spamc Message-ID: New Plugins item #1163624, was opened at 2005-03-15 10:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1163624&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Folkert van Heusden (fvh) Assigned to: Nobody/Anonymous (nobody) Summary: check_spamc Initial Comment: This little script can be used as a plugin for Nagios to check if the SpamAssassin 'spamd' process is still running and accepting connections and in general working as expected. http://www.vanheusden.com/Linux/#spamc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1163624&group_id=29880 From noreply at sourceforge.net Wed Mar 16 01:47:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 16 01:47:02 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1164325 ] Warning threshold must be float or float triplet!" at check_ Message-ID: Bugs item #1164325, was opened at 2005-03-16 09:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164325&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) Assigned to: Nobody/Anonymous (nobody) Summary: Warning threshold must be float or float triplet!" at check_ Initial Comment: No output generated, because of this Can the configure Script automatically find the problem ? (or documentation "INSTALL.UNIX" adding ?) The Workaround to fix the Problem was: - add the Line "setlocale(LC_NUMERIC, "POSIX");" in plugins/check_load.c - ./configure --disable-nls - Short Test: cd plugins ./check_load -w 1,1,1 -c 2,2,2 Needed "--disable-nls" at following OS: RedHat AS 3 ( gcc-3.2.3-49 ) SuSe-LINUX 9.x ( gcc-3.3.4-11 on 9.2 ) NOT SuSe 8.2 !! AIX 5.1 (not 4.3) ! ( C for AIX Compiler, Version 6 ) I found the Information visiting the following site: http://article.gmane.org/gmane.network.nagios.plugins.d evel/2473 1. Recompile the plugins using: ./configure --disable-nls I have not tested this, but I believe this should work. After the 'textdomain' call at the start of the plugin source code, add the line: setlocale(LC_NUMERIC, "POSIX"); Eg, with your problem plugin check_load. Edit plugins/check_load.c: -------------------check_load.c------------------- int main (int argc, char **argv) { int result = STATE_UNKNOWN; #if HAVE_GETLOADAVG==1 double la[3] = { 0.0, 0.0, 0.0 }; /* NetBSD complains about unitialized arrays */ #else # if HAVE_PROC_LOADAVG==1 FILE *fp; char input_buffer[MAX_INPUT_BUFFER]; char *tmp_ptr; # else char input_buffer[MAX_INPUT_BUFFER]; # endif #endif float la1, la5, la15; setlocale (LC_ALL, ""); bindtextdomain (PACKAGE, LOCALEDIR); textdomain (PACKAGE); setlocale(LC_NUMERIC, "POSIX"); <--- HERE!! -------------------check_load.c------------------- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164325&group_id=29880 From noreply at sourceforge.net Wed Mar 16 01:54:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 16 01:54:35 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1164331 ] IBM-AIX 5.1 :Link-Error "Undefined symbol: .libintl_gettext" Message-ID: Bugs item #1164331, was opened at 2005-03-16 09:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164331&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) Assigned to: Nobody/Anonymous (nobody) Summary: IBM-AIX 5.1 :Link-Error "Undefined symbol: .libintl_gettext" Initial Comment: not on AIX 4.3 ! Can configure find the Problem itself ? Workaround ./configure --disable-nls --with-included-gettext Solution found at this link: http://mail.gnome.org/archives/mc-devel/2002- September/msg00193.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164331&group_id=29880 From noreply at sourceforge.net Wed Mar 16 01:58:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 16 01:58:21 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1164335 ] Link-Error AIX 4.3 at libc.a(shr.o) Message-ID: Bugs item #1164335, was opened at 2005-03-16 09:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164335&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wilfried Brunken (df7be) Assigned to: Nobody/Anonymous (nobody) Summary: Link-Error AIX 4.3 at libc.a(shr.o) Initial Comment: The Message: Could not load program ./a.out: Dependent module libc.a(shr.o) could not be loaded. Can't the configure script recognize the problem ? Workaround: ./configure CFLAGS=-L=/usr/lib (should bei good also for AIX 5.1, but there not necessary) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1164335&group_id=29880 From noreply at sourceforge.net Thu Mar 17 06:53:25 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 17 06:53:25 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1165298 ] check_oracle.sh including TEMP tablespace Message-ID: Patches item #1165298, was opened at 2005-03-17 15:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1165298&group_id=29880 Category: Enhancement Group: None Status: Open Resolution: None Priority: 5 Submitted By: haiku76 (haiku76) Assigned to: Nobody/Anonymous (nobody) Summary: check_oracle.sh including TEMP tablespace Initial Comment: The standard tablespace check returned 0% used for the TEMP tablespace. Information about the bytes free of the tablespace are not found in dba_free_space but in another view. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1165298&group_id=29880 From noreply at sourceforge.net Thu Mar 17 08:13:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 17 08:13:20 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1165365 ] check_lsiraid LSI Logic RAID adaptor Message-ID: New Plugins item #1165365, was opened at 2005-03-17 11:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1165365&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rob Francis (slurb) Assigned to: Nobody/Anonymous (nobody) Summary: check_lsiraid LSI Logic RAID adaptor Initial Comment: Checks for the status of a RAID set on an LSI adaptor as commonly shipped on Dell servers. Returns OK only if the status of the set is OPTIMAL, else returns CRITICAL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1165365&group_id=29880 From nagios at proy.org Thu Mar 17 09:03:01 2005 From: nagios at proy.org (Patrick Proy) Date: Thu Mar 17 09:03:01 2005 Subject: [Nagiosplug-devel] Plugins help for nagios frontends In-Reply-To: <20050304025954.14145.qmail@web61301.mail.yahoo.com> Message-ID: <20050317170118.77881AC072@www.manubulon.com> Hi, There are quite a lot of nagios frontends making Nagios really easy to configure for end-users (like creating a service or a host), but the plugins have a lot of different arguments, so creating a front end is quite impossible. I think it would be a good idea if each plugin could be run with a "--frontend" option giving something like : ;;;;[;;;] ....... Ex : H;Host;String;$HOSTNAME$;"Hostname or IP address" w;warning;;"Warning value in % of disk usage";"%";0;100 Then the guy coding the frontends would be able to do something really cool with commands definition. AND, it wouldn't be a huge work (I would have to update my 7 plugins...). Patrick Proy Nagios AT proy.org From srunschke at abit.de Tue Mar 22 02:41:21 2005 From: srunschke at abit.de (Sascha Runschke) Date: Tue Mar 22 02:41:21 2005 Subject: [Nagiosplug-devel] Problem: check_icmp incorrectly reporting packet loss? Message-ID: Greetings, I have been using Nagios together with check_icmp for quite some time now and it mostly went very smooth. Just lately I made a few changes and now it seems that check_icmp is causing quite some problems. Since I am running quite a highly parallelized Nagios environment, I ordered a new server to get rid of the load spikes, I switched from an older Nagios 2 beta to 2.0b2 and updated my old nagiosplug cvs snapshot to 1.4. The old server was running RH9, the new one is running RH Enterprise Server 4. SELinux is disabled, since I couldn't get it to work with the Nagios.cmd file being accessed by the http- and usr-content. After a few days of smooth work, check_icmp seems to start choking, reporting paket loss and high latency where there is none actually. Following scenario: HP Compaq DL 380 G4 (Xeon 3.4Ghz) 3 GB Ram RedHat Enterprise Server 4 (SE disabled) Nagios 2.0b2 check_icmp 2005_03_15 (tried that after having problems with the one from nagiosplug 1.4) I'm running around 300 service checks per minute, quite some of them icmp related. Problem: After a few days check_icmp suddenly started to report high latency and 60-80% paket loss, but the strange thing is that it only reported it for 2 outgoing lines. (I am monitoring about 10 remote sites in addition to our HQ) So my first conclusion was problems with the internet connection for those sites. But to my surprise there were absolutely no problems. Neither the users there noticed _anything_, nor did my ping tests bring anything up. Even pinging from the Nagios machine worked absolutely fine - but using check_icmp to ping brought up the same strange behaviour - high latency (500-1000ms) and high paket loss (60-80%) with half of the checks made - the others were fine. Using /bin/ping at the same time brings up: [root at nagios check_icmp-2005-03-15]# ping 62.159.233.94 PING 62.159.233.94 (62.159.233.94) 56(84) bytes of data. ... ... --- 62.159.233.94 ping statistics --- 21 packets transmitted, 21 received, 0% packet loss, time 20027ms rtt min/avg/max/mdev = 37.718/109.663/307.297/98.933 ms, pipe 2 The quite high rtt is normal, since that site has a continuous bandwidth usage, but it seldom spikes - and it doesn't spike to 800ms with 80% loss for 44 hours in a row like check_icmp reported. A -v -v -v log output from check_icmp at the same time when the ping was done is attached. I'll see if I get to dig into check_icmp.c myself, but I am not too sure it's gonna happen since I'm loaded with work :/ Any ideas or hints to the problem? sash -------------------------------------------------- Sascha Runschke Netzwerk Administration IT-Services ABIT AG Robert-Bosch-Str. 1 40668 Meerbusch Tel.:+49 (0) 2150.9153.226 Mobil:+49 (0) 173.5419665 mailto:SRunschke at abit.de http://www.abit.net http://www.abit-epos.net http://www.my-academy.net -------------------------------------------------- Der Inhalt dieser Email sowie die Anh?nge sind ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Email oder dessen Vertreter sein sollten, so beachten Sie bitte, da? jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser Email unzul?ssig ist. Wir m?chten Sie au?erdem darauf hinweisen, da? die Kommunikation per Email ?ber das Internet unsicher ist, da fuer unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht. Wenn Sie diese Nachricht versehentlich erhalten, informieren Sie bitte den Absender und l?schen diese Nachricht mit den Anh?ngen. Herzlichen Dank The information and any attachments contained in this email are intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. We also like to inform you that communication via email over the internet is insecure because third parties may have the possibility to access and manipulate emails. If you have received the message in error, please advise the sender and delete the message and any attachments. Thank you very much. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: check_icmp_logoutput.txt URL: From larry.dawson at vanderbilt.edu Thu Mar 24 06:14:08 2005 From: larry.dawson at vanderbilt.edu (Laurence P Dawson) Date: Thu Mar 24 06:14:08 2005 Subject: [Nagiosplug-devel] Fix for minor defect in check_load plugin In-Reply-To: <20050324135159.92D3D136B1@sc8-sf-spam2.sourceforge.net> References: <20050324135159.92D3D136B1@sc8-sf-spam2.sourceforge.net> Message-ID: <1111673451.10856.33.camel@a132041.n1.vanderbilt.edu> There is a minor problem in the check_load.c plugin. It checks for is_intnonneg for the values of parameters that are supposed to be floats. There is a definite advantage for us in allowing float values, as using a value like 1.9 instead of 2 reduces notifications due to 'flapping'. Patch against cvs: diff -c check_load.c.orig check_load.c *** check_load.c.orig 2005-03-24 08:02:06.643753343 -0600 --- check_load.c 2005-03-23 15:44:01.000000000 -0600 *************** *** 186,192 **** switch (c) { case 'w': /* warning time threshold */ ! if (is_intnonneg (optarg)) { wload1 = atof (optarg); wload5 = atof (optarg); wload15 = atof (optarg); --- 186,192 ---- switch (c) { case 'w': /* warning time threshold */ ! if (is_numeric (optarg)) { wload1 = atof (optarg); wload5 = atof (optarg); wload15 = atof (optarg); *************** *** 202,208 **** usage (_("Warning threshold must be float or float triplet!\n")); break; case 'c': /* critical time threshold */ ! if (is_intnonneg (optarg)) { cload1 = atof (optarg); cload5 = atof (optarg); cload15 = atof (optarg); --- 202,208 ---- usage (_("Warning threshold must be float or float triplet!\n")); break; case 'c': /* critical time threshold */ ! if (is_numeric (optarg)) { cload1 = atof (optarg); cload5 = atof (optarg); cload15 = atof (optarg); From noreply at sourceforge.net Mon Mar 28 17:11:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 17:11:35 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1172222 ] check_queuepostfix Message-ID: New Plugins item #1172222, was opened at 2005-03-29 03:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1172222&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: OSG (osgfreefr) Assigned to: Nobody/Anonymous (nobody) Summary: check_queuepostfix Initial Comment: This little script, give the number of mail in the queue of postfix ussing the postqueue -p command. In the same time give how big is the queue in size. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1172222&group_id=29880 From noreply at sourceforge.net Mon Mar 28 17:17:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 28 17:17:26 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1172231 ] Check_compdate Message-ID: New Plugins item #1172231, was opened at 2005-03-29 03:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1172231&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: OSG (osgfreefr) Assigned to: Nobody/Anonymous (nobody) Summary: Check_compdate Initial Comment: Check if computer are synchronised about time. The nagios machine is the reference. It's compose by two scripts: .fisrt check_date must be installed on all machine by nrpe: #!/bin/sh # Vincent Tamet 20050327 etat="OK" date="Probleme lors du lancement de la commande Date." prog=`basename $0` date=`date +%s` if [ $? -eq "0" ] then etat="OK" echo "$prog $etat - $date." exit 0 else etat="UNKNOWN" echo "$prog $etat - $date." exit 2 fi .Second check_compdate must be installed on nagios computer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1172231&group_id=29880 From Stanley.Hopcroft at IPAustralia.gov.au Mon Mar 28 23:15:09 2005 From: Stanley.Hopcroft at IPAustralia.gov.au (Stanley Hopcroft) Date: Mon Mar 28 23:15:09 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 In-Reply-To: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> References: <4BCF0BC0-8CF0-11D9-B22A-000A95D47298@mac.com> Message-ID: <20050329065711.GG75855@ws11114.aipo.gov.au> Dear Folks, The only comment I have about 1.5 is suggesting the separation of the suid C plugins from the non-suid plugins. I think this is necessary because apart from the weaknesses in the implementations of the the suid plugins (check_dhcp, check_smart_*), testing becomes much more difficult on non core platforms. I do not have root access on HPUX - any version Solaris - " OS-X - " AIX - " and I cannot imagine getting such access to any but a subset (at best AIX and Solaris). These plugins then are unlikely to have the same degree of testing that the others have and therefore are unlikely to perform as well. Putting them in their own optional build directory (say /suid) with a README like that for /contrib may be beneficial in 1 stopping build failures caused by these plugins 2 lowering expectations about the performance of these plugins. Yours sincerely. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: disclaimer.txt URL: From Ton.Voon at egg.com Tue Mar 29 00:41:24 2005 From: Ton.Voon at egg.com (Voon, Ton) Date: Tue Mar 29 00:41:24 2005 Subject: [Nagiosplug-devel] Kickoff for 1.5 Message-ID: Sorry guys, haven't been staying on top of these emails. I think it is a great idea to separate the suid plugins, if only because they have to be installed differently (as root, rather than as a nagios or own user). I don't think their support *should* be any different - after all that was part of the discussion we had prior to the 1.4 release and I think we took it on that this was now part of our core. However, by having a separate directory, it is clear they are "different". So I'd advocate keeping them in by default. Stanley, do you want to move the suid stuff into a separate directory? (suid/? plugins-suid/? plugins-root/?) Will need to make some changes to the makefile.am at the top level. As to the other things that were discussed for 1.5, will need to start summarising and seeing who wants to pick up which tasks. I can track allocation via email, unless SF has some better tools for doing it. Ton -----Original Message----- From: nagiosplug-devel-admin at lists.sourceforge.net [mailto:nagiosplug-devel-admin at lists.sourceforge.net] On Behalf Of Stanley Hopcroft Sent: 29 March 2005 07:57 To: NagiosPlug Devel Subject: Re: [Nagiosplug-devel] Kickoff for 1.5 Dear Folks, The only comment I have about 1.5 is suggesting the separation of the suid C plugins from the non-suid plugins. I think this is necessary because apart from the weaknesses in the implementations of the the suid plugins (check_dhcp, check_smart_*), testing becomes much more difficult on non core platforms. I do not have root access on HPUX - any version Solaris - " OS-X - " AIX - " and I cannot imagine getting such access to any but a subset (at best AIX and Solaris). These plugins then are unlikely to have the same degree of testing that the others have and therefore are unlikely to perform as well. Putting them in their own optional build directory (say /suid) with a README like that for /contrib may be beneficial in 1 stopping build failures caused by these plugins 2 lowering expectations about the performance of these plugins. Yours sincerely. ----------------------------------------- Egg is a trading name of the Egg group of companies which includes: Egg plc (reg no 2448340), Egg Financial Products ltd (reg no 3319027), Egg International ltd (reg no 4059266), Egg Financial Intermediation ltd (reg no 382828), Egg Investments ltd (reg no 3403963) and Egg Banking plc (reg no 2999842. Egg Investments Ltd, Egg Banking plc and Egg Financial Intermediation Ltd are authorised and regulated by the Financial Services Authority (FSA) and are entered in the FSA register under numbers 190518, 205621 and 309551 respectively. These members of the Egg group are registered in England and Wales. Registered offices: 1 Waterhouse Square, 138-142 Holborn, London EC1N 2NA. This e-mail is confidential and for use by the addressee only. If you are not the intended recipient of this e-mail and have received it in error, please return the message to the sender by replying to it and then delete it from your mailbox. Internet e-mails are not necessarily secure. The Egg group of companies do not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by the Egg group of companies in this regard and the recipient should carry out such virus and other checks as it considers appropriate. This communication does not create or modify any contract. From noreply at sourceforge.net Tue Mar 29 06:02:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 29 06:02:18 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1172539 ] check_ntp perfdata and fixes Message-ID: Patches item #1172539, was opened at 2005-03-29 16:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1172539&group_id=29880 Category: Perf data Group: None Status: Open Resolution: None Priority: 5 Submitted By: Yann Dirson (ydirson) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp perfdata and fixes Initial Comment: This patch adds offset and jitter using usual perfdata syntax. As I had to remove \n's put in wrong places, I cleaned up a couple of trailing spaces as well. You'll also find I had to fix the regexp for ntpq, as was reported in several patches. I also added a check for the case the regexp does not match, to make it visible in the plugin output. You may also like the typo fix in one verbose message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1172539&group_id=29880 From mc2guy at hotmail.com Tue Mar 29 13:22:33 2005 From: mc2guy at hotmail.com (mc2 guy) Date: Tue Mar 29 13:22:33 2005 Subject: [Nagiosplug-devel] McAfee plugins for Nagios? Message-ID: Is there a McAfee GroupShield For Exchange plugins for Nagios? _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee? Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 From noreply at sourceforge.net Wed Mar 30 05:01:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 30 05:01:39 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1173263 ] check_sybase v0.6 Message-ID: Patches item #1173263, was opened at 2005-03-30 15:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1173263&group_id=29880 Category: Bugfix Group: None Status: Open Resolution: None Priority: 5 Submitted By: Simon Bellwood (sb-netman) Assigned to: Nobody/Anonymous (nobody) Summary: check_sybase v0.6 Initial Comment: A minor release to check_sybase that adds an --explain option to describe how free space is calculated. The download is available from: http://www.net-man.at/software/check_sybase-0.6.zip The latest version is always available from: http://www.net-man.at/software/check_sybase-LATEST.zip Will patch against 0.5 if needed. Simon Bellwood NetMan Network Management and IT Services GmbH ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1173263&group_id=29880 From noreply at sourceforge.net Wed Mar 30 05:08:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 30 05:08:50 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1173266 ] check_ntp matching expression and ntpq output Message-ID: Bugs item #1173266, was opened at 2005-03-30 07:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1173266&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rusty Allen (wackoadmin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp matching expression and ntpq output Initial Comment: The perl expression being used to parse the output of ntpq in check_ntp does not account for some possible output lines create by ntpq. remote refid st t when poll reach delay offset jitter ============================================================================== -163.185.18.1 192.5.41.40 2 u 116m 18h 377 2.133 16.566 2.467 *192.5.41.41 .USNO. 1 u 16h 18h 376 92.765 13.857 19.226 +204.34.198.40 .USNO. 1 u 10h 18h 376 66.439 -12.246 1.836 127.127.1.0 LOCAL(0) 10 l 54 64 377 0.000 0.000 0.008 +130.88.200.98 194.81.227.227 2 u 6h 18h 377 122.584 0.349 4.552 -128.118.25.3 128.118.25.5 2 u 118m 18h 377 63.745 -44.445 89.870 Note the "hours" tag in the "when" and "poll" values. I have change the expressionis to: if (/^(\*|o)([-0-9.\s]+)\s+([-0-9A-Za-z.]+)\s+([-0-9.]+)\s+([lumb-]+)\s+([-0-9hm.]+)\s+([-0-9.mh]+)\s+([-0-9.]+)\s+([-0-9.]+)\s+([-0-9.]+)\s+([-0-9.]+)/) { $c =~ /^(#)([-0-9.\s]+)\s+([-0-9A-Za-z.]+)\s+([-0-9.]+)\s+([lumb-]+)\s+([-0-9hm.]+)\s+([-0-9.mh]+)\s+([-0-9.]+)\s+([-0-9.]+)\s+([-0-9.]+)\s+([-0-9.]+)/; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1173266&group_id=29880 From noreply at sourceforge.net Thu Mar 31 05:08:45 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 31 05:08:45 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1174070 ] check_smtp TLS mistake with echange 2003 Message-ID: Bugs item #1174070, was opened at 2005-03-31 13:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1174070&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: jeff_fr (jeff_fr) Assigned to: Nobody/Anonymous (nobody) Summary: check_smtp TLS mistake with echange 2003 Initial Comment: Exchange 2003 is waitng EHLO or HELO before the STARTTLS instruction, this make the plugin unable to get the OK state from echange 2003 when using TLS . the solution is to add : send(sd, helocmd, strlen(helocmd), 0); recv(sd,buffer, MAX_INPUT_BUFFER-1, 0); between the line (approx 181) : if(use_ssl){ and line: send(sd, SMTP_STARTTLS, strelen(SMTP_STARTTLS), 0); It's not very clean but it's a fast modification to get the real result, in fact i checked that postfix was able to get the HELO before or after STARTTLS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1174070&group_id=29880 From noreply at sourceforge.net Thu Mar 31 05:17:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 31 05:17:40 2005 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1159828 ] CRITICAL check_ping on FC3 Message-ID: Bugs item #1159828, was opened at 2005-03-09 13:57 Message generated for change (Comment added) made by jeff_fr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 Category: None Group: None Status: Open Resolution: None Priority: 9 Submitted By: PiTsA (pitsa) Assigned to: Nobody/Anonymous (nobody) Summary: CRITICAL check_ping on FC3 Initial Comment: The ping verification its not working... [root at infoandre libexec]# ./check_ping -H 192.168.1.4 -w 100.0,0,20% -c 500.0,0,60% /bin/ping -n -U -w 10 -c 5 192.168.1.4 CRITICAL - Could not interpret output from ping command [root at infoandre libexec]# /bin/ping -n -U -w 10 -c 5 192.168.1.4 PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data. 64 bytes from 192.168.1.4: icmp_seq=0 ttl=128 time=0.249 ms 64 bytes from 192.168.1.4: icmp_seq=1 ttl=128 time=0.255 ms 64 bytes from 192.168.1.4: icmp_seq=2 ttl=128 time=0.198 ms 64 bytes from 192.168.1.4: icmp_seq=3 ttl=128 time=0.738 ms 64 bytes from 192.168.1.4: icmp_seq=4 ttl=128 time=0.187 ms --- 192.168.1.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.187/0.325/0.738/0.208 ms, pipe 2 [root at infoandre libexec]# ---------------------------------------------------------------------- Comment By: jeff_fr (jeff_fr) Date: 2005-03-31 13:14 Message: Logged In: YES user_id=1250267 you must modifiy chech_ping line 74 and add : setlocale (LC_ALL, "C"); instead of : setlocale (LC_ALL, ""); recompile ... in nagios it will be state ok in console mode you will get something like : PING CRITICAL - PAcket loss= 0%, TA= 1 ms ---------------------------------------------------------------------- Comment By: Bastien (dro0p) Date: 2005-03-11 10:29 Message: Logged In: YES user_id=1237097 Hi, Same problem here on a redhat 7.3. For me this problem is due to the local used. In fact my local (french) used , as float separator instead of . (us or english local). So the scanf function is unable to read float from the command ping (wich sort float using .). I made a small patch (it has a bad quality but it works). I post it here : ----- --- check_ping.c Fri Mar 11 10:13:08 2005 +++ check_ping.c Fri Mar 11 10:09:50 2005 @@ -401,6 +401,7 @@ { char buf[MAX_INPUT_BUFFER]; int result = STATE_UNKNOWN; + int i; if ((child_process = spopen (cmd)) == NULL) die (STATE_UNKNOWN, _("Could not open pipe: %s\n"), cmd); @@ -421,9 +422,19 @@ sscanf(buf,"%*d packets transmitted, %*d received, %d%% packet loss, time", &pl)==1 || sscanf(buf,"%*d packets transmitted, %*d received, +%*d errors, %d%% packet loss", &pl) == 1) continue; - /* get the round trip average */ else + { + if ((buf[0] == 'r') && (buf[1] == 't') && (buf[2] == 't')) + { + //fix for locales who uses , as float delimiter + for (i = 3 ; buf[i] != 0 ; i++) + { + if (buf[i] == '.') + buf[i] = ','; + } + } + if(sscanf(buf,"round-trip min/avg/max = %*f/%f/%*f",&rta)==1 || sscanf(buf,"round-trip min/avg/max/mdev = %*f/%f/%*f/%*f",&rta)==1 || sscanf(buf,"round-trip min/avg/max/sdev = %*f/%f/%*f/%*f",&rta)==1 || @@ -432,7 +443,8 @@ sscanf(buf,"round-trip (ms) min/avg/max = %*f/%f/%*f",&rta)==1 || sscanf(buf,"round-trip (ms) min/avg/max/stddev = %*f/%f/%*f/%*f",&rta)==1 || sscanf(buf,"rtt min/avg/max/mdev = %*f/%f/%*f/%*f ms",&rta)==1) - continue; + continue; + } } /* this is needed because there is no rta if all packets are lost */ ---- ---------------------------------------------------------------------- Comment By: PiTsA (pitsa) Date: 2005-03-09 14:00 Message: Logged In: YES user_id=1235741 nagios-plugins Version 1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1159828&group_id=29880 From noreply at sourceforge.net Thu Mar 31 05:33:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 31 05:33:14 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1119927 ] check_smtp_tls Message-ID: New Plugins item #1119927, was opened at 2005-02-10 10:10 Message generated for change (Comment added) made by jeff_fr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1119927&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: noliono (noliono) Assigned to: Nobody/Anonymous (nobody) Summary: check_smtp_tls Initial Comment: needed : lib net:telnet has to be install. a telnet command is send on the SMTP server, then a "STARTTLS" command and if TLS is present they will have a response code 250 ... and so on a nagios state (warning,critical,ok,unknow) ---------------------------------------------------------------------- Comment By: jeff_fr (jeff_fr) Date: 2005-03-31 13:31 Message: Logged In: YES user_id=1250267 Exchange is waiting for HELO or EHLO before the STARTTLS, in this case the script will return an ALERT instead of OK ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1119927&group_id=29880 From noreply at sourceforge.net Thu Mar 31 05:35:12 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 31 05:35:12 2005 Subject: [Nagiosplug-devel] [ nagiosplug-New Plugins-1119927 ] check_smtp_tls Message-ID: New Plugins item #1119927, was opened at 2005-02-10 10:10 Message generated for change (Comment added) made by jeff_fr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1119927&group_id=29880 Category: Perl plugin Group: None Status: Open Resolution: None Priority: 5 Submitted By: noliono (noliono) Assigned to: Nobody/Anonymous (nobody) Summary: check_smtp_tls Initial Comment: needed : lib net:telnet has to be install. a telnet command is send on the SMTP server, then a "STARTTLS" command and if TLS is present they will have a response code 250 ... and so on a nagios state (warning,critical,ok,unknow) ---------------------------------------------------------------------- Comment By: jeff_fr (jeff_fr) Date: 2005-03-31 13:32 Message: Logged In: YES user_id=1250267 Exchange is waiting for HELO or EHLO before the STARTTLS, in this case the script will return an ALERT instead of OK ---------------------------------------------------------------------- Comment By: jeff_fr (jeff_fr) Date: 2005-03-31 13:31 Message: Logged In: YES user_id=1250267 Exchange is waiting for HELO or EHLO before the STARTTLS, in this case the script will return an ALERT instead of OK ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=541465&aid=1119927&group_id=29880