Yeah I saw that, which is why I opened the ticket with Oracle. When I remove the -S switch, it just reports that it gets no data back from the server. And I know for a fact it actually is using SSL. I don't suppose there's a known issue with SSLv3 and the check_http plugin?
-----Original Message----- From: Marc Powell [mailto:m...@ena.com] Sent: Thursday, April 02, 2009 12:17 PM To: Nagios Users Subject: Re: [Nagios-users] unable to use check_http with oracle applicationserver On Apr 2, 2009, at 8:28 AM, Alex Alexiou wrote: > On OAS, the error logs show this: > > [Thu Apr 2 09:20:07 2009] [error] mod_ossl: SSL call to NZ function > nzos_Handshake failed with error 28858 Google does have hits on this specific error message. It's about 2.5 years old but may be the version you are using... http://kr.forums.oracle.com/forums/thread.jspa?threadID=73535&tstart=255 "I got this error in 10.1.2.0.2 and opened an SR. I was told that the problem is due to 'Internal bug:3824477'." > [Thu Apr 2 09:20:07 2009] [error] mod_ossl: SSL protocol error > [Hint: the client probably speaks HTTPS over HTTP protocol] This tells me that check_http is speaking HTTPS, but :443 on your server is not. :443 is expecting standard HTTP protocol. Probably because of the broken SSL call. -- Marc ------------------------------------------------------------------------ ------ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null