From notifications at github.com Sun Jan 3 10:21:20 2016 From: notifications at github.com (Igor Pashev) Date: Sun, 03 Jan 2016 01:21:20 -0800 Subject: Added check_mysql_slave (#1399) Message-ID: Supports MariaDB multi-source replication. It's a stripped version of `check_mysql` that checks slave status only. You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1399 -- Commit Summary -- * Added check_mysql_slave -- File Changes -- M configure.ac (2) M plugins/Makefile.am (5) A plugins/check_mysql_slave.c (509) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1399.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1399.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1399 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gereon.kremer at cs.rwth-aachen.de Mon Jan 4 15:03:53 2016 From: gereon.kremer at cs.rwth-aachen.de (Gereon Kremer) Date: Mon, 4 Jan 2016 15:03:53 +0100 Subject: Using check_http for https Message-ID: <568A7BC9.9080300@cs.rwth-aachen.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, I'm using nagios for website monitoring and recently one of the sites was migrated to https. I'll abstract from the nagios config now and directly show the problem on the plugin. I now want to migrate the following command to https: check_http -H What works: wget https:// What does not work (with result): check_http -S -H (timeout) check_http --ssl -H (timeout) check_http --ssl=1 -H (timeout) check_http --ssl=2 -H (SSL protocol version 2 is not supported by your SSL library.) check_http --ssl=3 -H (sslv3 alert handshake failure:s3_pkt.c:1294:SSL alert number 40) check_http -p 443 -H (timeout) I also tried to enable sni or additionally provide the IP via -I, but this did not change anything. I discovered the third-party check_https plugin which actually wraps wget. However, I'd like to use the -s option from check_http which is not provided by check_https. The version: $ check_http --version check_http v2.1.1 (monitoring-plugins 2.1.1) The tests were executed on a debian server as root (I know that I should not run nagios as root, but for testing this issue it seemed appropriate .) Best, Gereon - -- Gereon Kremer Lehr- und Forschungsgebiet Theorie Hybrider Systeme RWTH Aachen Tel: +49 241 80 21243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWinvHAAoJEIQ2nMX673Hf9g8IAI9XHrcsvADAqngEeXkYEeJO a+K8P3CK23Ft/V6num7Mg0DO0uMdPoGFKamaaVSR4Biq29INyYmx9wgMCgkQ5b3o c7O/CZbSG9GlZ327WUJQWo05DR4z7ctRJD83IhAIBw/IOt3mb/nUih06Bb8xFUxi f2Om8gSsD0yX7zWhcC2f+J8K8XG9AmacDqJFcMdptlHmdWbVRvkcVrJG+pJn6qXv UdH2D7/fPELjy1MfUx6tanUEl2FbvrWXIVzxOAClihsiDuDGAdwkRJz/837WWKqw im8p7L+4QHyRZzFIREf8rXuLeq7bJvMNjFeJ/BlD8g+0uvBC/W+OdkswHNBFmTw= =mDIK -----END PGP SIGNATURE----- From dermoth at aei.ca Mon Jan 4 19:44:32 2016 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 4 Jan 2016 13:44:32 -0500 Subject: Using check_http for https In-Reply-To: <568A7BC9.9080300@cs.rwth-aachen.de> References: <568A7BC9.9080300@cs.rwth-aachen.de> Message-ID: <568ABD90.5020502@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/01/16 09:03 AM, Gereon Kremer wrote: > > Hello, > > I'm using nagios for website monitoring and recently one of the sites > was migrated to https. > I'll abstract from the nagios config now and directly show the problem > on the plugin. > > I now want to migrate the following command to https: > check_http -H > > What works: > wget https:// > > What does not work (with result): > check_http -S -H (timeout) > check_http --ssl -H (timeout) > check_http --ssl=1 -H (timeout) > check_http --ssl=2 -H (SSL protocol version 2 is not supported > by your SSL library.) > check_http --ssl=3 -H (sslv3 alert handshake > failure:s3_pkt.c:1294:SSL alert number 40) > check_http -p 443 -H (timeout) Hi Gereon, Have you tried: check_https -H check_http -S -p 443 -H If I'm not mistaken, calling check_http as check_https does two things: 1. enable ssl (-S/--ssl), and 2. change the default port to 443 (check_https should be a symlink to check_http). When you set the port to 443, it's like doing "http://host:443/" : that will use normal http on an ssl connection which won't work. Similarly, I don't think check_http is smart enough to decide when it should change the default port to 443 unless when called as "check_https", so when you use -S/--ssl without explicitly setting port 443, it's like doing "https://host:80/" - going ssh on a non-ssh connection won't work neither. Regards, - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlaKvX4ACgkQ6dZ+Kt5BchbeIwCgyH17A5sbRD+Bew4476PaG62d jZMAnA/SNVadYqN6UTWAvAyodlt7xl+J =jtlD -----END PGP SIGNATURE----- From dermoth at aei.ca Mon Jan 4 19:52:22 2016 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 4 Jan 2016 13:52:22 -0500 Subject: Using check_http for https In-Reply-To: <568A7BC9.9080300@cs.rwth-aachen.de> References: <568A7BC9.9080300@cs.rwth-aachen.de> Message-ID: <568ABF66.5030308@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/01/16 09:03 AM, Gereon Kremer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > Hello, > > I'm using nagios for website monitoring and recently one of the sites > was migrated to https. > I'll abstract from the nagios config now and directly show the problem > on the plugin. > > I now want to migrate the following command to https: > check_http -H > > What works: > wget https:// > > What does not work (with result): > check_http -S -H (timeout) > check_http --ssl -H (timeout) > check_http --ssl=1 -H (timeout) > check_http --ssl=2 -H (SSL protocol version 2 is not supported > by your SSL library.) > check_http --ssl=3 -H (sslv3 alert handshake > failure:s3_pkt.c:1294:SSL alert number 40) > check_http -p 443 -H (timeout) > > I also tried to enable sni or additionally provide the IP via -I, but > this did not change anything. > I discovered the third-party check_https plugin which actually wraps > wget. However, I'd like to use the -s option from check_http which is > not provided by check_https. Hi Gereon, Have you tried: check_https -H check_http -S -p 443 -H If I'm not mistaken, calling check_http as check_https does two things: 1. enable ssl (-S/--ssl), and 2. change the default port to 443 (check_https should be a symlink to check_http). When you set the port to 443, it's like doing "http://host:443/" : that will use normal http on an ssl connection which won't work. Similarly, I don't think check_http is smart enough to decide when it should change the default port to 443 unless when called as "check_https", so when you use -S/--ssl without explicitly setting port 443, it's like doing "https://host:80/" - going ssl on a non-ssl connection won't work neither. Regards, P.s.: Sorry for repost, so long I haven't posted in here my gpg rules had to be updated - also corrected some typos. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlaKv1wACgkQ6dZ+Kt5BchY6dwCguRTU5FDHriMhMTBeYhxDQpmA l9QAoIkQqSWwdXd2Yzc2kKJ0WVVX69Dd =f3mX -----END PGP SIGNATURE----- From infotek at gmail.com Tue Jan 5 20:44:53 2016 From: infotek at gmail.com (Jason Ellison) Date: Tue, 5 Jan 2016 13:44:53 -0600 Subject: check_dhcp plugin issue In-Reply-To: <562F8B2B.7080707@spbau.ru> References: <562F8B2B.7080707@spbau.ru> Message-ID: I have some spare time to dedicate to this issue. Could you provide a packet capture and details on the versions of software involved? Jason Ellison https://www.linkedin.com/in/infotek On Tue, Oct 27, 2015 at 9:33 AM, Evgeny Beysembaev wrote: > Hello! > Is check_dhcp nagios monitoring plugin still supported? > The problem is, my DHCP server (Debian Stable, isc-dhcp) ignores requests > from the plugin, and i have a suspicion that it malformes the requests. Is > it possible to submit the problem or maybe send a patch? > > Thank you. > Evgeny Beysembaev From quratulain3535 at gmail.com Thu Jan 28 19:43:54 2016 From: quratulain3535 at gmail.com (qurat ulain) Date: Thu, 28 Jan 2016 23:43:54 +0500 Subject: question: 'check_http' Message-ID: Hi, I am developing a cloud product and want to use nagios for the monitoring part. Can you plz help me knowing that, whether I can set threshold in check_http? for sending me notification after increase in requests per seconds from certain threshold? If yes then how? Thanks Regards, Qurat ul ain -------------- next part -------------- An HTML attachment was scrubbed... URL: