Monitor https port in a non default port error

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
rohithroki
Posts: 138
Joined: Mon Nov 30, 2015 6:12 am

Monitor https port in a non default port error

Post by rohithroki »

Dear Team,
I am trying to configure https port for a non default port in nagios using the below command.

# ./check_http -S -H x.x.x.x -p 8080
I am getting the below error for the command

CRITICAL - Cannot make SSL connection.
139738252154728:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:769:

Kindly help me in fixing the error.

regards,
RKJ
User avatar
rhassing
Posts: 416
Joined: Sat Oct 05, 2013 10:29 pm
Location: Netherlands

Re: Monitor https port in a non default port error

Post by rhassing »

I assume the webpage is working when you browse to
https://x.x.x.x:8080
What happens if you try:

Code: Select all

./check_http -H x.x.x.x -p 8080
Rob Hassing
Image
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Monitor https port in a non default port error

Post by rkennedy »

Thanks @rhassing!

@robithroki - let us know the result.
Former Nagios Employee
rohithroki
Posts: 138
Joined: Mon Nov 30, 2015 6:12 am

Re: Monitor https port in a non default port error

Post by rohithroki »

hi rkennedy,rhassing

Thank you for your reply and apologies for the delay.

i have executed the below command in the nagios server and getting the below error

CRITICAL- Socket time out after 10 seconds

i have increased the time interval and checked and still i get the same error.Also telnet works fine for the below port .

regards,
RKJ
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Monitor https port in a non default port error

Post by rkennedy »

What application is running on port 8080?

From the Nagios machine, please post the result of nmap x.x.x.x (where x.x.x.x is the IP you're attempting to monitor)
Former Nagios Employee
rohithroki
Posts: 138
Joined: Mon Nov 30, 2015 6:12 am

Re: Monitor https port in a non default port error

Post by rohithroki »

@rkennedy

please find the results of nmap command

8080/tcp open http-proxy

Regards,
RKJ
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Monitor https port in a non default port error

Post by rkennedy »

Weird, the port is open. Let's dig into it with curl.

Can you please run the following, and post the output back?

Code: Select all

curl -v "https://x.x.x.x:8080"
Former Nagios Employee
rohithroki
Posts: 138
Joined: Mon Nov 30, 2015 6:12 am

Re: Monitor https port in a non default port error

Post by rohithroki »

please find the result of curl command below

curl -v "https://x.x.x.x:8080"
* About to connect() to x.x.x.x port 8080 (#0)
* Trying x.x.x.x... connected
* Connected to x.x.x.x (x.x.x.x) port 8080 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* NSS error -12263
* Closing connection #0
* SSL connect error
curl: (35) SSL connect error
User avatar
rhassing
Posts: 416
Joined: Sat Oct 05, 2013 10:29 pm
Location: Netherlands

Re: Monitor https port in a non default port error

Post by rhassing »

and what about:

Code: Select all

curl -v "http://x.x.x.x:8080"
Rob Hassing
Image
rohithroki
Posts: 138
Joined: Mon Nov 30, 2015 6:12 am

Re: Monitor https port in a non default port error

Post by rohithroki »

please find the curl results for http

curl -v "http://x.x.x.x:8080"
* About to connect() to x.x.x.x port 8080 (#0)
* Trying x.x.x.x... connected
* Connected to x.x.x.x (x.x.x.x) port 8080 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.2.3 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: x.x.x.x:8080
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Type: text/html; charset=ISO-8859-1
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Length: 284
< Server: Jetty(9.2.1.v20140609)
<
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404</h2>
<p>Problem accessing /. Reason:
<pre> Not Found</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/>

</body>
</html>
* Connection #0 to host x.x.x.x left intact
* Closing connection #0
Locked