[Nagiosplug-help] check_http -S problem after upgrade to 1.4.5

[Marcel Mitsuto Fucatu Sugano]

I am inside the network, that's why i've to specify the virtual host as
well.

>From my slackware box at another site i've managed to monitor it without
problems. The problem only presents with the newly compiled 1.4.5
version of the check_http plugin, which i have to put in produtcion
because it has the -k flag, for specifying a referer to bypass an apache
condition for one specific request.

But I am without luck trying to compile it.

I've already try the --enable-rpath as Sean Finney pointed, same result.

Don't know anything else that I could gather of information to place
here. Just hoping that someone had passed through the same problem and
solved it.

Thanks anyway.

Marcel


On Thu, 2006-12-07 at 23:36 +0000, Ton Voon wrote:
> Marcel,
> 
> 
> I've assumed that visitante.sac.uol.com.br is a public site.
> 
> 
> On my debian server and my sol9 server, I've run:
> 
> 
> check_http -S -f critical -p 443 -H
> visitante.sac.uol.com.br -u /esqueci-senha.html  -w 10 -c 20 -t 30 -v
> 
> 
> And this comes back OK - 4581 bytes. The command you are running is:
> 
> 
> check_http -S -I 10.6.19.13 -f critical -p 443 -H
> visitante.sac.uol.com.br -u /esqueci-senha.html  -w 10 -c 20 -t 30 -v
> 
> 
> I've not used the -I flag, but I note that 10.6.19.13 is not the
> public address. Are you are trying to hit the server via an internal
> IP?
> 
> 
> Ton
> 
> On 7 Dec 2006, at 20:20, Marcel Mitsuto Fucatu Sugano wrote:
> 
> > I've just set the LD_RUN_PATH as mencioned by Ton Voon about solaris
> > problems, but still no luck.
> > 
> > 
> > I keep getting "Error on receive" message after issuing a check_http
> > with -S flag.
> > 
> > 
> > Thanks anyway.
> > 
> > 
> > Marcel
> > 
> > 
> > 
> > 
> > On Thu, 2006-12-07 at 18:17 -0200, Marcel Mitsuto Fucatu Sugano
> > wrote:
> > > OS: Solaris 9
> > > Nagios-2.5
> > > nagios-plugins-1.4.5
> > > 
> > > 
> > > 
> > > 
> > > On Fri, 2006-12-01 at 12:34 -0200, Marcel Mitsuto Fucatu Sugano
> > > wrote:
> > > > Hello,
> > > > 
> > > > 
> > > > I need to upgrade check_http, and when put into production, all
> > > > SSL
> > > > based checks are troubled. Does anyone has seen anything like
> > > > this or
> > > > has gone through the same problem before?
> > > > 
> > > > 
> > > > Thanks in advance.
> > > > 
> > > > 
> > > > Marcel
> > > > 
> > > > 
> > > > ---------------------------------cut------------------------------------
> > > > bash-2.05# ~/check_http --version
> > > > check_http (nagios-plugins 1.4.5) 1.96
> > > > bash-2.05# ~/check_http -S -I 10.6.19.13 -f critical -p 443 -H
> > > > visitante.sac.uol.com.br -u /esqueci-senha.html  -w 10 -c 20 -t
> > > > 30 -v
> > > > CRITICAL - Cannot make SSL connection 
> > > > GET /esqueci-senha.html HTTP/1.0
> > > > User-Agent: check_http/1.96 (nagios-plugins 1.4.5)
> > > > Host: visitante.sac.uol.com.br
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Error on receive
> > > > bash-2.05# ./check_http -S -I 10.6.19.13 -f critical -p 443 -H
> > > > visitante.sac.uol.com.br -u /esqueci-senha.html  -w 10 -c 20 -t
> > > > 30   
> > > > HTTP ok: HTTP/1.1 200 OK -   0.560 second response time |time=
> > > > 0.560
> > > > bash-2.05# ./check_http --version
> > > > check_http (nagios-plugins 1.3.0) 1.24
> > > > The nagios plugins come with ABSOLUTELY NO WARRANTY. You may
> > > > redistribute
> > > > copies of the plugins under the terms of the GNU General Public
> > > > License.
> > > > For more information about these matters, see the file named
> > > > COPYING.
> > > > bash-2.05# 
> > > > 
> > > > 
> 
> 
> http://www.altinity.com
> T: +44 (0)870 787 9243
> F: +44 (0)845 280 1725
> Skype: tonvoon
> 
> 
> 
> 


AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/.

NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information. If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/.