[Check_mk (english)] FW: HTTP Active Check check

I'm trying to setup OMD with Check _MK and every attempt I make to contact a known website, internal or external fails with a connection_refused, unable to open TCP socket message. I need to be able to complete HTTP checks similar to what I have already in Nagios with curl commands and find results. I also need to test the check via server command line. Can you explain what is going on? Thank you.

check_mk_active-http! -I $HOSTADDRESS$ -u 'www.google.com' -ssl
HTTP CRITICAL - Unable to open TCP socket

---------------------------------------- The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.

Hi Charles,

at first: knowing your used OMD and Check_MK version could help debugging.

Generally you can check what’s going on with active http checks by navigating to your terminal console, become OMD siteuser and execute this (according to your provided data):

~/lib/nagios/plugins/check_http -I PUTYOURHOSTIPHERE -u ‘www.google.com’ --ssl -v

…param “-v” is for debugging output. If this does not work try the command without “–ssl”.

HTH,

Marcel

···

Nicholson, Charles (RIS-BNA) cnicholson@vitalchek.com schrieb am Do., 29. Okt. 2015 um 20:40 Uhr:

I’m trying to setup OMD with Check _MK and every attempt I make to contact a known website, internal or external fails with a connection_refused, unable to open TCP socket message. I need to be able to complete HTTP checks similar to what I have already in Nagios with curl commands and find results. I also need to test the check via server command line. Can you explain what is going on? Thank you.

check_mk_active-http! -I $HOSTADDRESS$ -u ‘www.google.com’ -ssl

HTTP CRITICAL - Unable to open TCP socket

---------------------------------------- The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Charles,

The -u option (url) is used to specify the url, not the hostname.
The command should be something like this:

~/lib/nagios/plugins/check_http -H 'www.google.com ’ -I
PUTYOURHOSTIPHERE -u ‘/’ --ssl

-H is used to specify the host header (vhost in WATO).
-u is used to spedify the url to reach (i.e. / or

/search?q=whatever+query)

Regards,

Paul
···

On 29/10/15 22:14, Marcel Schulte
wrote:

Hi Charles,

      at first: knowing your used OMD and Check_MK version could

help debugging.

      Generally you can check what's going on with active http

checks by navigating to your terminal console, become OMD
siteuser and execute this (according to your provided data):

~/lib/nagios/plugins/check_http -I PUTYOURHOSTIPHERE -u ’
–ssl -v

      ...param "-v" is for debugging output. If this does not

work try the command without “–ssl”.

HTH,

Marcel

Nicholson, Charles (RIS-BNA) < >
schrieb am Do., 29. Okt. 2015 um 20:40�Uhr:

      I'm trying

to setup OMD with Check _MK and every attempt I make to
contact a known website, internal or external fails with a
connection_refused, unable to open TCP socket message.� I need
to be able to complete HTTP checks similar to what I have
already in Nagios with curl commands and find results.� I also
need to test the check via server command line.� Can you
explain what is going on?� Thank you.

      check_mk_active-http! -I $HOSTADDRESS$ -u '[](http://www.google.com)          ' -ssl

HTTP CRITICAL - Unable to open TCP socket
---------------------------------------- The information
contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above.
This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient,
you are hereby notified that you have received this document
in error and that any review, dissemination, distribution, or
copying of this message is strictly prohibited. If you have
received this communication in error, please notify us
immediately by e-mail, and delete the original message.


checkmk-en mailing list

_______________________________________________
checkmk-en mailing list

www.google.comcnicholson@vitalchek.com
www.google.com

checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
checkmk-en@lists.mathias-kettner.dehttp://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi Paul,

thanks for clarification - it’s somewhat late and I should go to bed, did not recognize the -u param issue :wink:

Regards,

Marcel

···

Paul Bongers check-mk@paul-bongers.nl schrieb am Do., 29. Okt. 2015 um 23:14 Uhr:

Hi Charles,

The -u option (url) is used to specify the url, not the hostname.

The command should be something like this:

~/lib/nagios/plugins/check_http -H 'www.google.com ’ -I
PUTYOURHOSTIPHERE -u ‘/’ --ssl

-H is used to specify the host header (vhost in WATO).

-u is used to spedify the url to reach (i.e. / or

/search?q=whatever+query)

Regards,



Paul
  On 29/10/15 22:14, Marcel Schulte > wrote:

Hi Charles,

      at first: knowing your used OMD and Check_MK version could

help debugging.

      Generally you can check what's going on with active http

checks by navigating to your terminal console, become OMD
siteuser and execute this (according to your provided data):

~/lib/nagios/plugins/check_http -I PUTYOURHOSTIPHERE -u 'www.google.com
–ssl -v

      ...param "-v" is for debugging output. If this does not

work try the command without “–ssl”.

HTH,

Marcel

Nicholson, Charles (RIS-BNA) <cnicholson@vitalchek.com >
schrieb am Do., 29. Okt. 2015 um 20:40 Uhr:

      I'm trying

to setup OMD with Check _MK and every attempt I make to
contact a known website, internal or external fails with a
connection_refused, unable to open TCP socket message. I need
to be able to complete HTTP checks similar to what I have
already in Nagios with curl commands and find results. I also
need to test the check via server command line. Can you
explain what is going on? Thank you.

      check_mk_active-http! -I $HOSTADDRESS$ -u '[](http://www.google.com)[www.google.com](http://www.google.com)' -ssl

      HTTP CRITICAL - Unable to open TCP socket





      ---------------------------------------- The information

contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above.
This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient,
you are hereby notified that you have received this document
in error and that any review, dissemination, distribution, or
copying of this message is strictly prohibited. If you have
received this communication in error, please notify us
immediately by e-mail, and delete the original message.

      _______________________________________________

      checkmk-en mailing list

      checkmk-en@lists.mathias-kettner.de

      [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en