Nagios check a jsp file

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Thibault Genessay
> Sent: Thursday, December 15, 2005 11:36 AM
> To: Pantke, Cale
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Nagios check a jsp file
> 
> Pantke, Cale wrote:
> 
> >I have a link that looks like this http://hostnae:8080/login.jsp (I
> edited
> >the actual link on purpose) and I need to monitor that it is sending
data
> >correctly when looking at it. I used the check_http command like
this.
> >status:/var/www# /opt/nagios/libexec/check_http -H 10.3.8.41 -u
> >http://hostnae:8080/login.jsp
> >HTTP CRITICAL: HTTP/1.1 500 Internal Server Error
> >
> >However I know that when I go to that in a browser it pops up fine.
> Anyone
> >know of a solution to this? Is there a special plugin or command I
can do
> >for a .jsp file? I looked for a plugin and I could only find
"webinject"
> >which doesn't seem to work with Nagios.
> >
> You might want to try something like the attached Python script. It
uses
> the lynx browser to get the page and search for a magic phrase. It's
> just a sketch but should give you an overview of another feasible
> approach to do HTTP checking.

Note that check_http has this (and more) functionality using the -e, -s,
-r or -R parameters without the need to invoke two additional processes
(python and lynx).

--
Marc 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Nagios-users mailing list
Nagios-users at 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