subject:"\[Nagios\-users\] check

Re: [Nagios-users] check_http SSL cert. date format

2013-08-17 Thread William Leibzon

If you clone nagios-plugins then simply do pull request from a clean copy.
Otherwise send a patch to this mail list and I'll commit it being as I'm
the last one to work on certificate certificate check for check_http.


On Sat, Aug 17, 2013 at 11:37 AM, Niall O Broin wrote:

> Making the date format for check_http --ssl configurable has been
> requested for quite a while now, but it hasn't seemed to bother any
> committers enough to ever fix it.
>
> I fixed it a while ago on my local copy of check_http (didn't make it
> configurable - just hard coded what I wanted in place of the hard coded us
> format) but today I decided I'd make it configurable.
>
> It'd be nice if it'd just read a  date_format=  line from nagios.cfg but
> it seems that nagios plugins exist in quite a separate universe from nagios
> and that isn't easy - I'd be delighted if somebody would tell me I'm wrong.
>
> So, I've made each of check_http, check_smtp and check_tcp now take a
> --date-format flag, with allowed values the same as those in the nagios
> config file i.e.
>
> us  (MM-DD- HH:MM)
> euro(DD-MM- HH:MM)
> iso8601 (-MM-DD HH:MM)
> strict-iso8601  (-MM-DDTHH:MM)
>
> Note that I've dropped the seconds value as it's apparently not available.
>
> They also take a short option of -o which was decided on from the few
> available in each of check_http, check_smtp and check_tcp .
>
> Is there any interest in taking these changes back into the plugins
> source? If so, who would I send them to?
>
> I made the changes in a copy of nagios-plugins-1.4.16-89-gbfe6 and I just
> cloned the git repository and see there are quite some changes in that
> compared to nagios-plugins-1.4.16-89-gbfe6, but I doubt it'd be too much
> effort for me to redo my changes in the current git tree.
>
>
>
>
> Kindest regards,
>
>
>
> Niall  O Broin
>
>
>
>
>
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> 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
>
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___
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] check_http SSL cert. date format

2013-08-17 Thread Niall O Broin

Making the date format for check_http --ssl configurable has been requested for 
quite a while now, but it hasn't seemed to bother any committers enough to ever 
fix it.

I fixed it a while ago on my local copy of check_http (didn't make it 
configurable - just hard coded what I wanted in place of the hard coded us 
format) but today I decided I'd make it configurable.

It'd be nice if it'd just read a  date_format=  line from nagios.cfg but it 
seems that nagios plugins exist in quite a separate universe from nagios and 
that isn't easy - I'd be delighted if somebody would tell me I'm wrong.

So, I've made each of check_http, check_smtp and check_tcp now take a 
--date-format flag, with allowed values the same as those in the nagios config 
file i.e. 

us  (MM-DD- HH:MM)
euro(DD-MM- HH:MM)
iso8601 (-MM-DD HH:MM)
strict-iso8601  (-MM-DDTHH:MM)

Note that I've dropped the seconds value as it's apparently not available.

They also take a short option of -o which was decided on from the few available 
in each of check_http, check_smtp and check_tcp .

Is there any interest in taking these changes back into the plugins source? If 
so, who would I send them to?

I made the changes in a copy of nagios-plugins-1.4.16-89-gbfe6 and I just 
cloned the git repository and see there are quite some changes in that compared 
to nagios-plugins-1.4.16-89-gbfe6, but I doubt it'd be too much effort for me 
to redo my changes in the current git tree.




Kindest regards,



Niall  O Broin





signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___
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

Re: [Nagios-users] check_http with regex on redirects

2013-08-02 Thread james

>Try -f follow ?
>
>justinp@cerberus:~$ /usr/lib/nagios/plugins/check_http -h |grep -- -f
>[-b proxy_auth] [-f ]
>-f, --onredirect=

Looks like that will work, thank you!
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___
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

Re: [Nagios-users] check_http with regex on redirects

2013-08-02 Thread Justin T Pryzby

Try -f follow ?

justinp@cerberus:~$ /usr/lib/nagios/plugins/check_http -h |grep -- -f
   [-b proxy_auth] [-f ]
 -f, --onredirect=

On Fri, Aug 02, 2013 at 03:13:41PM -0400, james wrote:
> We were using an old version of check_http, 1.4.10, to look for the regex 
> '' on our sites using check_http. Recently we upgraded to a 
> different server (from centos to ubuntu) and re-installed nagios using the 
> package system. Now we are at version 1.4.15 of check_http and this no 
> longer returns OK status for sites where the page is redrected or rewritten 
> i get this instead:
> 
> HTTP CRITICAL: HTTP/1.1 301 Moved Permanently - pattern not found - 402 
> bytes in 0.222 second response time 
> 
> I'm not sure if it's a platform difference or something that changes in the 
> plugin. Any advice for getting this check to complete successfully again?
> 
> 

> --
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk

> ___
> 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


--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
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] check_http with regex on redirects

2013-08-02 Thread james

We were using an old version of check_http, 1.4.10, to look for the regex 
'' on our sites using check_http. Recently we upgraded to a 
different server (from centos to ubuntu) and re-installed nagios using the 
package system. Now we are at version 1.4.15 of check_http and this no 
longer returns OK status for sites where the page is redrected or rewritten 
i get this instead:

HTTP CRITICAL: HTTP/1.1 301 Moved Permanently - pattern not found - 402 
bytes in 0.222 second response time 

I'm not sure if it's a platform difference or something that changes in the 
plugin. Any advice for getting this check to complete successfully again?


--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-09 Thread Claudio Kuenzler

>
> If I use -R "Web" the response is ok but if i use -R "Web somethin" it
> returns error!
>

Because the pattern needs to exist in the source code.

./check_http -H granma.gr -u /index.html -R "Web somethin"
HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 4342 bytes in 0.126
second response time |time=0.125853s;;;0.00 size=4342B;;;0

./check_http -H granma.gr -u /index.html -R "Web Design"
HTTP OK: HTTP/1.1 200 OK - 4342 bytes in 0.125 second response time
|time=0.124846s;;;0.00 size=4342B;;;0




>
>
> 2013/5/9 Claudio Kuenzler 
>
>>
>> Sun May 5 22:29:03 EEST 2013 /usr/lib64/nagios/plugins/check_http -H
>>> granma.gr -u http://granma.gr/index.html -R "Web " -w 10 -c 20
>>> Name or service not known HTTP CRITICAL - Unable to open TCP socket
>>>
>>
>> You have to break up the -u argument. -u expects the path, not the
>> complete URI. So in this case:
>>
>> /usr/lib64/nagios/plugins/check_http -H granma.gr -u /index.html -R
>> "Web" -w 10 -c 20
>>
>>
>>
>> --
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their applications. This 200-page book is written by three acclaimed
>> leaders in the field. The early access version is available now.
>> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>>
>> ___
>> 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
>>
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> ___
> 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
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-09 Thread Κοκμάδης Δημήτριος

Thank you for the answer,

The problem doesn't seem to be at the url but at the -R option

If I use -R "Web" the response is ok but if i use -R "Web somethin" it
returns error!


2013/5/9 Claudio Kuenzler 

>
> Sun May 5 22:29:03 EEST 2013 /usr/lib64/nagios/plugins/check_http -H
>> granma.gr -u http://granma.gr/index.html -R "Web " -w 10 -c 20
>> Name or service not known HTTP CRITICAL - Unable to open TCP socket
>>
>
> You have to break up the -u argument. -u expects the path, not the
> complete URI. So in this case:
>
> /usr/lib64/nagios/plugins/check_http -H granma.gr -u /index.html -R "Web"
> -w 10 -c 20
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> ___
> 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
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-09 Thread Claudio Kuenzler

> Sun May 5 22:29:03 EEST 2013 /usr/lib64/nagios/plugins/check_http -H
> granma.gr -u http://granma.gr/index.html -R "Web " -w 10 -c 20
> Name or service not known HTTP CRITICAL - Unable to open TCP socket
>

You have to break up the -u argument. -u expects the path, not the complete
URI. So in this case:

/usr/lib64/nagios/plugins/check_http -H granma.gr -u /index.html -R "Web"
-w 10 -c 20
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-05 Thread Κοκμάδης Δημήτριος

Thank you for the replies.

I tried to use all these before asking!

By the check_debug.sh

Sun May 5 22:29:03 EEST 2013 /usr/lib64/nagios/plugins/check_http -H
granma.gr -u http://granma.gr/index.html -R "Web " -w 10 -c 20
Name or service not known HTTP CRITICAL - Unable to open TCP socket


If i check the same without space it works!

Do you have any ideas?


2013/5/5 Páll Guðjón Sigurðsson 

> Put your ARG in quotes. So it looks like this:
>
> $USER1$/check_http -H '$ARG1$' -s '$ARG2$' -w 10 -c 20
>
> Then it will handle spaces.
>
> Alternatively, you can use custom variables to a check command that is
> more complex, but in return your service definitions will become much more
> readable. Example:
>
>
> define service {
> host_name   HOSTNAME
> service_description http://...
> check_command   okc-check_http
> use generic-service
>
> __RESPONSE_WARNING  2
> __RESPONSE_CRITICAL 10
> __SEARCH_STRING
> __VIRTUAL_HOST  HOSTNAME
> __PORT  80
> __URI   /
>
> }
>
>
>
> define command {
>   command_line   $USER1$/check_http -I $HOSTADDRESS$ -H
> "$_SERVICE_VIRTUAL_HOST$" -p "$_SERVICE_PORT$" -u "$_SERVICE_URI$" -s
> "$_SERVICE_SEARCH_STRING$" -w "$_SERVICE_RESPONSE_WARNING$" -c
> "$_SERVICE_RESPONSE_CRITICAL$"
>   command_name       okc-check_http
> }
>
>
>
>
> - Original Message -
> From: "Κοκμάδης Δημήτριος" 
> To: nagios-users@lists.sourceforge.net
> Sent: Sunday, May 5, 2013 3:23:02 PM
> Subject: [Nagios-users] check_http with spaces problem
>
>
>
>
>
>
>
>
> Hi,
>
> I am trying to check multiple http sites, so i configure a bash script
> which create the service definition but i faced a problem when the expected
> string has spaces.
>
> So the command definition is like:
>
> $USER1$/check_http -H $ARG1$ -s $ARG2$ -w 10 -c 20
>
> if i pass an $ARG2$ without spaces it's work fine, but if it has spaces
> nagios can't make check. Could you give me a help?
>
> Thanks,
>
> Jim
>
>
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> 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
>
>
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> 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
>
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-05 Thread Páll Guðjón Sigurðsson

Put your ARG in quotes. So it looks like this:

$USER1$/check_http -H '$ARG1$' -s '$ARG2$' -w 10 -c 20 

Then it will handle spaces.

Alternatively, you can use custom variables to a check command that is more 
complex, but in return your service definitions will become much more readable. 
Example:


define service {
host_name   HOSTNAME
service_description http://...
check_command   okc-check_http
use generic-service

__RESPONSE_WARNING  2
__RESPONSE_CRITICAL 10
__SEARCH_STRING
__VIRTUAL_HOST  HOSTNAME
__PORT  80
__URI   /

}



define command {
  command_line   $USER1$/check_http -I $HOSTADDRESS$ -H 
"$_SERVICE_VIRTUAL_HOST$" -p "$_SERVICE_PORT$" -u "$_SERVICE_URI$" -s 
"$_SERVICE_SEARCH_STRING$" -w "$_SERVICE_RESPONSE_WARNING$" -c 
"$_SERVICE_RESPONSE_CRITICAL$"
  command_name   okc-check_http
}




- Original Message -
From: "Κοκμάδης Δημήτριος" 
To: nagios-users@lists.sourceforge.net
Sent: Sunday, May 5, 2013 3:23:02 PM
Subject: [Nagios-users] check_http with spaces problem








Hi, 

I am trying to check multiple http sites, so i configure a bash script which 
create the service definition but i faced a problem when the expected string 
has spaces. 

So the command definition is like: 

$USER1$/check_http -H $ARG1$ -s $ARG2$ -w 10 -c 20 

if i pass an $ARG2$ without spaces it's work fine, but if it has spaces nagios 
can't make check. Could you give me a help? 

Thanks, 

Jim 

--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
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

--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
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

Re: [Nagios-users] check_http with spaces problem

2013-05-05 Thread Sunil Sankar

Please put it within quotes , that should help


On Sun, May 5, 2013 at 8:53 PM, Κοκμάδης Δημήτριος wrote:

> Hi,
>
> I am trying to check multiple http sites, so i configure a bash script
> which create the service definition but i faced a problem when the expected
> string has spaces.
>
> So the command definition is like:
>
> $USER1$/check_http -H $ARG1$ -s $ARG2$ -w 10 -c 20
>
> if i pass an $ARG2$ without spaces it's work fine, but if it has spaces
> nagios can't make check. Could you give me a help?
>
> Thanks,
>
> Jim
>
>
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> 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
>



-- 
Regards
Sunil Sankar
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2___
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] check_http with spaces problem

2013-05-05 Thread Κοκμάδης Δημήτριος

Hi,

I am trying to check multiple http sites, so i configure a bash script
which create the service definition but i faced a problem when the expected
string has spaces.

So the command definition is like:

$USER1$/check_http -H $ARG1$ -s $ARG2$ -w 10 -c 20

if i pass an $ARG2$ without spaces it's work fine, but if it has spaces
nagios can't make check. Could you give me a help?

Thanks,

Jim
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2___
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] check_http --sni not working in nagios plugins 1.4.16

2013-03-21 Thread Justin Garrison

I am running Nagios Core 3.2.3 on RHEL 5.6 and cannot get certificate
checking working for my SNI enabled web servers. Every time I check the
certificate it only returns the host certificate instead of the vhost
certificate.

Is there documentation that lists what is required on the Nagios host to
check SNI enabled web servers? All I found is that plugins >1.4.15 are
required.

An example command I am running to test from the server is

./check_http --sni --ssl -H url-of-service.com -C 14

As I said, this ALWAYS returns the host certificate and not the service
certificate. I can only think there must be a problem with something on my
Nagios server that is causing this to fail.

Thank you

--
Justin Garrison
Systems Administrator
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
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] check_http --sni not working in nagios plugins 1.4.16

2013-03-21 Thread Justin Garrison

I am running Nagios Core 3.2.3 on RHEL 5.6 and cannot get certificate
checking working for my SNI enabled web servers. Every time I check the
certificate it only returns the host certificate instead of the vhost
certificate.

Is there documentation that lists what is required on the Nagios host to
check SNI enabled web servers? All I found is that plugins >1.4.15 are
required.

An example command I am running to test from the server is

./check_http --sni --ssl -H url-of-service.com -C 14

As I said, this ALWAYS returns the host certificate and not the service
certificate. I can only think there must be a problem with something on my
Nagios server that is causing this to fail.

Thank you

--
Justin Garrison
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
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

Re: [Nagios-users] check_http fails on Cisco ASA

2013-01-31 Thread Frank Bulk

That was it  thanks!

 

Frank

 

From: Travis Runyard [mailto:travisruny...@gmail.com] 
Sent: Thursday, January 31, 2013 11:07 PM
To: Nagios Users List
Subject: Re: [Nagios-users] check_http fails on Cisco ASA

 

Have you tried check_http -I  -S

The -H is for hostnames

 

On Thu, Jan 31, 2013 at 8:35 PM, Frank Bulk mailto:frnk...@iname.com> > wrote:

Does anyone have check_http working against the SSL VPN GUI interface of a
Cisco ASA?

Whenever I check it always closes, but wget and curl work fine:
=
nagios:/usr/lib/nagios/plugins# ./check_http -H  -S -v
GET / HTTP/1.1
User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
Connection: close
Host: 


CRITICAL - Socket timeout after 10 seconds
nagios:/usr/lib/nagios/plugins#
=
nagios:/usr/lib/nagios/plugins# wget https:// <https://%3cip> 
--no-check-certificate
--2013-01-31 22:31:39--  https:// <https://%3cip%3e/> /
Connecting to :443... connected.
WARNING: cannot verify âs certificate, issued by
â/CN=/unstructuredName=â

Self-signed certificate encountered.
WARNING: certificate common name âââ

HTTP request sent, awaiting response... 302 Object Moved
Location: /+CSCOE+/logon.html [following]
--2013-01-31 22:31:39--  https:// <https://%3cip%3e/+CSCOE+/logon.html>
/+CSCOE+/logon.html
Connecting to :443... connected.
WARNING: cannot verify âs certificate, issued by
â/CN=/unstructuredName=â

Self-signed certificate encountered.
WARNING: certificate common name âââ

HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: âindex.htmlâ

[ <=>
] 4,514   --.-K/s   in 0.03s

2013-01-31 22:31:39 (158 KB/s) - âindex.htmlâ

nagios:/usr/lib/nagios/plugins#
=
nagios:/usr/lib/nagios/plugins# curl https:// <https://%3cip> 
--insecure -v
* About to connect() to  port 443 (#0)
*   Trying ... connected
* Connected to  () port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using RC4-SHA
* Server certificate:
*subject: CN=; unstructuredName=
*start date: 2010-02-03 00:10:30 GMT
*expire date: 2020-02-01 00:10:30 GMT
*common name:  (does not match '')
*issuer: CN=; unstructuredName=
*SSL certificate verify result: self signed certificate (18),
continuing anyway.
> GET / HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0
OpenSSL/0.9.8o zlib/1.2.3.4 <http://1.2.3.4>  libidn/1.15 libssh2/1.2.5
> Host: 
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 302 Object Moved
< Server: Cisco AWARE 2.0
<
Fri, 01 Feb 2013 04:07:54 GMT
< Location: /+CSCOE+/logon.html
< Set-Cookie: tg=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Cache-Control: no-cache
< Pragma: no-cache
* HTTP/1.0 connection set to keep alive!
< Connection: Keep-Alive
< Date:

* Connection #0 to host  left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
nagios:/usr/lib/nagios/plugins#
=



--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
<mailto: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

 

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan___
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

Re: [Nagios-users] check_http fails on Cisco ASA

2013-01-31 Thread Travis Runyard

Have you tried check_http -I  -S
The -H is for hostnames


On Thu, Jan 31, 2013 at 8:35 PM, Frank Bulk  wrote:

> Does anyone have check_http working against the SSL VPN GUI interface of a
> Cisco ASA?
>
> Whenever I check it always closes, but wget and curl work fine:
> =
> nagios:/usr/lib/nagios/plugins# ./check_http -H  -S -v
> GET / HTTP/1.1
> User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
> Connection: close
> Host: 
>
>
> CRITICAL - Socket timeout after 10 seconds
> nagios:/usr/lib/nagios/plugins#
> =
> nagios:/usr/lib/nagios/plugins# wget https:// --no-check-certificate
> --2013-01-31 22:31:39--  https:///
> Connecting to :443... connected.
> WARNING: cannot verify âs certificate, issued by
> â/CN=/unstructuredName=â
>
> Self-signed certificate encountered.
> WARNING: certificate common name âââ
>
> HTTP request sent, awaiting response... 302 Object Moved
> Location: /+CSCOE+/logon.html [following]
> --2013-01-31 22:31:39--  https:///+CSCOE+/logon.html
> Connecting to :443... connected.
> WARNING: cannot verify âs certificate, issued by
> â/CN=/unstructuredName=â
>
> Self-signed certificate encountered.
> WARNING: certificate common name âââ
>
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: âindex.htmlâ
>
> [ <=>
> ] 4,514   --.-K/s   in 0.03s
>
> 2013-01-31 22:31:39 (158 KB/s) - âindex.htmlâ
>
> nagios:/usr/lib/nagios/plugins#
> =
> nagios:/usr/lib/nagios/plugins# curl https:// --insecure -v
> * About to connect() to  port 443 (#0)
> *   Trying ... connected
> * Connected to  () port 443 (#0)
> * successfully set certificate verify locations:
> *   CAfile: none
>   CApath: /etc/ssl/certs
> * SSLv3, TLS handshake, Client hello (1):
> * SSLv3, TLS handshake, Server hello (2):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Server finished (14):
> * SSLv3, TLS handshake, Client key exchange (16):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSL connection using RC4-SHA
> * Server certificate:
> *subject: CN=; unstructuredName=
> *start date: 2010-02-03 00:10:30 GMT
> *expire date: 2020-02-01 00:10:30 GMT
> *common name:  (does not match '')
> *issuer: CN=; unstructuredName=
> *SSL certificate verify result: self signed certificate (18),
> continuing anyway.
> > GET / HTTP/1.1
> > User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0
> OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.5
> > Host: 
> > Accept: */*
> >
> * HTTP 1.0, assume close after body
> < HTTP/1.0 302 Object Moved
> < Server: Cisco AWARE 2.0
> <
> Fri, 01 Feb 2013 04:07:54 GMT
> < Location: /+CSCOE+/logon.html
> < Set-Cookie: tg=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/
> < Content-Type: text/html; charset=UTF-8
> < Transfer-Encoding: chunked
> < Cache-Control: no-cache
> < Pragma: no-cache
> * HTTP/1.0 connection set to keep alive!
> < Connection: Keep-Alive
> < Date:
>
> * Connection #0 to host  left intact
> * Closing connection #0
> * SSLv3, TLS alert, Client hello (1):
> nagios:/usr/lib/nagios/plugins#
> =
>
>
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> ___
> 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
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan___
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] check_http fails on Cisco ASA

2013-01-31 Thread Frank Bulk

Does anyone have check_http working against the SSL VPN GUI interface of a
Cisco ASA?

Whenever I check it always closes, but wget and curl work fine:
=
nagios:/usr/lib/nagios/plugins# ./check_http -H  -S -v
GET / HTTP/1.1
User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
Connection: close
Host: 


CRITICAL - Socket timeout after 10 seconds
nagios:/usr/lib/nagios/plugins#
=
nagios:/usr/lib/nagios/plugins# wget https:// --no-check-certificate
--2013-01-31 22:31:39--  https:///
Connecting to :443... connected.
WARNING: cannot verify âs certificate, issued by
â/CN=/unstructuredName=â
 
Self-signed certificate encountered.
WARNING: certificate common name âââ
 
HTTP request sent, awaiting response... 302 Object Moved
Location: /+CSCOE+/logon.html [following]
--2013-01-31 22:31:39--  https:///+CSCOE+/logon.html
Connecting to :443... connected.
WARNING: cannot verify âs certificate, issued by
â/CN=/unstructuredName=â
 
Self-signed certificate encountered.
WARNING: certificate common name âââ
 
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: âindex.htmlâ

[ <=>
] 4,514   --.-K/s   in 0.03s

2013-01-31 22:31:39 (158 KB/s) - âindex.htmlâ

nagios:/usr/lib/nagios/plugins#
=
nagios:/usr/lib/nagios/plugins# curl https:// --insecure -v
* About to connect() to  port 443 (#0)
*   Trying ... connected
* Connected to  () port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using RC4-SHA
* Server certificate:
*subject: CN=; unstructuredName=
*start date: 2010-02-03 00:10:30 GMT
*expire date: 2020-02-01 00:10:30 GMT
*common name:  (does not match '')
*issuer: CN=; unstructuredName=
*SSL certificate verify result: self signed certificate (18),
continuing anyway.
> GET / HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0
OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.5
> Host: 
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 302 Object Moved
< Server: Cisco AWARE 2.0
< 
Fri, 01 Feb 2013 04:07:54 GMT
< Location: /+CSCOE+/logon.html
< Set-Cookie: tg=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Cache-Control: no-cache
< Pragma: no-cache
* HTTP/1.0 connection set to keep alive!
< Connection: Keep-Alive
< Date:

* Connection #0 to host  left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
nagios:/usr/lib/nagios/plugins#
=


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
___
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] check_http --ssl --sni returning host certificate

2013-01-11 Thread Justin Garrison

I am running red hat 5.6 with nagios core 3.2.3 and plugins 1.4.16

When I run the command
check_http --sni --ssl -H apache-vhost.com -f follow -C 8
I get the apache host certificate instead of the vhost certificate

The server is on apache 2.2.15 with sni enabled. The proper certificate
works inside a browser but no matter which vhost I use to test they always
return the host certificate information.

Is there something else that needs to be configured in nagios or on the
apache server to verify individual vhost certificates?

Thank you

--
Justin Garrison
Systems Administrator
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812___
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

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-22 Thread Claudio Kuenzler

Jaap, if you'd use check_http correctly, as the others mentioned, it would
work.
It just happens that https://latitude.google.com shows a 503 error right
this moment and for curiosity's sake I tested it:

# ./check_http -H latitude.google.com -S
HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 1119 bytes in 0.071
second response time |time=0.070649s;;;0.00 size=1119B;;;0

As you see, it works as it should if used correctly.

On Tue, Nov 20, 2012 at 10:26 AM, Travis Runyard wrote:

> He's not using host headers in his definition.
>
>
> On Tue, Nov 20, 2012 at 12:05 AM, Joerg Linge wrote:
>
>> again
>>
>> check_http -H  -u http://www.testsomething.com
>>
>> is a proxy request. NOT an valid HTTP request
>>
>> Joerg
>>
>> Am 20.11.2012 um 08:35 schrieb Jaap van Arragon > >:
>>
>> > Herewith
>> >
>> > define service{
>> >use generic-service_24x7
>> >host_name   www1
>> >service_description check http 
>> >check_command   check_http! -u
>> > http://www.testsomething.com -w 5 -c 8
>> > }
>> >
>> > This gives me a
>> >
>> > HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
>> >
>> > Back.
>> >
>> >
>> > But in the browser the check gives me a
>> >
>> > 503 statuscode back.
>> >
>> > The Nagios check_http script isn't detecting this 503 error message.
>> >
>> > Regards,
>> >
>> > Jaap
>> >
>> >
>> > On 11/20/12 8:20 AM, "Joerg Linge"  wrote:
>> >
>> >> Please provide a complete example!
>> >> check_http works correct since years
>> >>
>> >> Joerg
>> >>
>> >> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" <
>> j.vanarra...@lukkien.com>:
>> >>
>> >>> Hey Joerg,
>> >>>
>> >>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>> >>>
>> >>> any ideas?
>> >>>
>> >>> Regards,
>> >>> Jaap
>> >>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>> >>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>> >>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>> >>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>> >>>
>> >>>
>> >>> Your example
>> >>>
>> >>> /usr/local/nagios/libexec/check_http -I  -u http://
>> -w1 -c2
>> >>>
>> >>> is a proxy request!
>> >>>
>> >>> -I = ip address to connect to
>> >>> -H = HTTP/1.1 Host Header
>> >>> -u = relative url to fetch without protocol infos like http://
>> >>>
>> >>> some examples
>> >>>
>> >>> check nagios.org
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>> >>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>> >>> |time=1.703114s;;;0.00 size=54919B;;;0
>> >>>
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>> >>> nagios.org has address 96.126.126.159
>> >>>
>> >>> ok, nagios .org runns on 96.126.126.159
>> >>> lets check a non existing page. we got 404!
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> >>> nagios.org -u /404
>> >>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second
>> response
>> >>> time |time=0.536015s;;;0.00 size=17141B;;;0
>> >>>
>> >>> lets ask nagios.org for icinga.org ;) and we will get a 302
>> >>>
>> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> >>> icinga.org -u /
>> >>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>> >>> |time=1.837209s;;;0.00 size=242B;;;0
>> >>>
>> >>> Joerg
>> >>>
>> >>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon <
>> j.vanarra...@lukkien.com>:
>> >>>
>> >>>> Thank you for your reply.
>> >>>>
>> >&

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-20 Thread Travis Runyard

He's not using host headers in his definition.


On Tue, Nov 20, 2012 at 12:05 AM, Joerg Linge  wrote:

> again
>
> check_http -H  -u http://www.testsomething.com
>
> is a proxy request. NOT an valid HTTP request
>
> Joerg
>
> Am 20.11.2012 um 08:35 schrieb Jaap van Arragon  >:
>
> > Herewith
> >
> > define service{
> >use generic-service_24x7
> >host_name   www1
> >service_description check http 
> >check_command   check_http! -u
> > http://www.testsomething.com -w 5 -c 8
> > }
> >
> > This gives me a
> >
> > HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time
> >
> > Back.
> >
> >
> > But in the browser the check gives me a
> >
> > 503 statuscode back.
> >
> > The Nagios check_http script isn't detecting this 503 error message.
> >
> > Regards,
> >
> > Jaap
> >
> >
> > On 11/20/12 8:20 AM, "Joerg Linge"  wrote:
> >
> >> Please provide a complete example!
> >> check_http works correct since years
> >>
> >> Joerg
> >>
> >> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" <
> j.vanarra...@lukkien.com>:
> >>
> >>> Hey Joerg,
> >>>
> >>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
> >>>
> >>> any ideas?
> >>>
> >>> Regards,
> >>> Jaap
> >>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
> >>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
> >>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
> >>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
> >>>
> >>>
> >>> Your example
> >>>
> >>> /usr/local/nagios/libexec/check_http -I  -u http://
> -w1 -c2
> >>>
> >>> is a proxy request!
> >>>
> >>> -I = ip address to connect to
> >>> -H = HTTP/1.1 Host Header
> >>> -u = relative url to fetch without protocol infos like http://
> >>>
> >>> some examples
> >>>
> >>> check nagios.org
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
> >>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
> >>> |time=1.703114s;;;0.00 size=54919B;;;0
> >>>
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
> >>> nagios.org has address 96.126.126.159
> >>>
> >>> ok, nagios .org runns on 96.126.126.159
> >>> lets check a non existing page. we got 404!
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
> >>> nagios.org -u /404
> >>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second
> response
> >>> time |time=0.536015s;;;0.00 size=17141B;;;0
> >>>
> >>> lets ask nagios.org for icinga.org ;) and we will get a 302
> >>>
> >>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
> >>> icinga.org -u /
> >>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
> >>> |time=1.837209s;;;0.00 size=242B;;;0
> >>>
> >>> Joerg
> >>>
> >>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon <
> j.vanarra...@lukkien.com>:
> >>>
> >>>> Thank you for your reply.
> >>>>
> >>>> I¹ve tried the check without the ip adress option but it makes no
> >>>> difference.
> >>>>
> >>>> Any other ideas?
> >>>>
> >>>> Thanks.
> >>>>
> >>>>
> >>>> On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
> >>>>
> >>>>> You said u are using it like so:
> >>>>>
> >>>>> Check:
> >>>>> /usr/local/nagios/libexec/check_http -I  -u http://
> -w1
> >>>>> -c2
> >>>>>
> >>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and
> the url
> >>>>> its causing problems. Maybe its replying on the IP, but not on the
> URL your
> >>>>> providing. You prob only need one or the other if im not mistaken
> >>>&g

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-20 Thread Joerg Linge

again

check_http -H  -u http://www.testsomething.com

is a proxy request. NOT an valid HTTP request

Joerg

Am 20.11.2012 um 08:35 schrieb Jaap van Arragon :

> Herewith
> 
> define service{
>use generic-service_24x7
>host_name   www1
>service_description check http 
>check_command   check_http! -u
> http://www.testsomething.com -w 5 -c 8
> }
> 
> This gives me a 
> 
> HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time 
> 
> Back.
> 
> 
> But in the browser the check gives me a
> 
> 503 statuscode back.
> 
> The Nagios check_http script isn't detecting this 503 error message.
> 
> Regards,
> 
> Jaap
> 
> 
> On 11/20/12 8:20 AM, "Joerg Linge"  wrote:
> 
>> Please provide a complete example!
>> check_http works correct since years
>> 
>> Joerg
>> 
>> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" :
>> 
>>> Hey Joerg,
>>> 
>>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>>> 
>>> any ideas?
>>> 
>>> Regards,
>>> Jaap 
>>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>>> 
>>> 
>>> Your example
>>> 
>>> /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2
>>> 
>>> is a proxy request!
>>> 
>>> -I = ip address to connect to
>>> -H = HTTP/1.1 Host Header
>>> -u = relative url to fetch without protocol infos like http://
>>> 
>>> some examples
>>> 
>>> check nagios.org
>>> 
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>>> |time=1.703114s;;;0.00 size=54919B;;;0
>>> 
>>> 
>>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>>> nagios.org has address 96.126.126.159
>>> 
>>> ok, nagios .org runns on 96.126.126.159
>>> lets check a non existing page. we got 404!
>>> 
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>>> nagios.org -u /404
>>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response
>>> time |time=0.536015s;;;0.00 size=17141B;;;0
>>> 
>>> lets ask nagios.org for icinga.org ;) and we will get a 302
>>> 
>>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>>> icinga.org -u /
>>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>>> |time=1.837209s;;;0.00 size=242B;;;0
>>> 
>>> Joerg
>>> 
>>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
>>> 
>>>> Thank you for your reply.
>>>> 
>>>> I¹ve tried the check without the ip adress option but it makes no
>>>> difference.
>>>> 
>>>> Any other ideas?
>>>> 
>>>> Thanks.
>>>> 
>>>> 
>>>> On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
>>>> 
>>>>> You said u are using it like so:
>>>>> 
>>>>> Check:
>>>>> /usr/local/nagios/libexec/check_http -I  -u http:// -w1
>>>>> -c2
>>>>> 
>>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url
>>>>> its causing problems. Maybe its replying on the IP, but not on the URL 
>>>>> your
>>>>> providing. You prob only need one or the other if im not mistaken
>>>>> 
>>>>> Cheers!
>>>>> 
>>>>> 
>>>>> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon
>>>>>  wrote:
>>>>>> Hello,
>>>>>> 
>>>>>> Does anyone know why it gives me a 200 back?
>>>>>> 
>>>>>> If you need more info, I will gladly provide it ;-)
>>>>>> 
>>>>>> Thank you.
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> Jaap
>>>>>> 
>>>>>> 
>>>>>> On 11/16/12 11:54 AM, "Jaap van Arragon"  
>>>>>> wrote:
>>>&

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Jaap van Arragon

Herewith

define service{
use generic-service_24x7
host_name   www1
service_description check http 
check_command   check_http! -u
http://www.testsomething.com -w 5 -c 8
 }

This gives me a 

HTTP OK: HTTP/1.1 200 OK - 414 bytes in 0.002 second response time 

Back.


But in the browser the check gives me a

503 statuscode back.

The Nagios check_http script isn't detecting this 503 error message.

Regards,

Jaap


On 11/20/12 8:20 AM, "Joerg Linge"  wrote:

> Please provide a complete example!
> check_http works correct since years
> 
> Joerg
> 
> Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" :
> 
>> Hey Joerg,
>> 
>> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
>> 
>> any ideas?
>> 
>> Regards,
>> Jaap 
>> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
>> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
>> Sent: Mon, 19 Nov 2012 18:07:52 +0100
>> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
>> 
>> 
>> Your example
>> 
>> /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2
>> 
>> is a proxy request!
>> 
>> -I = ip address to connect to
>> -H = HTTP/1.1 Host Header
>> -u = relative url to fetch without protocol infos like http://
>> 
>> some examples
>> 
>> check nagios.org
>> 
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
>> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time
>> |time=1.703114s;;;0.00 size=54919B;;;0
>> 
>> 
>> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
>> nagios.org has address 96.126.126.159
>> 
>> ok, nagios .org runns on 96.126.126.159
>> lets check a non existing page. we got 404!
>> 
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> nagios.org -u /404
>> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response
>> time |time=0.536015s;;;0.00 size=17141B;;;0
>> 
>> lets ask nagios.org for icinga.org ;) and we will get a 302
>> 
>> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H
>> icinga.org -u /
>> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time
>> |time=1.837209s;;;0.00 size=242B;;;0
>> 
>> Joerg
>> 
>> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
>> 
>>> Thank you for your reply.
>>> 
>>> I¹ve tried the check without the ip adress option but it makes no
>>> difference.
>>> 
>>> Any other ideas?
>>> 
>>> Thanks.
>>> 
>>> 
>>> On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
>>> 
>>>> You said u are using it like so:
>>>> 
>>>> Check:
>>>> /usr/local/nagios/libexec/check_http -I  -u http:// -w1
>>>> -c2
>>>> 
>>>> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url
>>>> its causing problems. Maybe its replying on the IP, but not on the URL your
>>>> providing. You prob only need one or the other if im not mistaken
>>>> 
>>>> Cheers!
>>>> 
>>>> 
>>>> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon
>>>>  wrote:
>>>>> Hello,
>>>>> 
>>>>> Does anyone know why it gives me a 200 back?
>>>>> 
>>>>> If you need more info, I will gladly provide it ;-)
>>>>> 
>>>>> Thank you.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Jaap
>>>>> 
>>>>> 
>>>>> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> I¹m trying to use the check_http plugin to verify if one of our website
>>>>>> is
>>>>>> available.
>>>>>> 
>>>>>> When I check our website it gives me a 200 OK status code back even when
>>>>>> the
>>>>>> website isn¹t available en the URL gives me a 503 status code through the
>>>>>> browser.
>>>>>> 
>>>>>> After some searching I came across the post below:
>>>>>> 
>>>>>> http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
>>>>>> 
>>>>

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Joerg Linge

Please provide a complete example!
check_http works correct since years

Joerg

Am 19.11.2012 um 23:00 schrieb "Jaap van Arragon" :

> Hey Joerg,
> 
> The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)
> 
> any ideas?
> 
> Regards,
> Jaap 
> From: Joerg Linge [mailto:pitchf...@ederdrom.de]
> To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
> Sent: Mon, 19 Nov 2012 18:07:52 +0100
> Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK
> 
> 
> Your example
> 
> /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2
> 
> is a proxy request!
> 
> -I = ip address to connect to
> -H = HTTP/1.1 Host Header
> -u = relative url to fetch without protocol infos like http://
> 
> some examples
> 
> check nagios.org
> 
> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
> HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time 
> |time=1.703114s;;;0.00 size=54919B;;;0
> 
> 
> OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
> nagios.org has address 96.126.126.159
> 
> ok, nagios .org runns on 96.126.126.159
> lets check a non existing page. we got 404!
> 
> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H 
> nagios.org -u /404
> HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response 
> time |time=0.536015s;;;0.00 size=17141B;;;0
> 
> lets ask nagios.org for icinga.org ;) and we will get a 302
> 
> OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H 
> icinga.org -u /
> HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time 
> |time=1.837209s;;;0.00 size=242B;;;0
> 
> Joerg
> 
> Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
> 
> > Thank you for your reply.
> > 
> > I’ve tried the check without the ip adress option but it makes no 
> > difference.
> > 
> > Any other ideas?
> > 
> > Thanks.
> > 
> > 
> > On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
> > 
> >> You said u are using it like so:
> >> 
> >> Check:
> >> /usr/local/nagios/libexec/check_http -I  -u http:// -w1 
> >> -c2
> >> 
> >> Maybe drop the IP address? I dunno, maybe cuz you have both IP and the url 
> >> its causing problems. Maybe its replying on the IP, but not on the URL 
> >> your providing. You prob only need one or the other if im not mistaken
> >> 
> >> Cheers!
> >> 
> >> 
> >> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon 
> >>  wrote:
> >>> Hello,
> >>> 
> >>> Does anyone know why it gives me a 200 back?
> >>> 
> >>> If you need more info, I will gladly provide it ;-)
> >>> 
> >>> Thank you.
> >>> 
> >>> Regards,
> >>> 
> >>> Jaap
> >>> 
> >>> 
> >>> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
> >>> 
> >>> > Hello,
> >>> >
> >>> > I’m trying to use the check_http plugin to verify if one of our website 
> >>> > is
> >>> > available.
> >>> >
> >>> > When I check our website it gives me a 200 OK status code back even 
> >>> > when the
> >>> > website isn’t available en the URL gives me a 503 status code through 
> >>> > the
> >>> > browser.
> >>> >
> >>> > After some searching I came across the post below:
> >>> >
> >>> > http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
> >>> >
> >>> > This states that there is a bug in check_http. The only thing is that 
> >>> > the post
> >>> > is from 2003 so I expect that the necessary changes are already in the 
> >>> > new
> >>> > release.
> >>> >
> >>> > Things I’ve tried:
> >>> >
> >>> > - recompiled the latest version of the check_http plugin but the 
> >>> > necessary
> >>> > changes seems to be integrated there already.
> >>> > - updated the plugins package to the latest version for our release
> >>> >
> >>> > Check:
> >>> > /usr/local/nagios/libexec/check_http -I  -u http:// 
> >>> > -w1 -c2
> >>> >
> >>> > Packages:
> >>> >
> >>> > ii nagios-images 0.5
> >>> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Jaap van Arragon

Hey Joerg,


The 4xx and 3xx error are handeld correctly but not the 5xx error ;-)


any ideas?


Regards,
Jaap 
  _  

From: Joerg Linge [mailto:pitchf...@ederdrom.de]
To: Nagios Users List [mailto:nagios-users@lists.sourceforge.net]
Sent: Mon, 19 Nov 2012 18:07:52 +0100
Subject: Re: [Nagios-users] Check_http status 503 gives 200 OK


  Your example
  
   /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2
  
  is a proxy request!
  
  -I = ip address to connect to
  -H = HTTP/1.1 Host Header
  -u = relative url to fetch without protocol infos like http://
  
  some examples
  
  check nagios.org
  
  OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
  HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time 
|time=1.703114s;;;0.00 size=54919B;;;0
  
  
  OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
  nagios.org has address 96.126.126.159
  
  ok, nagios .org runns on 96.126.126.159
  lets check a non existing page. we got 404!
  
  OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H 
nagios.org -u /404
  HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response 
time |time=0.536015s;;;0.00 size=17141B;;;0
  
  lets ask nagios.org for icinga.org ;) and we will get a 302
  
  OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H 
icinga.org -u /
  HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time 
|time=1.837209s;;;0.00 size=242B;;;0
  
  Joerg
  
  Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :
  
  > Thank you for your reply.
  > 
  > I’ve tried the check without the ip adress option but it makes no 
difference.
  > 
  > Any other ideas?
  > 
  > Thanks.
  > 
  > 
  > On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
  > 
  >> You said u are using it like so:
  >> 
  >>Check:
  >>/usr/local/nagios/libexec/check_http -I  -u http:// 
-w1 -c2
  >> 
  >> Maybe drop the IP address?  I dunno, maybe cuz you have both IP and the 
url its causing problems. Maybe its replying on the IP, but not on the URL your 
providing.  You prob only need one or the other if im not mistaken
  >> 
  >> Cheers!
  >> 
  >> 
  >> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon 
 wrote:
  >>> Hello,
  >>> 
  >>> Does anyone know why it gives me a 200 back?
  >>> 
  >>> If you need more info, I will gladly provide it ;-)
  >>> 
  >>> Thank you.
  >>> 
  >>> Regards,
  >>> 
  >>> Jaap
  >>> 
  >>> 
  >>> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
  >>> 
  >>> > Hello,
  >>> >
  >>> > I’m trying to use the check_http plugin to verify if one of our website 
is
  >>> > available.
  >>> >
  >>> > When I check our website it gives me a 200 OK status code back even 
when the
  >>> > website isn’t available en the URL gives me a 503 status code through 
the
  >>> > browser.
  >>> >
  >>> > After some searching I came across the post below:
  >>> >
  >>> > http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
  >>> >
  >>> > This states that there is a bug in check_http. The only thing is that 
the post
  >>> > is from 2003 so I expect that the necessary changes are already in the 
new
  >>> > release.
  >>> >
  >>> > Things I’ve tried:
  >>> >
  >>> > - recompiled the latest version of the check_http plugin but the 
necessary
  >>> > changes seems to be integrated there already.
  >>> > - updated the plugins package to the latest version for our release
  >>> >
  >>> > Check:
  >>> > /usr/local/nagios/libexec/check_http -I  -u http:// 
-w1 -c2
  >>> >
  >>> > Packages:
  >>> >
  >>> > ii nagios-images 0.5
  >>> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
  >>> > ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
  >>> > ii nagios-plugins 1.4.14-1ubuntu1
  >>> > ii nagios-plugins-basic 1.4.14-1ubuntu1
  >>> > ii nagios-plugins-standard 1.4.14-1ubuntu1
  >>> > ii nagios3 3.2.0-4ubuntu2.2
  >>> > ii nagios3-cgi 3.2.0-4ubuntu2.2
  >>> > ii nagios3-common 3.2.0-4ubuntu2.2
  >>> > ii nagios3-core 3.2.0-4ubuntu2.2
  >>> > ii nagiosgrapher 1.7.1-1
  >>> >
  >>> > Does anyone know why it gives me a status 200 OK back? At the moment I 
can't
  >>> > rely on my Nagios checks..
  >>> >
  >>> > Thank you in advance
  >>> >

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Joerg Linge


Your example

 /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2

is a proxy request!

-I = ip address to connect to
-H = HTTP/1.1 Host Header
-u = relative url to fetch without protocol infos like http://

some examples

check nagios.org

OMD[gearman]:~/lib/nagios/plugins$ ./check_http -H nagios.org
HTTP OK: HTTP/1.1 200 OK - 54919 bytes in 1.703 second response time 
|time=1.703114s;;;0.00 size=54919B;;;0


OMD[gearman]:~/lib/nagios/plugins$ host nagios.org
nagios.org has address 96.126.126.159

ok, nagios .org runns on 96.126.126.159
lets check a non existing page. we got 404!

OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H nagios.org 
-u /404
HTTP WARNING: HTTP/1.1 404 Not Found - 17141 bytes in 0.536 second response 
time |time=0.536015s;;;0.00 size=17141B;;;0

lets ask nagios.org for icinga.org ;) and we will get a 302

OMD[gearman]:~/lib/nagios/plugins$ ./check_http -I 96.126.126.159 -H icinga.org 
-u /
HTTP OK: HTTP/1.1 302 Found - 242 bytes in 1.837 second response time 
|time=1.837209s;;;0.00 size=242B;;;0

Joerg

Am 19.11.2012 um 17:14 schrieb Jaap van Arragon :

> Thank you for your reply.
> 
> I’ve tried the check without the ip adress option but it makes no difference.
> 
> Any other ideas?
> 
> Thanks.
> 
> 
> On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:
> 
>> You said u are using it like so:
>> 
>>Check:
>>/usr/local/nagios/libexec/check_http -I  -u http:// -w1 
>> -c2
>> 
>> Maybe drop the IP address?  I dunno, maybe cuz you have both IP and the url 
>> its causing problems. Maybe its replying on the IP, but not on the URL your 
>> providing.  You prob only need one or the other if im not mistaken
>> 
>> Cheers!
>> 
>> 
>> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon  
>> wrote:
>>> Hello,
>>> 
>>> Does anyone know why it gives me a 200 back?
>>> 
>>> If you need more info, I will gladly provide it ;-)
>>> 
>>> Thank you.
>>> 
>>> Regards,
>>> 
>>> Jaap
>>> 
>>> 
>>> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
>>> 
>>> > Hello,
>>> >
>>> > I’m trying to use the check_http plugin to verify if one of our website is
>>> > available.
>>> >
>>> > When I check our website it gives me a 200 OK status code back even when 
>>> > the
>>> > website isn’t available en the URL gives me a 503 status code through the
>>> > browser.
>>> >
>>> > After some searching I came across the post below:
>>> >
>>> > http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
>>> >
>>> > This states that there is a bug in check_http. The only thing is that the 
>>> > post
>>> > is from 2003 so I expect that the necessary changes are already in the new
>>> > release.
>>> >
>>> > Things I’ve tried:
>>> >
>>> > - recompiled the latest version of the check_http plugin but the necessary
>>> > changes seems to be integrated there already.
>>> > - updated the plugins package to the latest version for our release
>>> >
>>> > Check:
>>> > /usr/local/nagios/libexec/check_http -I  -u http:// -w1 
>>> > -c2
>>> >
>>> > Packages:
>>> >
>>> > ii nagios-images 0.5
>>> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
>>> > ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
>>> > ii nagios-plugins 1.4.14-1ubuntu1
>>> > ii nagios-plugins-basic 1.4.14-1ubuntu1
>>> > ii nagios-plugins-standard 1.4.14-1ubuntu1
>>> > ii nagios3 3.2.0-4ubuntu2.2
>>> > ii nagios3-cgi 3.2.0-4ubuntu2.2
>>> > ii nagios3-common 3.2.0-4ubuntu2.2
>>> > ii nagios3-core 3.2.0-4ubuntu2.2
>>> > ii nagiosgrapher 1.7.1-1
>>> >
>>> > Does anyone know why it gives me a status 200 OK back? At the moment I 
>>> > can't
>>> > rely on my Nagios checks..
>>> >
>>> > Thank you in advance
>>> >
>>> > Regards
>>> > Jaap
>>> 
>>> 
>>> 
>>> --
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> ___
>>> 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
>> 
>> 
> --
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov___
> Nagios-users mailing list
> Nagios-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/n

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Jaap van Arragon

Thank you for your reply.

I¹ve tried the check without the ip adress option but it makes no
difference.

Any other ideas?

Thanks.


On 11/19/12 2:29 PM, "Ryan Edwards"  wrote:

> You said u are using it like so:
> 
>    Check:
>    /usr/local/nagios/libexec/check_http -I  -u http:// -w1
> -c2
> 
> Maybe drop the IP address?  I dunno, maybe cuz you have both IP and the url
> its causing problems. Maybe its replying on the IP, but not on the URL your
> providing.  You prob only need one or the other if im not mistaken
> 
> Cheers!
> 
> 
> On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon 
> wrote:
>> Hello,
>> 
>> Does anyone know why it gives me a 200 back?
>> 
>> If you need more info, I will gladly provide it ;-)
>> 
>> Thank you.
>> 
>> Regards,
>> 
>> Jaap
>> 
>> 
>> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
>> 
>>> > Hello,
>>> >
>>> > I¹m trying to use the check_http plugin to verify if one of our website is
>>> > available.
>>> >
>>> > When I check our website it gives me a 200 OK status code back even when
>>> the
>>> > website isn¹t available en the URL gives me a 503 status code through the
>>> > browser.
>>> >
>>> > After some searching I came across the post below:
>>> >
>>> > http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
>>> >
>>> > This states that there is a bug in check_http. The only thing is that the
>>> post
>>> > is from 2003 so I expect that the necessary changes are already in the new
>>> > release.
>>> >
>>> > Things I¹ve tried:
>>> >
>>> > - recompiled the latest version of the check_http plugin but the necessary
>>> > changes seems to be integrated there already.
>>> > - updated the plugins package to the latest version for our release
>>> >
>>> > Check:
>>> > /usr/local/nagios/libexec/check_http -I  -u http:// -w1
>>> -c2
>>> >
>>> > Packages:
>>> >
>>> > ii nagios-images 0.5
>>> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
>>> > ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
>>> > ii nagios-plugins 1.4.14-1ubuntu1
>>> > ii nagios-plugins-basic 1.4.14-1ubuntu1
>>> > ii nagios-plugins-standard 1.4.14-1ubuntu1
>>> > ii nagios3 3.2.0-4ubuntu2.2
>>> > ii nagios3-cgi 3.2.0-4ubuntu2.2
>>> > ii nagios3-common 3.2.0-4ubuntu2.2
>>> > ii nagios3-core 3.2.0-4ubuntu2.2
>>> > ii nagiosgrapher 1.7.1-1
>>> >
>>> > Does anyone know why it gives me a status 200 OK back? At the moment I
>>> can't
>>> > rely on my Nagios checks..
>>> >
>>> > Thank you in advance
>>> >
>>> > Regards
>>> > Jaap
>> 
>> 
>> 
>> 
->>
-
>> Monitor your physical, virtual and cloud infrastructure from a single
>> web console. Get in-depth insight into apps, servers, databases, vmware,
>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>> Pricing starts from $795 for 25 servers or applications!
>> http://p.sf.net/sfu/zoho_dev2dev_nov
>> ___
>> 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
> 
> 

--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
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

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Ryan Edwards

You said u are using it like so:

   Check:
   /usr/local/nagios/libexec/check_http -I  -u http:// -w1
-c2

Maybe drop the IP address?  I dunno, maybe cuz you have both IP and the url
its causing problems. Maybe its replying on the IP, but not on the URL your
providing.  You prob only need one or the other if im not mistaken

Cheers!


On Mon, Nov 19, 2012 at 7:14 AM, Jaap van Arragon
wrote:

> Hello,
>
> Does anyone know why it gives me a 200 back?
>
> If you need more info, I will gladly provide it ;-)
>
> Thank you.
>
> Regards,
>
> Jaap
>
>
> On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:
>
> > Hello,
> >
> > I¹m trying to use the check_http plugin to verify if one of our website
> is
> > available.
> >
> > When I check our website it gives me a 200 OK status code back even when
> the
> > website isn¹t available en the URL gives me a 503 status code through the
> > browser.
> >
> > After some searching I came across the post below:
> >
> > http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
> >
> > This states that there is a bug in check_http. The only thing is that
> the post
> > is from 2003 so I expect that the necessary changes are already in the
> new
> > release.
> >
> > Things I¹ve tried:
> >
> > - recompiled the latest version of the check_http plugin but the
> necessary
> > changes seems to be integrated there already.
> > - updated the plugins package to the latest version for our release
> >
> > Check:
> > /usr/local/nagios/libexec/check_http -I  -u http://
> -w1 -c2
> >
> > Packages:
> >
> > ii nagios-images 0.5
> > ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
> > ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
> > ii nagios-plugins 1.4.14-1ubuntu1
> > ii nagios-plugins-basic 1.4.14-1ubuntu1
> > ii nagios-plugins-standard 1.4.14-1ubuntu1
> > ii nagios3 3.2.0-4ubuntu2.2
> > ii nagios3-cgi 3.2.0-4ubuntu2.2
> > ii nagios3-common 3.2.0-4ubuntu2.2
> > ii nagios3-core 3.2.0-4ubuntu2.2
> > ii nagiosgrapher 1.7.1-1
> >
> > Does anyone know why it gives me a status 200 OK back? At the moment I
> can't
> > rely on my Nagios checks..
> >
> > Thank you in advance
> >
> > Regards
> > Jaap
>
>
>
>
> --
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> ___
> 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
>



-- 
Christianity: The belief that some cosmic Jewish Zombie can make you live
forever if you symbolically eat his flesh and telepathically tell him that
you accept him as your master, so he can remove an evil force from your
soul that is present in humanity because a rib-woman was convinced by a
talking snake to eat from a magical tree.  Makes perfect sense!
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov___
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

Re: [Nagios-users] Check_http status 503 gives 200 OK

2012-11-19 Thread Jaap van Arragon

Hello,

Does anyone know why it gives me a 200 back?

If you need more info, I will gladly provide it ;-)

Thank you.

Regards,

Jaap 


On 11/16/12 11:54 AM, "Jaap van Arragon"  wrote:

> Hello,
> 
> I¹m trying to use the check_http plugin to verify if one of our website is
> available. 
> 
> When I check our website it gives me a 200 OK status code back even when the
> website isn¹t available en the URL gives me a 503 status code through the
> browser.
> 
> After some searching I came across the post below:
> 
> http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485
> 
> This states that there is a bug in check_http. The only thing is that the post
> is from 2003 so I expect that the necessary changes are already in the new
> release. 
> 
> Things I¹ve tried:
> 
> - recompiled the latest version of the check_http plugin but the necessary
> changes seems to be integrated there already.
> - updated the plugins package to the latest version for our release
> 
> Check:
> /usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2
> 
> Packages:
> 
> ii nagios-images 0.5
> ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
> ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
> ii nagios-plugins 1.4.14-1ubuntu1
> ii nagios-plugins-basic 1.4.14-1ubuntu1
> ii nagios-plugins-standard 1.4.14-1ubuntu1
> ii nagios3 3.2.0-4ubuntu2.2
> ii nagios3-cgi 3.2.0-4ubuntu2.2
> ii nagios3-common 3.2.0-4ubuntu2.2
> ii nagios3-core 3.2.0-4ubuntu2.2
> ii nagiosgrapher 1.7.1-1
> 
> Does anyone know why it gives me a status 200 OK back? At the moment I can't
> rely on my Nagios checks..
> 
> Thank you in advance
> 
> Regards
> Jaap



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
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] Check_http status 503 gives 200 OK

2012-11-16 Thread Jaap van Arragon

Hello,

I¹m trying to use the check_http plugin to verify if one of our website is
available. 

When I check our website it gives me a 200 OK status code back even when the
website isn¹t available en the URL gives me a 503 status code through the
browser.

After some searching I came across the post below:

http://permalink.gmane.org/gmane.network.nagios.plugins.devel/485

This states that there is a bug in check_http. The only thing is that the
post is from 2003 so I expect that the necessary changes are already in the
new release. 

Things I¹ve tried:

- recompiled the latest version of the check_http plugin but the necessary
changes seems to be integrated there already.
- updated the plugins package to the latest version for our release

Check:
/usr/local/nagios/libexec/check_http -I  -u http:// -w1 -c2

Packages:

ii nagios-images 0.5
ii nagios-nrpe-plugin 2.12-4ubuntu1.10.04.1
ii nagios-nrpe-server 2.12-4ubuntu1.10.04.1
ii nagios-plugins 1.4.14-1ubuntu1
ii nagios-plugins-basic 1.4.14-1ubuntu1
ii nagios-plugins-standard 1.4.14-1ubuntu1
ii nagios3 3.2.0-4ubuntu2.2
ii nagios3-cgi 3.2.0-4ubuntu2.2
ii nagios3-common 3.2.0-4ubuntu2.2
ii nagios3-core 3.2.0-4ubuntu2.2
ii nagiosgrapher 1.7.1-1

Does anyone know why it gives me a status 200 OK back? At the moment I can't
rely on my Nagios checks..

Thank you in advance

Regards
Jaap



--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
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

Re: [Nagios-users] check_http throwing 141 exit on ssl error

2012-09-14 Thread Mike Lindsey

On 9/14/12 11:25 AM, Justin T Pryzby wrote:
> This may be unrelated to the question of why it's exiting with a
> nonstandard, out of range exit status, but is port 83 really HTTP over
> SSL?  It seems as if the plugin sent an ssl initiation, and the remote
> side closed the connection (perhaps because it wasn't ssl?).
>
> Later, the plugin tried to gracefully end the ssl session, but the
> socket was already closed (ECONNRESET), resulting in EPIPE, which I
> think is expected.
When the remote device isn't in this current state that's causing it to 
close inbound connections immediately after the socket is opened, yes, 
that's an https port.

On 9/14/12 11:54 AM, Andreas Ericsson wrote:
> On 09/14/2012 08:09 PM, Mike Lindsey wrote:
>> I'm typically used to seeing this kind of error code for a missing
>> plugin, but I've got a device that is accepting tcp connections and then
>> due to a local misconfiguration, immediately closing them.
>>
>> But rather than a normal critical I'm getting:
>> """
>> (Return code of 141 is out of bounds)
>> """
>>
> SIGPIPE has sig id 13. When a program catches a signal, it returns
> the sigid as a negative number, but the field for the exit status
> is unsigned, so it gets translated to 128 + sigid instead.
>
> As I read it back, I realize that doesn't exactly make supersense
> to anyone not familiar with integer math as computers do it, but
> I can assure you that's the reason.
Yup, makes sense now, and if I'd bothered to hit the man page, I'd have 
groked that.  As it was I just assumed 141 was SIGPIPE, so almost there 
but with an invalid (and irrelevant assumption).

>> When run by hand I have:
>> """
>> root@ops-mon-nagios3 /usr/local/nagios/libexec $ ./check_http -H
>> device.domain.com -w "10" -c "20" -S -p "83" -f follow
>> CRITICAL - Cannot make SSL connection
>> root@ops-mon-nagios3 /usr/local/nagios/libexec $ echo $?
>> 141
>> """
>>
>> write(1, "CRITICAL - Cannot make SSL conne"..., 39) = 39
>> write(3, "\200w\1\3\1\0N\0\0\0
>> \0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 EPIPE
>> (Broken pipe)
>> --- SIGPIPE (Broken pipe) @ 0 (0) ---
>> +++ killed by SIGPIPE +++
>>
> And there's the SIGPIPE. Case closed.
>

Would it be appropriate for the check (and potentially any other 
nagios-plugins check that opens a socket) to trap SIGPIPE and return a 
normal valid critical?

As is, any http or https (or smtp or ldap, etc) check that's hitting a 
device behaving in this manner, is going to display a non-useful message 
in the Nagios UI, instead of the actual critical output. This is an 
error condition on a remote host, covered by what is normally valid 
working monitoring.  If this should be more cleanly caught by lower 
level parent dependency monitoring, how?  check_tcp returns 'ok' because 
the port opens.

If this is expected and desired behavior, should the output be updated 
to not include the misleading 'CRITICAL' prefix?

-- 
Mike Lindsey


--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
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

Re: [Nagios-users] check_http throwing 141 exit on ssl error

2012-09-14 Thread Andreas Ericsson

On 09/14/2012 08:09 PM, Mike Lindsey wrote:
> I'm typically used to seeing this kind of error code for a missing
> plugin, but I've got a device that is accepting tcp connections and then
> due to a local misconfiguration, immediately closing them.
> 
> But rather than a normal critical I'm getting:
> """
> (Return code of 141 is out of bounds)
> """
> 

SIGPIPE has sig id 13. When a program catches a signal, it returns
the sigid as a negative number, but the field for the exit status
is unsigned, so it gets translated to 128 + sigid instead.

As I read it back, I realize that doesn't exactly make supersense
to anyone not familiar with integer math as computers do it, but
I can assure you that's the reason.

When you get exit code 127 or 126 (below 128, but high), it's
because execve() has thrown an error and the shell is trying to
signal it the only way you can. It does that by returning 0x80
and subtracting the error number. 128 is 0x80 and would be a
negative number (which are reserved for signal-triggered exits),
so 127 is 0x80 - EPERM, which means the Nagios user lacks execute
permissions for the file. 126 is 0x80 - ENOENT, which means the
plugin doesn't exist in the path specified, or one of the elements
in the path leading to the plugin is missing. There are others too.
Check out "man 2 execve" for all the details.

> When run by hand I have:
> """
> root@ops-mon-nagios3 /usr/local/nagios/libexec $ ./check_http -H
> device.domain.com -w "10" -c "20" -S -p "83" -f follow
> CRITICAL - Cannot make SSL connection
> root@ops-mon-nagios3 /usr/local/nagios/libexec $ echo $?
> 141
> """
> 
> write(1, "CRITICAL - Cannot make SSL conne"..., 39) = 39
> write(3, "\200w\1\3\1\0N\0\0\0
> \0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 EPIPE
> (Broken pipe)
> --- SIGPIPE (Broken pipe) @ 0 (0) ---
> +++ killed by SIGPIPE +++
> 

And there's the SIGPIPE. Case closed.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
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

Re: [Nagios-users] check_http throwing 141 exit on ssl error

2012-09-14 Thread Justin T Pryzby

This may be unrelated to the question of why it's exiting with a
nonstandard, out of range exit status, but is port 83 really HTTP over
SSL?  It seems as if the plugin sent an ssl initiation, and the remote
side closed the connection (perhaps because it wasn't ssl?).

Later, the plugin tried to gracefully end the ssl session, but the
socket was already closed (ECONNRESET), resulting in EPIPE, which I
think is expected.

Justin

On Fri, Sep 14, 2012 at 11:09:48AM -0700, Mike Lindsey wrote:
> I'm typically used to seeing this kind of error code for a missing 
> plugin, but I've got a device that is accepting tcp connections and then 
> due to a local misconfiguration, immediately closing them.
> 
> But rather than a normal critical I'm getting:
> """
> (Return code of 141 is out of bounds)
> """
> 
> When run by hand I have:
> """
> root@ops-mon-nagios3 /usr/local/nagios/libexec $ ./check_http -H 
> device.domain.com -w "10" -c "20" -S -p "83" -f follow
> CRITICAL - Cannot make SSL connection
> root@ops-mon-nagios3 /usr/local/nagios/libexec $ echo $?
> 141
> """
> 
> Anyone seen this before?  Is this resolved in nagios-plugins > 1.4.15?
> 
> Here's some potentially useful, lightly filtered strace output, showing 
> it exiting on a SIGPIPE:
> """
> socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
> connect(3, {sa_family=AF_INET, sin_port=htons(83), 
> sin_addr=inet_addr("68.232.133.59")}, 16) = 0
> write(3, "\200w\1\3\1\0N\0\0\0 
> \0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 
> ECONNRESET (Connection reset by peer)
> fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
> = 0x2ab9e22dd000
> write(1, "CRITICAL - Cannot make SSL conne"..., 39) = 39
> write(3, "\200w\1\3\1\0N\0\0\0 
> \0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 EPIPE 
> (Broken pipe)
> --- SIGPIPE (Broken pipe) @ 0 (0) ---
> +++ killed by SIGPIPE +++

--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
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] check_http throwing 141 exit on ssl error

2012-09-14 Thread Mike Lindsey

I'm typically used to seeing this kind of error code for a missing 
plugin, but I've got a device that is accepting tcp connections and then 
due to a local misconfiguration, immediately closing them.

But rather than a normal critical I'm getting:
"""
(Return code of 141 is out of bounds)
"""

When run by hand I have:
"""
root@ops-mon-nagios3 /usr/local/nagios/libexec $ ./check_http -H 
device.domain.com -w "10" -c "20" -S -p "83" -f follow
CRITICAL - Cannot make SSL connection
root@ops-mon-nagios3 /usr/local/nagios/libexec $ echo $?
141
"""

Anyone seen this before?  Is this resolved in nagios-plugins > 1.4.15?

Here's some potentially useful, lightly filtered strace output, showing 
it exiting on a SIGPIPE:
"""
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(83), 
sin_addr=inet_addr("68.232.133.59")}, 16) = 0
write(3, "\200w\1\3\1\0N\0\0\0 
\0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 
ECONNRESET (Connection reset by peer)
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x2ab9e22dd000
write(1, "CRITICAL - Cannot make SSL conne"..., 39) = 39
write(3, "\200w\1\3\1\0N\0\0\0 
\0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 EPIPE 
(Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
+++ killed by SIGPIPE +++



-- Mike Lindsey

-- 
Mike Lindsey


--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
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

Re: [Nagios-users] check_http and self signed certs

2012-08-15 Thread Claudio Kuenzler

On Wed, Aug 15, 2012 at 5:03 PM,  wrote:

> Using -H url -I IP -s string -f follow and -p where applicable
> Timeout seems to be the issue yet the URLs are loading fine in less than a
> second, (-t is set to 45 seconds as well)
> Thanks
>

Generally you can use -S and -p 443 for SSL-sites. It doesn't matter if the
certificate is verified or self-signed.

./check_http -H www.example.com -p 443 -S
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http and self signed certs

2012-08-15 Thread masoud . tabrizi

Using -H url -I IP -s string -f follow and -p where applicable
Timeout seems to be the issue yet the URLs are loading fine in less than a 
second, (-t is set to 45 seconds as well)
Thanks  
-Original Message-
From: Claudio Kuenzler 
Date: Wed, 15 Aug 2012 16:29:19 
To: Nagios Users List
Reply-To: Nagios Users List 
Subject: Re: [Nagios-users] check_http and self signed certs

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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

Re: [Nagios-users] check_http and self signed certs

2012-08-15 Thread Claudio Kuenzler

This should work, also with self-signed certs. Doing this in my Nagios
config as well.
Whats the check_http command you're launching?
What's the error message?

On Wed, Aug 15, 2012 at 4:15 PM, Masoud Tabrizi wrote:

> All,
> We are using version 4.1.13 for the check_http for checking our URLs.
> it seems like the check_http is not able to get through the self signed
> certs we have installed;
> Are there any options or suggestions to get around this?
> thanks in advance
> Masoud Tabrizi
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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] check_http and self signed certs

2012-08-15 Thread Masoud Tabrizi

All,
We are using version 4.1.13 for the check_http for checking our URLs.
it seems like the check_http is not able to get through the self signed 
certs we have installed;
Are there any options or suggestions to get around this?
thanks in advance
Masoud Tabrizi



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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

Re: [Nagios-users] check_http

2012-06-15 Thread Leonardo Bacha Abrantes

Hey Travis!

thank you so much my friend!
it worked!!

On Thu, Jun 14, 2012 at 7:28 PM, Travis Runyard wrote:

> You can monitor the path of a website with the -u option. Here is an
> example:
> check_http -H mysite.com -u "/tux" -f follow
>
> You will probably want to use the "-f follow" option if your website uses
> any kind of redirection method.
>
> ;-)
> Travis Runyard
>
> On Wed, Jun 13, 2012 at 6:16 AM, Leonardo Bacha Abrantes <
> leona...@lbasolutions.com> wrote:
>
>> Hey people,
>>
>> I'm monitoring my site using the command line
>> /usr/local/nagios/libexec/check_http -w 4 -c 8 -H mysite.com. It's work
>> fine, however, I have some sites that has not a host added in my dns, and
>> to access it and use mysite.com/tux.
>>
>> and when I use heck_http -w 4 -c 8 -H mysite.com/tux, it fail.
>> How can I monitory it ?
>>
>> many thanks!
>>
>>
>>
>>
>> --
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> 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
>>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http

2012-06-14 Thread Travis Runyard

You can monitor the path of a website with the -u option. Here is an
example:
check_http -H mysite.com -u "/tux" -f follow

You will probably want to use the "-f follow" option if your website uses
any kind of redirection method.

;-)
Travis Runyard

On Wed, Jun 13, 2012 at 6:16 AM, Leonardo Bacha Abrantes <
leona...@lbasolutions.com> wrote:

> Hey people,
>
> I'm monitoring my site using the command line
> /usr/local/nagios/libexec/check_http -w 4 -c 8 -H mysite.com. It's work
> fine, however, I have some sites that has not a host added in my dns, and
> to access it and use mysite.com/tux.
>
> and when I use heck_http -w 4 -c 8 -H mysite.com/tux, it fail.
> How can I monitory it ?
>
> many thanks!
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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] check_http

2012-06-14 Thread Leonardo Bacha Abrantes

Hey people,

I'm monitoring my site using the command line
/usr/local/nagios/libexec/check_http -w 4 -c 8 -H mysite.com. It's work
fine, however, I have some sites that has not a host added in my dns, and
to access it and use mysite.com/tux.

and when I use heck_http -w 4 -c 8 -H mysite.com/tux, it fail.
How can I monitory it ?

many thanks!
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http fails for two Sprint sites

2012-05-16 Thread Frank Bulk - iName.com

FYI: Sprint did something this morning such that those sites are now
checking cleanly with check_http.

Frank


From: Frank Bulk [frnk...@iname.com]
Sent: Friday, February 24, 2012 8:27 AM
To: 'Paul Dubuc'; 'Nagios Users List'
Subject: RE: [Nagios-users] check_http fails for two Sprint sites

Yes, I did -- no go.  You can test it yourself -- there's nothing special
about where I'm testing it from. =)

It's clear that check_http is choking on it, and I suspect it's because it
redirects to a secure version of the site.

Frank

-Original Message-
From: Paul Dubuc [mailto:w...@paul.dubuc.org]
Sent: Friday, February 24, 2012 8:26 AM
To: frnk...@iname.com; Nagios Users List
Subject: Re: [Nagios-users] check_http fails for two Sprint sites

Frank Bulk wrote:
> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
> failed to pass check_http.  What's strange is that the v4 version of
> www.sprint.net also fails.
>
> I see that there are 302's (redirection) to the secure version of the
site,
> but using the '-f follow' command doesn't help, either.  It seems that if
> the site one being is redirected to is secure that the check command
fails.
>

Did you try any of the other options for -f, like '-f sticky' or '-f
stickyport'?



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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

Re: [Nagios-users] check_http script is not working

2012-05-08 Thread Claudio Kuenzler

Jeez. I should drink a coffee before responding... ouch.

The syntax is correct, as you see in my post I had a typo in the verisign
domain name.

# ./check_http -w 5 -c 10 --ssl -H www.verisign.com
HTTP OK: HTTP/1.1 200 OK - 42718 bytes in 0.830 second response time
|time=0.830120s;5.00;10.00;0.00 size=42718B;;;0

So it works. Sorry for false information.

Do as Bram suggested, try to "open" the website with lynx or curl.

Hello ,
>>
>> ** **
>>
>> I’m Sankar testing nagios scripts. I have tried to ping URL check from
>> check_http script from nagios.
>>
>> ** **
>>
>> http://nagiosplugins.org/man/check_http (URL) = Reference
>>
>> ** **
>>
>> Root# check_http -w 5 -c 10 --ssl -H www.verisign.com 
>>
>>  Name or service not known
>>
>> HTTP CRITICAL - Unable to open TCP socket
>>
>> ** **
>>
>> **
>>
> You're using a wrong order... See here the difference:
>
> # ./check_http -w 5 -c 10 --ssl -H www.verisisgn.com
>
> Name or service not known
> HTTP CRITICAL - Unable to open TCP socket
>
> # ./check_http -H www.verisign.com --ssl -w 5 -c 10
> HTTP OK: HTTP/1.1 200 OK - 42718 bytes in 0.822 second response time
> |time=0.821882s;5.00;10.00;0.00 size=42718B;;;0
>
> I know the way you tried it is shown in the --help but it obviously
> doesn't work.
>
>
>
>> **
>>
>> Please help us in checking whether URL is up or down. How efficiently
>> this script can be used ?
>>
>> Is there any way to find out URL availability ? with port ? or ping ? can
>> we pass proxy ?
>>
>> ** **
>>
>> Thanks in advance.
>>
>> ** **
>>
>> Best regards, Sankar 
>>
>>
>> --
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> 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
>>
>
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http script is not working

2012-05-08 Thread Claudio Kuenzler

>
> Hello ,
>
> ** **
>
> I’m Sankar testing nagios scripts. I have tried to ping URL check from
> check_http script from nagios.
>
> ** **
>
> http://nagiosplugins.org/man/check_http (URL) = Reference
>
> ** **
>
> Root# check_http -w 5 -c 10 --ssl -H www.verisign.com 
>
>  Name or service not known
>
> HTTP CRITICAL - Unable to open TCP socket
>
> ** **
>
> **
>
You're using a wrong order... See here the difference:

# ./check_http -w 5 -c 10 --ssl -H www.verisisgn.com
Name or service not known
HTTP CRITICAL - Unable to open TCP socket

# ./check_http -H www.verisign.com --ssl -w 5 -c 10
HTTP OK: HTTP/1.1 200 OK - 42718 bytes in 0.822 second response time
|time=0.821882s;5.00;10.00;0.00 size=42718B;;;0

I know the way you tried it is shown in the --help but it obviously doesn't
work.



> **
>
> Please help us in checking whether URL is up or down. How efficiently this
> script can be used ?
>
> Is there any way to find out URL availability ? with port ? or ping ? can
> we pass proxy ?
>
> ** **
>
> Thanks in advance.
>
> ** **
>
> Best regards, Sankar 
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> 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
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http script is not working

2012-05-08 Thread Bram Gillemon

Hi,

Can you visit the url using lynx / curl / ..., your syntax is correct. So it 
looks like another problem.

Kr,
Bram

On 08 May 2012, at 09:01, Sankar, Bheemarasetty wrote:

> Hello ,
>  
> I’m Sankar testing nagios scripts. I have tried to ping URL check from 
> check_http script from nagios.
>  
> http://nagiosplugins.org/man/check_http (URL) = Reference
>  
> Root# check_http -w 5 -c 10 --ssl -H www.verisign.com
>  Name or service not known
> HTTP CRITICAL - Unable to open TCP socket
>  
>  
> Please help us in checking whether URL is up or down. How efficiently this 
> script can be used ?
> Is there any way to find out URL availability ? with port ? or ping ? can we 
> pass proxy ?
>  
> Thanks in advance.
>  
> Best regards, Sankar
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. 
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
> 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

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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] check_http script is not working

2012-05-08 Thread Sankar, Bheemarasetty

Hello ,

I'm Sankar testing nagios scripts. I have tried to ping URL check from 
check_http script from nagios.

http://nagiosplugins.org/man/check_http (URL) = Reference

Root# check_http -w 5 -c 10 --ssl -H www.verisign.com
 Name or service not known
HTTP CRITICAL - Unable to open TCP socket


Please help us in checking whether URL is up or down. How efficiently this 
script can be used ?
Is there any way to find out URL availability ? with port ? or ping ? can we 
pass proxy ?

Thanks in advance.

Best regards, Sankar
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
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

Re: [Nagios-users] check_http issue

2012-03-12 Thread Jeffrey Watts

I wonder if it's an epoch thing...   Are all of the certs that are failing
ones in which the expiry year is 2038 or greater?

Jeffrey.

On Mon, Mar 12, 2012 at 4:04 AM, Sunny Jaisinghani <
sunny_jaisingh...@symantec.com> wrote:

> Hello,
>
> I am using the check_http plugin for checking the SSL cert expiry. Even if
> the cert is not due to expire very soon, the plugin reports as CRITICAL.
> I have few more certs for which the plugin reports correct status.
>
> What could be going wrong over here. ??
>
> BAD
>
> # /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8001 -w 30
> -c 30 -C 30
> CRITICAL - Certificate expired on 02/17/2062 22:44.
>
> # openssl x509 -in abc.example.com.crt -noout –enddate
> notAfter=Feb 17 22:57:24 2062 GMT
>
> GOOD
>
> # /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8000 -w 30
> -c 30 -C 30
> OK - Certificate will expire on 02/09/2013 23:59.
>
> # openssl x509 -in xyz.example.com.crt -noout –enddate
> notAfter=Feb 10 23:59:59 2013 GMT
>
>
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2___
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

Re: [Nagios-users] check_http issue

2012-03-12 Thread Claudio Kuenzler

I know this doesn't answer your questions, but did you give the
check_ssl_cert plugin a try?

https://svn.id.ethz.ch/nagios_plugins/check_ssl_cert/check_ssl_cert

I'm using this plugin to check ssl certificates, not only on http but also
tls

On Mon, Mar 12, 2012 at 10:04 AM, Sunny Jaisinghani <
sunny_jaisingh...@symantec.com> wrote:

> Hello,
>
> I am using the check_http plugin for checking the SSL cert expiry. Even if
> the cert is not due to expire very soon, the plugin reports as CRITICAL.
> I have few more certs for which the plugin reports correct status.
>
> What could be going wrong over here. ??
>
> BAD
>
> # /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8001 -w 30
> -c 30 -C 30
> CRITICAL - Certificate expired on 02/17/2062 22:44.
>
> # openssl x509 -in abc.example.com.crt -noout –enddate
> notAfter=Feb 17 22:57:24 2062 GMT
>
> GOOD
>
> # /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8000 -w 30
> -c 30 -C 30
> OK - Certificate will expire on 02/09/2013 23:59.
>
> # openssl x509 -in xyz.example.com.crt -noout –enddate
> notAfter=Feb 10 23:59:59 2013 GMT
>
>
> Thanks
> Sunny
>
>
>
>
>
>
>
>
> --
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> ___
> 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
>
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2___
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] check_http issue

2012-03-12 Thread Sunny Jaisinghani

Hello,

I am using the check_http plugin for checking the SSL cert expiry. Even if the 
cert is not due to expire very soon, the plugin reports as CRITICAL.
I have few more certs for which the plugin reports correct status.

What could be going wrong over here. ??

BAD

# /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8001 -w 30 -c 30 
-C 30
CRITICAL - Certificate expired on 02/17/2062 22:44.

# openssl x509 -in abc.example.com.crt -noout –enddate
notAfter=Feb 17 22:57:24 2062 GMT

GOOD

# /usr/lib/nagios/plugins/check_http --ssl -H XX.XX.XX.XX  -p 8000 -w 30 -c 30 
-C 30
OK - Certificate will expire on 02/09/2013 23:59.

# openssl x509 -in xyz.example.com.crt -noout –enddate
notAfter=Feb 10 23:59:59 2013 GMT


Thanks
Sunny






--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2___
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

Re: [Nagios-users] check_http 1.4.15

2012-03-01 Thread Claudio Kuenzler

Scott,

Did you read my answer at all (Feb 27th)? You're looking for something that
hasn't been implemented.

Here again the post:

The link you posted is a user-contributed patch for check_http, posted on
the tracker on Jan 3rd 2012.
Nagios Plugins v. 1.4.15 were released in July 2010 so you can be sure that
this patch has not made it into 1.4.15.

You have two options:
- Wait and hope that this patch will make it sometime into the branch and
next version release (good luck with that)
- Re-compile check_http from source with the patch yourself

-
ck

On Wed, Feb 29, 2012 at 11:38 PM, Werner, Robert
wrote:

>  Can you include the command line you are using and what you expect it to
> do? 
>
> ** **
>
> --
>
> Robert G. Werner
>
> Oracle Apps Systems Administrator
>
> rwer...@pomwonderful.com
>
> 559.521.5089
>
> ** **
>
> *From:* Scott Ford [mailto:sm_f...@yahoo.com]
> *Sent:* Tuesday, February 28, 2012 12:03 PM
> *To:* nagios-users@lists.sourceforge.net
> *Subject:* [Nagios-users] check_http 1.4.15
>
> ** **
>
> All,
>
>
> I installed Nagios Plugins v.1.4.15 after reading a post on Sourceforge
> that showed the latest version of check_http included an option for regular
> expression searches in the header of the file.  That option does not seem
> to be available.  Can anyone shed some light on this?  This is the post I
> read...
>
> ** **
>
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=3469275&group_id=29880&atid=397599
> 
>
> ** **
>
> Thank you in advance,
>
> ** **
>
> Scott
>
> ** **
>
> 
>
> ** **
>
> [sforddev plugins]# ./check_http --help
> check_http v1.4.15 (nagios-plugins 1.4.15)
> Copyright (c) 1999 Ethan Galstad 
> Copyright (c) 1999-2008 Nagios Plugin Development Team
> 
>
> This plugin tests the HTTP service on the specified host. It can test
> normal (http) and secure (https) servers, follow redirects, search for
> strings and regular expressions, check connection times, and report on
> certificate expiration times.
>
>
> Usage:
>  check_http -H  | -I  [-u ] [-p ]
>[-w ] [-c ] [-t ] [-L] [-a auth]
>[-b proxy_auth] [-f ]
>[-e ] [-s string] [-l] [-r  | -R  regex>]
>[-P string] [-m :] [-4|-6] [-N] [-M ]
>[-A string] [-k string] [-S] [--sni] [-C ] [-T ]
>[-j method]
> NOTE: One or both of -H and -I must be specified
>
> Options:
>  -h, --help
> Print detailed help screen
>  -V, --version
> Print version information
>  -H, --hostname=ADDRESS
> Host name argument for servers using host headers (virtual host)
> Append a port to include it in the header (eg: example.com:5000)
>  -I, --IP-address=ADDRESS
> IP address or name (use numeric address if possible to bypass DNS
> lookup).
>  -p, --port=INTEGER
> Port number (default: 80)
>  -4, --use-ipv4
> Use IPv4 connection
>  -6, --use-ipv6
> Use IPv6 connection
>  -e, --expect=STRING
> Comma-delimited list of strings, at least one of them is expected in
> the first (status) line of the server response (default: HTTP/1.)
> If specified skips all other status line logic (ex: 3xx, 4xx, 5xx
> processing)
>  -s, --string=STRING
> String to expect in the content
>  -u, --url=PATH
> URL to GET or POST (default: /)
>  -P, --post=STRING
> URL encoded http POST data
>  -j, --method=STRING  (for example: HEAD, OPTIONS, TRACE, PUT, DELETE)
> Set HTTP method.
>  -N, --no-body
> Don't wait for document body: stop reading after headers.
> (Note that this still does an HTTP GET or POST, not a HEAD.)
>  -M, --max-age=SECONDS
> Warn if document is more than SECONDS old. the number can also be of
> the form "10m" for minutes, "10h" for hours, or "10d" for days.
>  -T, --content-type=STRING
> specify Content-Type header media type when POSTing
>
>  -l, --linespan
> Allow regex to span newlines (must precede -r or -R)
>  -r, --regex, --ereg=STRING
> Search page for regex STRING
>  -R, --eregi=STRING
> Search page for case-insensitive regex STRING
>  --invert-regex
> Return CRITICAL if found, OK if not
>
>  -a, --authorization=AUTH_PAIR
> Username:password on sites with basic authentication
>  -b, --proxy-authorization=AUTH_PAIR
>  Username:password on proxy-servers with basic authentication
>  -A, --useragent=STRING
> String to be sent in http header as "User Agent"
>  -k, --header=STRING
>  Any other tags to be sent in http header. Use multiple times for
> additional headers
>

Re: [Nagios-users] check_http 1.4.15

2012-02-29 Thread Werner, Robert

Can you include the command line you are using and what you expect it to do?

--
Robert G. Werner
Oracle Apps Systems Administrator
rwer...@pomwonderful.com
559.521.5089

From: Scott Ford [mailto:sm_f...@yahoo.com]
Sent: Tuesday, February 28, 2012 12:03 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_http 1.4.15

All,

I installed Nagios Plugins v.1.4.15 after reading a post on Sourceforge that 
showed the latest version of check_http included an option for regular 
expression searches in the header of the file.  That option does not seem to be 
available.  Can anyone shed some light on this?  This is the post I read...

http://sourceforge.net/tracker/index.php?func=detail&aid=3469275&group_id=29880&atid=397599

Thank you in advance,

Scott



[sforddev plugins]# ./check_http --help
check_http v1.4.15 (nagios-plugins 1.4.15)
Copyright (c) 1999 Ethan Galstad mailto:nag...@nagios.org>>
Copyright (c) 1999-2008 Nagios Plugin Development Team

mailto:nagiosplug-de...@lists.sourceforge.net>>

This plugin tests the HTTP service on the specified host. It can test
normal (http) and secure (https) servers, follow redirects, search for
strings and regular expressions, check connection times, and report on
certificate expiration times.


Usage:
 check_http -H  | -I  [-u ] [-p ]
   [-w ] [-c ] [-t ] [-L] [-a auth]
   [-b proxy_auth] [-f ]
   [-e ] [-s string] [-l] [-r  | -R ]
   [-P string] [-m :] [-4|-6] [-N] [-M ]
   [-A string] [-k string] [-S] [--sni] [-C ] [-T ]
   [-j method]
NOTE: One or both of -H and -I must be specified

Options:
 -h, --help
Print detailed help screen
 -V, --version
Print version information
 -H, --hostname=ADDRESS
Host name argument for servers using host headers (virtual host)
Append a port to include it in the header (eg: example.com:5000)
 -I, --IP-address=ADDRESS
IP address or name (use numeric address if possible to bypass DNS lookup).
 -p, --port=INTEGER
Port number (default: 80)
 -4, --use-ipv4
Use IPv4 connection
 -6, --use-ipv6
Use IPv6 connection
 -e, --expect=STRING
Comma-delimited list of strings, at least one of them is expected in
the first (status) line of the server response (default: HTTP/1.)
If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
processing)
 -s, --string=STRING
String to expect in the content
 -u, --url=PATH
URL to GET or POST (default: /)
 -P, --post=STRING
URL encoded http POST data
 -j, --method=STRING  (for example: HEAD, OPTIONS, TRACE, PUT, DELETE)
Set HTTP method.
 -N, --no-body
Don't wait for document body: stop reading after headers.
(Note that this still does an HTTP GET or POST, not a HEAD.)
 -M, --max-age=SECONDS
Warn if document is more than SECONDS old. the number can also be of
the form "10m" for minutes, "10h" for hours, or "10d" for days.
 -T, --content-type=STRING
specify Content-Type header media type when POSTing

 -l, --linespan
Allow regex to span newlines (must precede -r or -R)
 -r, --regex, --ereg=STRING
Search page for regex STRING
 -R, --eregi=STRING
Search page for case-insensitive regex STRING
 --invert-regex
Return CRITICAL if found, OK if not

 -a, --authorization=AUTH_PAIR
Username:password on sites with basic authentication
 -b, --proxy-authorization=AUTH_PAIR
 Username:password on proxy-servers with basic authentication
 -A, --useragent=STRING
String to be sent in http header as "User Agent"
 -k, --header=STRING
 Any other tags to be sent in http header. Use multiple times for 
additional headers
 -L, --link
Wrap output in HTML link (obsoleted by urlize)
 -f, --onredirect=
How to handle redirected pages. sticky is like follow but stick to the
specified IP address. stickyport also ensure post stays the same.
 -m, --pagesize=INTEGER<:INTEGER>
Minimum page size required (bytes) : Maximum page size required (bytes)
 -w, --warning=DOUBLE
Response time to result in warning status (seconds)
 -c, --critical=DOUBLE
Response time to result in critical status (seconds)
 -t, --timeout=INTEGER
Seconds before connection times out (default: 10)
 -v, --verbose
Show details for command-line debugging (Nagios may truncate output)

Notes:
 This plugin will attempt to open an HTTP connection with the host.
 Successful connects return STATE_OK, refusals and timeouts return 
STATE_CRITICAL
 other errors return STATE_UNKNOWN.  Successful connects, but incorrect reponse
 messages from the host result in STATE_WARNING return values.  If you are
 checking a virtual server that uses 'host headers' you must supply the FQDN
 (fully qualified domain name) as the [host_name] argument.

Send email to 
nagios-users@lists.sourceforge.net<mailto:nagios-users@lists.sourceforge.net> 
if you have questions
regarding use of this software. To submit patches or su

[Nagios-users] check_http 1.4.15

2012-02-29 Thread Scott Ford

All,


I installed Nagios Plugins v.1.4.15 after reading a post on Sourceforge 
that showed the latest version of check_http included an option for 
regular expression searches in the header of the file.  That option does
 not seem to be available.  Can anyone shed some light on this?  This is
 the post I read...

http://sourceforge.net/tracker/index.php?func=detail&aid=3469275&group_id=29880&atid=397599

Thank you in advance,

Scott



[sforddev plugins]# ./check_http --help
check_http v1.4.15 (nagios-plugins 1.4.15)
Copyright (c) 1999 Ethan Galstad 
Copyright (c) 1999-2008 Nagios Plugin Development Team
    

This plugin tests the HTTP service on the specified host. It can test
normal (http) and secure (https) servers, follow redirects, search for
strings and regular expressions, check connection times, and report on
certificate expiration times.


Usage:
 check_http -H  | -I  [-u ] [-p ]
  
 [-w ] [-c ] [-t ] [-L] [-a auth]
   [-b proxy_auth] [-f ]
   [-e ] [-s string] [-l] [-r  | -R ]
   [-P string] [-m :] [-4|-6] [-N] [-M ]
   [-A string] [-k string] [-S] [--sni] [-C ] [-T ]
   [-j method]
NOTE: One or both of -H and -I must be specified

Options:
 -h, --help
    Print detailed help screen
 -V, --version
    Print version information
 -H, --hostname=ADDRESS
    Host name argument for servers using host headers (virtual
 host)
    Append a port to include it in the header (eg: example.com:5000)
 -I, --IP-address=ADDRESS
    IP address or name (use numeric address if possible to bypass DNS lookup).
 -p, --port=INTEGER
    Port number (default: 80)
 -4, --use-ipv4
    Use IPv4 connection
 -6, --use-ipv6
    Use IPv6 connection
 -e, --expect=STRING
    Comma-delimited list of strings, at least one of them is expected in
    the first (status) line of the server response (default: HTTP/1.)
    If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
processing)
 -s, --string=STRING
    String to expect in the content
 -u, --url=PATH
    URL to GET or POST (default: /)
 -P, --post=STRING
    URL encoded http
 POST data
 -j, --method=STRING  (for example: HEAD, OPTIONS, TRACE, PUT, DELETE)
    Set HTTP method.
 -N, --no-body
    Don't wait for document body: stop reading after headers.
    (Note that this still does an HTTP GET or POST, not a HEAD.)
 -M, --max-age=SECONDS
    Warn if document is more than SECONDS old. the number can also be of
    the form "10m" for minutes, "10h" for hours, or "10d" for days.
 -T, --content-type=STRING
    specify Content-Type header media type when POSTing

 -l, --linespan
    Allow regex to span newlines (must precede -r or -R)
 -r, --regex, --ereg=STRING
    Search page for regex STRING
 -R, --eregi=STRING
    Search page for case-insensitive regex STRING
 --invert-regex
   
 Return CRITICAL if found, OK if not

 -a, --authorization=AUTH_PAIR
    Username:password on sites with basic authentication
 -b, --proxy-authorization=AUTH_PAIR
 Username:password on proxy-servers with basic authentication
 -A, --useragent=STRING
    String to be sent in http header as "User Agent"
 -k, --header=STRING
 Any other tags to be sent in http header. Use multiple times for 
additional headers
 -L, --link
    Wrap output in HTML link (obsoleted by urlize)
 -f, --onredirect=
    How to handle redirected pages. sticky is like follow but stick to the
    specified IP address. stickyport also ensure post stays the same.
 -m, --pagesize=INTEGER<:INTEGER>
    Minimum page
 size required (bytes) : Maximum page size required (bytes)
 -w, --warning=DOUBLE
    Response time to result in warning status (seconds)
 -c, --critical=DOUBLE
    Response time to result in critical status (seconds)
 -t, --timeout=INTEGER
    Seconds before connection times out (default: 10)
 -v, --verbose
    Show details for command-line debugging (Nagios may truncate output)

Notes:
 This plugin will attempt to open an HTTP connection with the host.
 Successful connects return STATE_OK, refusals and timeouts return 
STATE_CRITICAL
 other errors return STATE_UNKNOWN.  Successful connects, but incorrect reponse
 messages from the host result in STATE_WARNING return values.  If you are
 checking a virtual server that uses 'host headers' you must supply the FQDN
 (fully qualified domain
 name) as the [host_name] argument.

Send email to nagios-users@lists.sourceforge.net if you have questions
regarding use of this software. To submit patches or suggest improvements,
send email to nagiosplug-de...@lists.sourceforge.net--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/n

Re: [Nagios-users] check_http 1.4.15

2012-02-27 Thread Claudio Kuenzler

Hi Scott,

The link you posted is a user-contributed patch for check_http, posted on
the tracker on Jan 3rd 2012.
Nagios Plugins v. 1.4.15 were released in July 2010 so you can be sure that
this patch has not made it into 1.4.15.

You have two options:
- Wait and hope that this patch will make it sometime into the branch and
next version release (good luck with that)
- Re-compile check_http from source with the patch yourself

On Thu, Feb 23, 2012 at 11:24 PM, Scott Ford  wrote:

> All,
>
> I installed Nagios Plugins v.1.4.15 after reading a post on Sourceforge
> that showed the latest version of check_http included an option for regular
> expression searches in the header of the file.  That option does not seem
> to be available.  Can anyone shed some light on this?  This is the post I
> read...
>
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=3469275&group_id=29880&atid=397599
>
> Thank you in advance,
>
> Scott
>
> 
>
> [sforddev plugins]# ./check_http --help
> check_http v1.4.15 (nagios-plugins 1.4.15)
> Copyright (c) 1999 Ethan Galstad 
> Copyright (c) 1999-2008 Nagios Plugin Development Team
> 
>
> This plugin tests the HTTP service on the specified host. It can test
> normal (http) and secure (https) servers, follow redirects, search for
> strings and regular expressions, check connection times, and report on
> certificate expiration times.
>
>
> Usage:
>  check_http -H  | -I  [-u ] [-p ]
>[-w ] [-c ] [-t ] [-L] [-a auth]
>[-b proxy_auth] [-f ]
>[-e ] [-s string] [-l] [-r  | -R  regex>]
>[-P string] [-m :] [-4|-6] [-N] [-M ]
>[-A string] [-k string] [-S] [--sni] [-C ] [-T ]
>[-j method]
> NOTE: One or both of -H and -I must be specified
>
> Options:
>  -h, --help
> Print detailed help screen
>  -V, --version
> Print version information
>  -H, --hostname=ADDRESS
> Host name argument for servers using host headers (virtual host)
> Append a port to include it in the header (eg: example.com:5000)
>  -I, --IP-address=ADDRESS
> IP address or name (use numeric address if possible to bypass DNS
> lookup).
>  -p, --port=INTEGER
> Port number (default: 80)
>  -4, --use-ipv4
> Use IPv4 connection
>  -6, --use-ipv6
> Use IPv6 connection
>  -e, --expect=STRING
> Comma-delimited list of strings, at least one of them is expected in
> the first (status) line of the server response (default: HTTP/1.)
> If specified skips all other status line logic (ex: 3xx, 4xx, 5xx
> processing)
>  -s, --string=STRING
> String to expect in the content
>  -u, --url=PATH
> URL to GET or POST (default: /)
>  -P, --post=STRING
> URL encoded http POST data
>  -j, --method=STRING  (for example: HEAD, OPTIONS, TRACE, PUT, DELETE)
> Set HTTP method.
>  -N, --no-body
> Don't wait for document body: stop reading after headers.
> (Note that this still does an HTTP GET or POST, not a HEAD.)
>  -M, --max-age=SECONDS
> Warn if document is more than SECONDS old. the number can also be of
> the form "10m" for minutes, "10h" for hours, or "10d" for days.
>  -T, --content-type=STRING
> specify Content-Type header media type when POSTing
>
>  -l, --linespan
> Allow regex to span newlines (must precede -r or -R)
>  -r, --regex, --ereg=STRING
> Search page for regex STRING
>  -R, --eregi=STRING
> Search page for case-insensitive regex STRING
>  --invert-regex
> Return CRITICAL if found, OK if not
>
>  -a, --authorization=AUTH_PAIR
> Username:password on sites with basic authentication
>  -b, --proxy-authorization=AUTH_PAIR
>  Username:password on proxy-servers with basic authentication
>  -A, --useragent=STRING
> String to be sent in http header as "User Agent"
>  -k, --header=STRING
>  Any other tags to be sent in http header. Use multiple times for
> additional headers
>  -L, --link
> Wrap output in HTML link (obsoleted by urlize)
>  -f, --onredirect=
> How to handle redirected pages. sticky is like follow but stick to the
> specified IP address. stickyport also ensure post stays the same.
>  -m, --pagesize=INTEGER<:INTEGER>
> Minimum page size required (bytes) : Maximum page size required (bytes)
>  -w, --warning=DOUBLE
> Response time to result in warning status (seconds)
>  -c, --critical=DOUBLE
> Response time to result in critical status (seconds)
>  -t, --timeout=INTEGER
> Seconds before connection times out (default: 10)
>  -v, --verbose
> Show details for command-line debugging (Nagios may truncate output)
>
> Notes:
>  This plugin will attempt to open an HTTP connection with the host.
>  Successful connects return STATE_OK, refusals and timeouts return
> STATE_CRITICAL
>  other errors return STATE_UNKNOWN.  Successful connects, but incorrect
> reponse
>  messages from the host result in STATE_WARNING return values.  If you are
>  checking a virtual server that uses 'host headers' you must supply the
> FQDN
>  (fully qualified doma

[Nagios-users] check_http 1.4.15

2012-02-24 Thread Scott Ford

All,

I installed Nagios Plugins v.1.4.15 after reading a post on Sourceforge 
that showed the latest version of check_http included an option for 
regular expression searches in the header of the file.  That option does
 not seem to be available.  Can anyone shed some light on this?  This is
 the post I read...

http://sourceforge.net/tracker/index.php?func=detail&aid=3469275&group_id=29880&atid=397599

Thank you in advance,

Scott



[sforddev plugins]# ./check_http --help
check_http v1.4.15 (nagios-plugins 1.4.15)
Copyright (c) 1999 Ethan Galstad 
Copyright (c) 1999-2008 Nagios Plugin Development Team
    

This plugin tests the HTTP service on the specified host. It can test
normal (http) and secure (https) servers, follow redirects, search for
strings and regular expressions, check connection times, and report on
certificate expiration times.


Usage:
 check_http -H  | -I  [-u ] [-p ]
   [-w ] [-c ] [-t ] [-L] [-a auth]
   [-b proxy_auth] [-f ]
   [-e ] [-s string] [-l] [-r  | -R ]
   [-P string] [-m :] [-4|-6] [-N] [-M ]
   [-A string] [-k string] [-S] [--sni] [-C ] [-T ]
   [-j method]
NOTE: One or both of -H and -I must be specified

Options:
 -h, --help
    Print detailed help screen
 -V, --version
    Print version information
 -H, --hostname=ADDRESS
    Host name argument for servers using host headers (virtual host)
    Append a port to include it in the header (eg: example.com:5000)
 -I, --IP-address=ADDRESS
    IP address or name (use numeric address if possible to bypass DNS lookup).
 -p, --port=INTEGER
    Port number (default: 80)
 -4, --use-ipv4
    Use IPv4 connection
 -6, --use-ipv6
    Use IPv6 connection
 -e, --expect=STRING
    Comma-delimited list of strings, at least one of them is expected in
    the first (status) line of the server response (default: HTTP/1.)
    If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
processing)
 -s, --string=STRING
    String to expect in the content
 -u, --url=PATH
    URL to GET or POST (default: /)
 -P, --post=STRING
    URL encoded http POST data
 -j, --method=STRING  (for example: HEAD, OPTIONS, TRACE, PUT, DELETE)
    Set HTTP method.
 -N, --no-body
    Don't wait for document body: stop reading after headers.
    (Note that this still does an HTTP GET or POST, not a HEAD.)
 -M, --max-age=SECONDS
    Warn if document is more than SECONDS old. the number can also be of
    the form "10m" for minutes, "10h" for hours, or "10d" for days.
 -T, --content-type=STRING
    specify Content-Type header media type when POSTing

 -l, --linespan
    Allow regex to span newlines (must precede -r or -R)
 -r, --regex, --ereg=STRING
    Search page for regex STRING
 -R, --eregi=STRING
    Search page for case-insensitive regex STRING
 --invert-regex
    Return CRITICAL if found, OK if not

 -a, --authorization=AUTH_PAIR
    Username:password on sites with basic authentication
 -b, --proxy-authorization=AUTH_PAIR
 Username:password on proxy-servers with basic authentication
 -A, --useragent=STRING
    String to be sent in http header as "User Agent"
 -k, --header=STRING
 Any other tags to be sent in http header. Use multiple times for 
additional headers
 -L, --link
    Wrap output in HTML link (obsoleted by urlize)
 -f, --onredirect=
    How to handle redirected pages. sticky is like follow but stick to the
    specified IP address. stickyport also ensure post stays the same.
 -m, --pagesize=INTEGER<:INTEGER>
    Minimum page size required (bytes) : Maximum page size required (bytes)
 -w, --warning=DOUBLE
    Response time to result in warning status (seconds)
 -c, --critical=DOUBLE
    Response time to result in critical status (seconds)
 -t, --timeout=INTEGER
    Seconds before connection times out (default: 10)
 -v, --verbose
    Show details for command-line debugging (Nagios may truncate output)

Notes:
 This plugin will attempt to open an HTTP connection with the host.
 Successful connects return STATE_OK, refusals and timeouts return 
STATE_CRITICAL
 other errors return STATE_UNKNOWN.  Successful connects, but incorrect reponse
 messages from the host result in STATE_WARNING return values.  If you are
 checking a virtual server that uses 'host headers' you must supply the FQDN
 (fully qualified domain name) as the [host_name] argument.

Send email to nagios-users@lists.sourceforge.net if you have questions
regarding use of this software. To submit patches or suggest improvements,
send email to nagiosplug-de...@lists.sourceforge.net--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-u

Re: [Nagios-users] check_http fails for two Sprint sites

2012-02-24 Thread Paul Dubuc

Frank Bulk wrote:
> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
> failed to pass check_http.  What's strange is that the v4 version of
> www.sprint.net also fails.
>
> I see that there are 302's (redirection) to the secure version of the site,
> but using the '-f follow' command doesn't help, either.  It seems that if
> the site one being is redirected to is secure that the check command fails.
>

Did you try any of the other options for -f, like '-f sticky' or '-f 
stickyport'?

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
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

Re: [Nagios-users] check_http fails for two Sprint sites

2012-02-24 Thread Frank Bulk

Yes, I did -- no go.  You can test it yourself -- there's nothing special
about where I'm testing it from. =)

It's clear that check_http is choking on it, and I suspect it's because it
redirects to a secure version of the site.

Frank

-Original Message-
From: Paul Dubuc [mailto:w...@paul.dubuc.org] 
Sent: Friday, February 24, 2012 8:26 AM
To: frnk...@iname.com; Nagios Users List
Subject: Re: [Nagios-users] check_http fails for two Sprint sites

Frank Bulk wrote:
> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
> failed to pass check_http.  What's strange is that the v4 version of
> www.sprint.net also fails.
>
> I see that there are 302's (redirection) to the secure version of the
site,
> but using the '-f follow' command doesn't help, either.  It seems that if
> the site one being is redirected to is secure that the check command
fails.
>

Did you try any of the other options for -f, like '-f sticky' or '-f
stickyport'?



--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
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

Re: [Nagios-users] check_http fails for two Sprint sites

2012-02-23 Thread Joerg Linge

OK, more tests.

check_http with verbose output

OMD[gearman]:~$ ./lib/nagios/plugins/check_http -vv -H www.sprint.net
GET / HTTP/1.1
User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
Connection: close
Host: www.sprint.net


CRITICAL - Socket timeout after 10 seconds

so lets test with low level telnet 


OMD[gearman]:~$ telnet www.sprint.net 80
Trying 2600::...
Connected to www.sprint.net.
Escape character is '^]'.
GET / HTTP/1.1
Host: www.sprint.net

HTTP/1.1 302 Moved Temporarily
Server: HTTP Proxy/1.0
Connection: Close
Content-Length: 0
Location: https://www.sprint.net/


Server: HTTP Proxy/1.0 ??

Lets do a http 1.0 request


OMD[gearman]:~$ telnet www.sprint.net 80
Trying 2600::...
Connected to www.sprint.net.
Escape character is '^]'.
GET / HTTP/1.0

HTTP/1.1 200 OK
Set-Cookie: ServerID=1125; path=/
Date: Fri, 24 Feb 2012 07:26:04 GMT
Content-Type: text/html
Connection: close
Server: Apache/2.2.21 (Unix)

Now its an Apache 2.2.22 ??

Joerg

Am 24.02.2012 um 07:02 schrieb Frank Bulk:

> So if wget can follow redirects from insecure to secure sites, why can't
> check_http?
> 
> Frank
> 
> -Original Message-
> From: Joerg Linge [mailto:pitchf...@ederdrom.de] 
> Sent: Thursday, February 23, 2012 11:40 PM
> To: Nagios Users List
> Subject: Re: [Nagios-users] check_http fails for two Sprint sites
> 
> Hi Frank,
> your side does not respond to http requests
> 
> OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -H www.sprint.net
> CRITICAL - Socket timeout after 10 seconds
> OMD[gearman]:~$ ./lib/nagios/plugins/check_http -H www.sprint.net
> CRITICAL - Socket timeout after 10 seconds
> 
> HTTPS works well
> 
> OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -S -H www.sprint.net
> HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.744 second response time
> |time=0.743648s;;;0.00 size=18004B;;;0
> OMD[gearman]:~$ ./lib/nagios/plugins/check_http -S -H www.sprint.net
> HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.736 second response time
> |time=0.735588s;;;0.00 size=18004B;;;0
> 
> wget redirects directly to HTTPS 
> 
> OMD[gearman]:~$ wget www.sprint.net
> --2012-02-24 06:37:35--  http://www.sprint.net/
> Resolving www.sprint.net... 2600::, 208.24.22.50
> Connecting to www.sprint.net|2600::|:80... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: https://www.sprint.net/ [following]
> --2012-02-24 06:37:36--  https://www.sprint.net/
> Connecting to www.sprint.net|2600::|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: “index.html”
> 2012-02-24 06:37:37 (1.31 MB/s) - “index.html” saved [17739]
> 
> 
> Joerg
> 
> Am 24.02.2012 um 00:58 schrieb Frank Bulk:
> 
>> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
>> failed to pass check_http.  What's strange is that the v4 version of
>> www.sprint.net also fails.  
>> 
>> I see that there are 302's (redirection) to the secure version of the
> site,
>> but using the '-f follow' command doesn't help, either.  It seems that if
>> the site one being is redirected to is secure that the check command
> fails.
>> 
>> I'm running check_http version 1.4.15.
>> 
>> Here's my output:
>> 
>> 
> 
>> ==
>> nagios:/etc/nagios3#
>> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net
> -4
>> CRITICAL - Socket timeout after 10 seconds
>> nagios:/etc/nagios3#
>> nagios:/etc/nagios3# wget -4 www.sprint.net
>> --2012-02-23 17:52:06--  http://www.sprint.net/
>> Resolving www.sprint.net... 208.24.22.50
>> Connecting to www.sprint.net|208.24.22.50|:80... connected.
>> HTTP request sent, awaiting response... 302 Moved Temporarily
>> Location: https://www.sprint.net/ [following]
>> --2012-02-23 17:52:06--  https://www.sprint.net/
>> Connecting to www.sprint.net|208.24.22.50|:443... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: unspecified [text/html]
>> Saving to: âindex.html.4â
>> 
>>   [ <=>
>> ] 16,997  --.-K/s   in 0.05s
>> 
>> 2012-02-23 17:52:06 (348 KB/s) - âindex.html.4â
>> 
>> nagios:/etc/nagios3#
>> 
> 
>> ==
>> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net
> -6
>> CRITICAL - Socket timeout after 10 seconds
>> nagios:/etc/nagios3#
>> nagios:/etc/nagios3# wget -6 www.sprint.net
>> --2012-02-23 17:54:49--  http://www.sprint

Re: [Nagios-users] check_http fails for two Sprint sites

2012-02-23 Thread Frank Bulk

So if wget can follow redirects from insecure to secure sites, why can't
check_http?

Frank

-Original Message-
From: Joerg Linge [mailto:pitchf...@ederdrom.de] 
Sent: Thursday, February 23, 2012 11:40 PM
To: Nagios Users List
Subject: Re: [Nagios-users] check_http fails for two Sprint sites

Hi Frank,
your side does not respond to http requests

OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -H www.sprint.net
CRITICAL - Socket timeout after 10 seconds
OMD[gearman]:~$ ./lib/nagios/plugins/check_http -H www.sprint.net
CRITICAL - Socket timeout after 10 seconds

HTTPS works well

OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -S -H www.sprint.net
HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.744 second response time
|time=0.743648s;;;0.00 size=18004B;;;0
OMD[gearman]:~$ ./lib/nagios/plugins/check_http -S -H www.sprint.net
HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.736 second response time
|time=0.735588s;;;0.00 size=18004B;;;0

wget redirects directly to HTTPS 

OMD[gearman]:~$ wget www.sprint.net
--2012-02-24 06:37:35--  http://www.sprint.net/
Resolving www.sprint.net... 2600::, 208.24.22.50
Connecting to www.sprint.net|2600::|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.sprint.net/ [following]
--2012-02-24 06:37:36--  https://www.sprint.net/
Connecting to www.sprint.net|2600::|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: index.html
2012-02-24 06:37:37 (1.31 MB/s) - index.html saved [17739]

 
Joerg

Am 24.02.2012 um 00:58 schrieb Frank Bulk:

> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
> failed to pass check_http.  What's strange is that the v4 version of
> www.sprint.net also fails.  
> 
> I see that there are 302's (redirection) to the secure version of the
site,
> but using the '-f follow' command doesn't help, either.  It seems that if
> the site one being is redirected to is secure that the check command
fails.
> 
> I'm running check_http version 1.4.15.
> 
> Here's my output:
> 
>

> ==
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net
-4
> CRITICAL - Socket timeout after 10 seconds
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# wget -4 www.sprint.net
> --2012-02-23 17:52:06--  http://www.sprint.net/
> Resolving www.sprint.net... 208.24.22.50
> Connecting to www.sprint.net|208.24.22.50|:80... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: https://www.sprint.net/ [following]
> --2012-02-23 17:52:06--  https://www.sprint.net/
> Connecting to www.sprint.net|208.24.22.50|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: âindex.html.4â
> 
>[ <=>
> ] 16,997  --.-K/s   in 0.05s
> 
> 2012-02-23 17:52:06 (348 KB/s) - âindex.html.4â
> 
> nagios:/etc/nagios3#
>

> ==
> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net
-6
> CRITICAL - Socket timeout after 10 seconds
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# wget -6 www.sprint.net
> --2012-02-23 17:54:49--  http://www.sprint.net/
> Resolving www.sprint.net... 2600::
> Connecting to www.sprint.net|2600::|:80... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: https://www.sprint.net/ [following]
> --2012-02-23 17:54:49--  https://www.sprint.net/
> Connecting to www.sprint.net|2600::|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: âindex.html.5â
> 
>[ <=>
> ] 17,739  --.-K/s   in 0s
> 
> 2012-02-23 17:54:49 (174 MB/s) - âindex.html.5â
> 
> nagios:/etc/nagios3#
>

> ==
> 
> 
>

--
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> ___
> 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


---

Re: [Nagios-users] check_http fails for two Sprint sites

2012-02-23 Thread Joerg Linge

Hi Frank,
your side does not respond to http requests

OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -H www.sprint.net
CRITICAL - Socket timeout after 10 seconds
OMD[gearman]:~$ ./lib/nagios/plugins/check_http -H www.sprint.net
CRITICAL - Socket timeout after 10 seconds

HTTPS works well

OMD[gearman]:~$ ./lib/nagios/plugins/check_http -6 -S -H www.sprint.net
HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.744 second response time 
|time=0.743648s;;;0.00 size=18004B;;;0
OMD[gearman]:~$ ./lib/nagios/plugins/check_http -S -H www.sprint.net
HTTP OK: HTTP/1.1 200 OK - 18004 bytes in 0.736 second response time 
|time=0.735588s;;;0.00 size=18004B;;;0

wget redirects directly to HTTPS 

OMD[gearman]:~$ wget www.sprint.net
--2012-02-24 06:37:35--  http://www.sprint.net/
Resolving www.sprint.net... 2600::, 208.24.22.50
Connecting to www.sprint.net|2600::|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.sprint.net/ [following]
--2012-02-24 06:37:36--  https://www.sprint.net/
Connecting to www.sprint.net|2600::|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html”
2012-02-24 06:37:37 (1.31 MB/s) - “index.html” saved [17739]

 
Joerg

Am 24.02.2012 um 00:58 schrieb Frank Bulk:

> Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
> failed to pass check_http.  What's strange is that the v4 version of
> www.sprint.net also fails.  
> 
> I see that there are 302's (redirection) to the secure version of the site,
> but using the '-f follow' command doesn't help, either.  It seems that if
> the site one being is redirected to is secure that the check command fails.
> 
> I'm running check_http version 1.4.15.
> 
> Here's my output:
> 
> 
> ==
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -4
> CRITICAL - Socket timeout after 10 seconds
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# wget -4 www.sprint.net
> --2012-02-23 17:52:06--  http://www.sprint.net/
> Resolving www.sprint.net... 208.24.22.50
> Connecting to www.sprint.net|208.24.22.50|:80... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: https://www.sprint.net/ [following]
> --2012-02-23 17:52:06--  https://www.sprint.net/
> Connecting to www.sprint.net|208.24.22.50|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: âindex.html.4â
> 
>[ <=>
> ] 16,997  --.-K/s   in 0.05s
> 
> 2012-02-23 17:52:06 (348 KB/s) - âindex.html.4â
> 
> nagios:/etc/nagios3#
> 
> ==
> nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -6
> CRITICAL - Socket timeout after 10 seconds
> nagios:/etc/nagios3#
> nagios:/etc/nagios3# wget -6 www.sprint.net
> --2012-02-23 17:54:49--  http://www.sprint.net/
> Resolving www.sprint.net... 2600::
> Connecting to www.sprint.net|2600::|:80... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: https://www.sprint.net/ [following]
> --2012-02-23 17:54:49--  https://www.sprint.net/
> Connecting to www.sprint.net|2600::|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: âindex.html.5â
> 
>[ <=>
> ] 17,739  --.-K/s   in 0s
> 
> 2012-02-23 17:54:49 (174 MB/s) - âindex.html.5â
> 
> nagios:/etc/nagios3#
> 
> ==
> 
> 
> --
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> ___
> 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


--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
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/nu

[Nagios-users] check_http fails for two Sprint sites

2012-02-23 Thread Frank Bulk

Starting this morning two IPv6 sites, www.sprint.net and www.sprintv6.net
failed to pass check_http.  What's strange is that the v4 version of
www.sprint.net also fails.  

I see that there are 302's (redirection) to the secure version of the site,
but using the '-f follow' command doesn't help, either.  It seems that if
the site one being is redirected to is secure that the check command fails.

I'm running check_http version 1.4.15.

Here's my output:


==
nagios:/etc/nagios3#
nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -4
CRITICAL - Socket timeout after 10 seconds
nagios:/etc/nagios3#
nagios:/etc/nagios3# wget -4 www.sprint.net
--2012-02-23 17:52:06--  http://www.sprint.net/
Resolving www.sprint.net... 208.24.22.50
Connecting to www.sprint.net|208.24.22.50|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.sprint.net/ [following]
--2012-02-23 17:52:06--  https://www.sprint.net/
Connecting to www.sprint.net|208.24.22.50|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: âindex.html.4â

[ <=>
] 16,997  --.-K/s   in 0.05s

2012-02-23 17:52:06 (348 KB/s) - âindex.html.4â

nagios:/etc/nagios3#

==
nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -6
CRITICAL - Socket timeout after 10 seconds
nagios:/etc/nagios3#
nagios:/etc/nagios3# wget -6 www.sprint.net
--2012-02-23 17:54:49--  http://www.sprint.net/
Resolving www.sprint.net... 2600::
Connecting to www.sprint.net|2600::|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.sprint.net/ [following]
--2012-02-23 17:54:49--  https://www.sprint.net/
Connecting to www.sprint.net|2600::|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: âindex.html.5â

[ <=>
] 17,739  --.-K/s   in 0s

2012-02-23 17:54:49 (174 MB/s) - âindex.html.5â

nagios:/etc/nagios3#

==


--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
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] check_http frequent timeouts

2012-01-19 Thread James Osbourn

I am monitoring an external web server at one of our sites from a Nagios 
instance at another site.  During the day I will see frequent timeouts 
retrieving the webpage.  I have increased the timeout to 20 seconds and the 
problem still occurs.

What is interesting is that I have other web serves at the same site being 
monitored in the same way that are not exhibiting the same issue.

I am trying to pin down whether this is a related to the Nagios check or if the 
server itself is as fault, or perhaps the path in between.  The only difference 
with those servers that are working and the one that is giving time outs is the 
web server that is be running.  The one with the time outs is running lighttp 
and the others are running apache.

Has anyone seen any similar situation and could lend any suggestions as to a 
possible fix.

Thanks

James

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
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

Re: [Nagios-users] check_http -L writes raw html (a href) but does not render link in browser

2011-11-15 Thread Kimberly McKinnis

Aha. Thank you muchly!




On 11/9/11 9:40 PM, "Joerg Linge"  wrote:

>
>Am 09.11.2011 um 22:33 schrieb Kimberly McKinnis:
>
>> I'm using the stock Nagios 3 package from aptitude on Ubuntu. I wrote a
>> new check using check_http, but the -L isn't entirely doing what I'd
>> expect. Do I need to set something else somewhere in Nagios to get
>>browser
>> renderable code? I've tried both Firefox and Safari on MacOSX Lion.
>> 
>> My check:
>> define command{
>>command_namecheck-livepass-gateways
>>command_line/usr/lib/nagios/plugins/check_http -L -H
>>  -u  -t 5 -R 'unknown' --invert-regex
>>}
>> 
>> 
>> 
>> My check spits out the raw html code instead of actually making it a
>>link:
>> > HREF="obfuscated URL"
>> target="_blank">HTTP OK: HTTP/1.1 200 OK - 13878 bytes in 0.304
>> second response time 
>
>cgi.cfg:
>
># ESCAPE HTML TAGS
># This option determines whether HTML tags in host and service
># status output is escaped in the web interface.  If enabled,
># your plugin output will not be able to contain clickable links.
>
>escape_html_tags=1
>
>--
>
>RSA(R) Conference 2012
>Save $700 by Nov 18
>Register now
>http://p.sf.net/sfu/rsa-sfdev2dev1
>___
>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


--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
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

Re: [Nagios-users] check_http -L writes raw html (a href) but does not render link in browser

2011-11-09 Thread Joerg Linge


Am 09.11.2011 um 22:33 schrieb Kimberly McKinnis:

> I'm using the stock Nagios 3 package from aptitude on Ubuntu. I wrote a
> new check using check_http, but the -L isn't entirely doing what I'd
> expect. Do I need to set something else somewhere in Nagios to get browser
> renderable code? I've tried both Firefox and Safari on MacOSX Lion.
> 
> My check:
> define command{
>command_namecheck-livepass-gateways
>command_line/usr/lib/nagios/plugins/check_http -L -H
>  -u  -t 5 -R 'unknown' --invert-regex
>}
> 
> 
> 
> My check spits out the raw html code instead of actually making it a link:
>  HREF="obfuscated URL"
> target="_blank">HTTP OK: HTTP/1.1 200 OK - 13878 bytes in 0.304
> second response time 

cgi.cfg:

# ESCAPE HTML TAGS
# This option determines whether HTML tags in host and service
# status output is escaped in the web interface.  If enabled,
# your plugin output will not be able to contain clickable links.

escape_html_tags=1

--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
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] check_http -L writes raw html (a href) but does not render link in browser

2011-11-09 Thread Kimberly McKinnis

I'm using the stock Nagios 3 package from aptitude on Ubuntu. I wrote a
new check using check_http, but the -L isn't entirely doing what I'd
expect. Do I need to set something else somewhere in Nagios to get browser
renderable code? I've tried both Firefox and Safari on MacOSX Lion.

My check:
define command{
command_namecheck-livepass-gateways
command_line/usr/lib/nagios/plugins/check_http -L -H
 -u  -t 5 -R 'unknown' --invert-regex
}



My check spits out the raw html code instead of actually making it a link:
HTTP OK: HTTP/1.1 200 OK - 13878 bytes in 0.304
second response time 




C O N V I V A 
Kimberly McKinnis | Systems Engineer, Service Delivery | k...@conviva.com |
Mobile: 724.612.2716 |
2 WATERS PARK DRIVE  |  SUITE 150  |  SAN MATEO  |  CA  |  94403  |
www.conviva.com |




--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
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

Re: [Nagios-users] check_http results - interpreting error messages.

2011-11-02 Thread Holger Weiß

* Giles Coochey  [2011-11-02 09:09]:
> I am monitoring a website, and I sometimes get two types of error:
> 
> One is:
> 
> CRITICAL - Socket timeout after 10 seconds
> 
> and the other is:
> 
> HTTP CRITICAL - No data received from host
> 
> What is the difference between the two errors? Is it the case that
> the HTTP CRITICAL error connected to the server via TCP, but didn't
> get a page and that the Socket timeout error didn't even establish
> the TCP connection?

Yes, that's the difference.

Holger

--
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
___
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] check_http results - interpreting error messages.

2011-11-02 Thread Giles Coochey


I am monitoring a website, and I sometimes get two types of error:

One is:

CRITICAL - Socket timeout after 10 seconds

and the other is:

HTTP CRITICAL - No data received from host

What is the difference between the two errors? Is it the case that the 
HTTP CRITICAL error connected to the server via TCP, but didn't get a 
page and that the Socket timeout error didn't even establish the TCP 
connection?


Thanks

Giles



smime.p7s
Description: S/MIME Cryptographic Signature
--
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1___
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

Re: [Nagios-users] check_http and other response codes

2011-10-14 Thread Morty

On Thu, Oct 13, 2011 at 09:39:43AM +0200, Jörg Linge wrote:

> http://nagiosplugins.org/man/check_http
> 
> Option -e
> 
> -e, --expect=STRING
> Comma-delimited list of strings, at least one of them is expected in
> the first (status) line of the server response (default: HTTP/1.)
> If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
> processing)

Oh, thanks!  I saw that option, but misunderstood it.  Now I've got it
working.

For TRACE, I think the "negate" implementation is actually better.
CUPS IPP returns no response code at all to a TRACE request, which is
good from my perspective.

- Morty

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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

Re: [Nagios-users] check_http and other response codes

2011-10-13 Thread Jörg Linge


Am 13.10.2011 um 09:18 schrieb Morty:

> On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
>> Isn't there some regex matching?
> 
> There is.  But it didn't help me in either case.  check_http
> apparently does an implicit test to make sure it gets a valid response
> code such as 200.  And the regex checking is in content, not headers
> or response code.  So check_http -H $host -S -r 401 still returns a
> warning with a server that requires auth, and check_http -H $host -S
> -j TRACE -r 405 still returns a warning on a server with TRACE
> disabled.
> 
> While reading a different thread on this mailing list, I found Mark
> Thomas's mention of "negate".  That actually did workaround my HTTP
> TRACE problem -- TRACE will cause check_http to return a warning when
> it's disabled and ok when it's enabled, so the following command
> definition will test for HTTP TRACE:
> 
> define command{
>command_namecheck_http_trace
>command_line$USER1$/negate -sw OK -o CRITICAL -c OK -- 
> $USER1$/check_http -j TRACE -f sticky -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
>}
> 
> But IMHO, that's something of a hack.  And it doesn't deal with the 401 issue.

http://nagiosplugins.org/man/check_http

Option -e

-e, --expect=STRING
Comma-delimited list of strings, at least one of them is expected in
the first (status) line of the server response (default: HTTP/1.)
If specified skips all other status line logic (ex: 3xx, 4xx, 5xx 
processing)
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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

Re: [Nagios-users] check_http and other response codes

2011-10-13 Thread Morty

On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
> Isn't there some regex matching?

There is.  But it didn't help me in either case.  check_http
apparently does an implicit test to make sure it gets a valid response
code such as 200.  And the regex checking is in content, not headers
or response code.  So check_http -H $host -S -r 401 still returns a
warning with a server that requires auth, and check_http -H $host -S
-j TRACE -r 405 still returns a warning on a server with TRACE
disabled.

While reading a different thread on this mailing list, I found Mark
Thomas's mention of "negate".  That actually did workaround my HTTP
TRACE problem -- TRACE will cause check_http to return a warning when
it's disabled and ok when it's enabled, so the following command
definition will test for HTTP TRACE:

define command{
command_namecheck_http_trace
command_line$USER1$/negate -sw OK -o CRITICAL -c OK -- 
$USER1$/check_http -j TRACE -f sticky -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
}

But IMHO, that's something of a hack.  And it doesn't deal with the 401 issue.

- Morty

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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

Re: [Nagios-users] check_http and other response codes

2011-10-12 Thread Frank Bulk

Isn't there some regex matching?

Frank

-Original Message-
From: Morty [mailto:morty+nag...@frakir.org] 
Sent: Wednesday, October 12, 2011 9:46 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_http and other response codes

On some of our apache servers, the normal response code is 401
(authentication required) rather than 200.  I'd also like to use
nagios to make sure the apache TRACE method stays disabled, with a
response code of 405.  Problem: check_http returns a warning if the
response code is anything but 200.  In the first case, both 200 and
401 are acceptable; in the latter case, I want 405 rather than 200.

Is there a way to require or allow a different response code?

I'm using check_http 1.4.15, as packaged with Debian 5.x.  I googled,
but didn't find clue.  :(

Thanks!

- Morty


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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] check_http and other response codes

2011-10-12 Thread Morty

On some of our apache servers, the normal response code is 401
(authentication required) rather than 200.  I'd also like to use
nagios to make sure the apache TRACE method stays disabled, with a
response code of 405.  Problem: check_http returns a warning if the
response code is anything but 200.  In the first case, both 200 and
401 are acceptable; in the latter case, I want 405 rather than 200.

Is there a way to require or allow a different response code?

I'm using check_http 1.4.15, as packaged with Debian 5.x.  I googled,
but didn't find clue.  :(

Thanks!

- Morty

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
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

Re: [Nagios-users] check_http with multiple outcomes?

2011-08-09 Thread Terry Carmen

Quoting "Dr. Ed Morbius" :

> Terry:
>
> on 23:37 Mon 08 Aug, Terry Carmen (te...@cnysupport.com) wrote:
>> Quoting Edward Morbius :
>> >
>> > When some things are going well and others aren't fully up to speed (slow
>> > database), we'll get a "DATABASE_TEST_RAN_LONG", which isn't ideal, but at
>> > least for a few occurances (n <= 5) we can live with.  In particular, we
>> > DON'T want a single result sounding off pagers in the middle of the night.
>>
>> You can specify -e "OK,DATABASE_TEST_RAN_LONG", then let the plugin
>> decide if it's slow or not, with the -w,  -c and -t  parameters.
>>
>> Terry
>
> Thanks.
>
> I'd considered that. It doesn't quite match what we want to test.  I'm
> thinking we may need to have a few different tests, possibly related to
> one another.
>
> If there's a 4xx/5xx error, it's a hard fail.
>
> If there's no 4xx/5xx error, but we get the "DATABASE_TEST_RAN_LONG"
> result, it's a soft fail, turning hard on 6 repeats.  That string
> appears in our application, it's not a nagios-determined slowness.
> Alternately, we might want to have a separate test for DB performance
> (there may well be, I'm still digging through rules and tests).
>
> If there's an "OK" result, there's no error.
>
>
> The 4xx/5xx errors are exclusive of the other two possible results. If
> there's no 4xx/5xx error, we've got the option of either of the other
> two conditions.
>
> So: is this a three-check test?  How would I set precedence among them?

You can actually completely ignore the DATABASE_TEST_RAN_LONG result and let 
the plugin decide if it ran long or not. That's part of it's design. The plugin 
also handles the 4xx and 5xx errors. 

However if you insist on using the DATABASE_TEST_RAN_LONG result to determine 
if the server is happy, then you'll need to modify the plugin to catch the 
string and interpret it as a WARNING OR CRITICAL as appropriate. Nagios won't 
notify on it until it happens several times in a row, depending on your 
specific settings.

Unless I'm misunderstanding something, The only result that matters is "OK" 
because everything else is "Not OK", regardless of whether it's a performance 
issue, an access issue or a server failure. I believe you're unnecessarily 
complicating the test.
--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
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

Re: [Nagios-users] check_http with multiple outcomes?

2011-08-09 Thread Dr. Ed Morbius

Terry:

on 23:37 Mon 08 Aug, Terry Carmen (te...@cnysupport.com) wrote:
> Quoting Edward Morbius :
> >
> > When some things are going well and others aren't fully up to speed (slow
> > database), we'll get a "DATABASE_TEST_RAN_LONG", which isn't ideal, but at
> > least for a few occurances (n <= 5) we can live with.  In particular, we
> > DON'T want a single result sounding off pagers in the middle of the night.
> 
> You can specify -e "OK,DATABASE_TEST_RAN_LONG", then let the plugin
> decide if it's slow or not, with the -w,  -c and -t  parameters.
> 
> Terry

Thanks.

I'd considered that. It doesn't quite match what we want to test.  I'm
thinking we may need to have a few different tests, possibly related to
one another.

If there's a 4xx/5xx error, it's a hard fail.

If there's no 4xx/5xx error, but we get the "DATABASE_TEST_RAN_LONG"
result, it's a soft fail, turning hard on 6 repeats.  That string
appears in our application, it's not a nagios-determined slowness.
Alternately, we might want to have a separate test for DB performance
(there may well be, I'm still digging through rules and tests).

If there's an "OK" result, there's no error.

The 4xx/5xx errors are exclusive of the other two possible results. If
there's no 4xx/5xx error, we've got the option of either of the other
two conditions.

So: is this a three-check test?  How would I set precedence among them?

-- 
Dr. Ed Morbius, Chief Scientist /|
  Robot Wrangler / Staff Psychologist| When you seek unlimited power
Krell Power Systems Unlimited|  Go to Krell!

--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
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

Re: [Nagios-users] check_http with multiple outcomes?

2011-08-08 Thread Terry Carmen

Quoting Edward Morbius :
>
> When some things are going well and others aren't fully up to speed (slow
> database), we'll get a "DATABASE_TEST_RAN_LONG", which isn't ideal, but at
> least for a few occurances (n <= 5) we can live with.  In particular, we
> DON'T want a single result sounding off pagers in the middle of the night.

You can specify -e "OK,DATABASE_TEST_RAN_LONG", then let the plugin decide if 
it's slow or not, with the -w,  -c and -t  parameters.

Terry

[-w ] [-c ] [-t ] [  
>
> The current test looks like:
>
> define command{
>         command_name    check_jetty
>         command_line    /usr/lib/nagios/plugins/check_http -H
> '$HOSTADDRESS$' -u /serviceStatus -e 200 -s OK
>         }
>
> What would be a sane process of getting Nagios to:
>
>  - Report all clear when we get a 200 status and "OK" text on page?
>  - Wait for 6 consecutive instances of "DATABASE_TEST_RAN_LONG" before
> alerting for that result.
>  - Alert immediately on any cases not matching one of the above?
>
> I don't believe we can capture this in a single test unless I'm missing
> something.
>
> Thanks in advance.
>
> --
> Dr. Ed Morbius
> Chief Scientist
> Krell Power Systems Unlimited
>

  

-- 
Terry Carmen
CNY Support, LLC
Web. Database. Business.
http://www.cnysupport.com--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
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] check_http with multiple outcomes?

2011-08-08 Thread Edward Morbius

We're monitoring a local Jetty (Java webserver) process using an application
status page. When everything's going well, it includes the string "OK",
which we check for. This should be a clearly successful status test.

When everything's not going well, we get some sort of 4xx or 5xx error
message. This should trigger alerts immediately.

When some things are going well and others aren't fully up to speed (slow
database), we'll get a "DATABASE_TEST_RAN_LONG", which isn't ideal, but at
least for a few occurances (n <= 5) we can live with.  In particular, we
DON'T want a single result sounding off pagers in the middle of the night.

The current test looks like:

define command{
command_namecheck_jetty
command_line/usr/lib/nagios/plugins/check_http -H
'$HOSTADDRESS$' -u /serviceStatus -e 200 -s OK
}

What would be a sane process of getting Nagios to:

 - Report all clear when we get a 200 status and "OK" text on page?
 - Wait for 6 consecutive instances of "DATABASE_TEST_RAN_LONG" before
alerting for that result.
 - Alert immediately on any cases not matching one of the above?

I don't believe we can capture this in a single test unless I'm missing
something.

Thanks in advance.

-- 
Dr. Ed Morbius
Chief Scientist
Krell Power Systems Unlimited
--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
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

Re: [Nagios-users] check_http + headers

2011-07-29 Thread af . at . work

I tried multiple -k parameters to add more headers with the same
result.  This is the output from Nagios with a 400 Bad Request status.
I assume that is because the cookie is effectively broken.

GET http://mywebsite.com/home.aspx HTTP/1.1
User-Agent: check_http/v1.4.15 (nagios-plugins 1.4.15)
Connection: close
Host: mywebsite.com
Cookie: user=4reqrerqwr
userlogin=123adsfjlk324


cURL via the CLI is almost identical, but the Cookie: is kept on one line.

GET http://mywebsite.com/home.aspx HTTP/1.1
Connection: close
Host: mywebsite.com
Cookie: user=4reqrerqwr;userlogin=123adsfjlk324



On Fri, Jul 29, 2011 at 10:49 AM, Ton Voon  wrote:
>
> On 29 Jul 2011, at 14:35, af.at.w...@gmail.com wrote:
>
>> I am trying to mimic this in Nagios with check_http like so:
>>
>> ./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
>> follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
>> -v
>
> You should use multiple -k to add more headers.
>
> Ton
>
>
> --
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> ___
> 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
>

--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
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

Re: [Nagios-users] check_http + headers

2011-07-29 Thread af . at . work

Per the Nagios doc, I also tried putting the ; in a $USERn$ variable &
passed that in my check but it still drops the second cookie value to
another line.

On Fri, Jul 29, 2011 at 10:14 AM,   wrote:
> Wrapping in quotes still made pushed the second value to another line.
> Cookie: 
> "AwarenessNETUserLogin_8800=04dDHmcJjn2vfcvP97i+z9yBGic0y4BIhNfDo8wN1fE=
> username=admin"
>
> Can the ; be escaped? I can't pass anything else.
>
> On Fri, Jul 29, 2011 at 10:03 AM, Gary Every  wrote:
>> Try using something besides  a ; to separate the user and userlogin or
>> better yet encapsulate them in quotes???
>>  'Cookie: "user=4reqrerqwr;userlogin=123adsfjlk324"'
>>
>> On Fri, Jul 29, 2011 at 6:35 AM,  wrote:
>>>
>>> With cURL, I can successfully log into the website I ultimately want
>>> have Nagios test by passing --cookies.
>>>
>>> Something like this: curl --cookie
>>> "user=4reqrerqwr;userlogin=123adsfjlk324"
>>> http://mysite.com/home/index.aspx -v | grep Welcome
>>>
>>> I know it is successful because, 1, I can visually see the rendered
>>> code and 2, the grep search for Welcome would only be seen if the
>>> authentication was successful.
>>>
>>> I am trying to mimic this in Nagios with check_http like so:
>>>
>>> ./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
>>> follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
>>> -v
>>>
>>> One big difference I see is that in cURL the cookie is set on 1 line
>>> but the verbose response from check_http shows the cookie on two
>>> lines.
>>>
>>> Cookie: user=4reqrerqwr;userlogin=123adsfjlk324 vs
>>>
>>> Cookie: user=4reqrerqwr
>>> userlogin=123adsfjlk324
>>>
>>> I am open to suggestions and of course alternatives. I have checked
>>> out WebInject but this seems to be SO close I hate to drop it.
>>>
>>> Lastly, I have tried check_curl, and extended it to support cookies.
>>> This DOES work but I am getting (null) on the responses and the grep
>>> never causes Nagios to fail regardless of a valid result being
>>> returned.
>>>
>>>
>>> --
>>> Got Input?   Slashdot Needs You.
>>> Take our quick survey online.  Come on, we don't ask for help often.
>>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>>> http://p.sf.net/sfu/slashdot-survey
>>> ___
>>> 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
>>
>>
>>
>> --
>> Gary Every
>> "Pay it Forward!"
>>
>>
>> --
>> Got Input?   Slashdot Needs You.
>> Take our quick survey online.  Come on, we don't ask for help often.
>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>> http://p.sf.net/sfu/slashdot-survey
>> ___
>> 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
>>
>

--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
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

Re: [Nagios-users] check_http + headers

2011-07-29 Thread Ton Voon


On 29 Jul 2011, at 14:35, af.at.w...@gmail.com wrote:

> I am trying to mimic this in Nagios with check_http like so:
> 
> ./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
> follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
> -v

You should use multiple -k to add more headers.

Ton


--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
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

Re: [Nagios-users] check_http + headers

2011-07-29 Thread af . at . work

Wrapping in quotes still made pushed the second value to another line.
Cookie: "AwarenessNETUserLogin_8800=04dDHmcJjn2vfcvP97i+z9yBGic0y4BIhNfDo8wN1fE=
username=admin"

Can the ; be escaped? I can't pass anything else.

On Fri, Jul 29, 2011 at 10:03 AM, Gary Every  wrote:
> Try using something besides  a ; to separate the user and userlogin or
> better yet encapsulate them in quotes???
>  'Cookie: "user=4reqrerqwr;userlogin=123adsfjlk324"'
>
> On Fri, Jul 29, 2011 at 6:35 AM,  wrote:
>>
>> With cURL, I can successfully log into the website I ultimately want
>> have Nagios test by passing --cookies.
>>
>> Something like this: curl --cookie
>> "user=4reqrerqwr;userlogin=123adsfjlk324"
>> http://mysite.com/home/index.aspx -v | grep Welcome
>>
>> I know it is successful because, 1, I can visually see the rendered
>> code and 2, the grep search for Welcome would only be seen if the
>> authentication was successful.
>>
>> I am trying to mimic this in Nagios with check_http like so:
>>
>> ./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
>> follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
>> -v
>>
>> One big difference I see is that in cURL the cookie is set on 1 line
>> but the verbose response from check_http shows the cookie on two
>> lines.
>>
>> Cookie: user=4reqrerqwr;userlogin=123adsfjlk324 vs
>>
>> Cookie: user=4reqrerqwr
>> userlogin=123adsfjlk324
>>
>> I am open to suggestions and of course alternatives. I have checked
>> out WebInject but this seems to be SO close I hate to drop it.
>>
>> Lastly, I have tried check_curl, and extended it to support cookies.
>> This DOES work but I am getting (null) on the responses and the grep
>> never causes Nagios to fail regardless of a valid result being
>> returned.
>>
>>
>> --
>> Got Input?   Slashdot Needs You.
>> Take our quick survey online.  Come on, we don't ask for help often.
>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>> http://p.sf.net/sfu/slashdot-survey
>> ___
>> 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
>
>
>
> --
> Gary Every
> "Pay it Forward!"
>
>
> --
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> ___
> 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
>

--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
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

Re: [Nagios-users] check_http + headers

2011-07-29 Thread Gary Every

Try using something besides  a ; to separate the user and userlogin or
better yet encapsulate them in quotes???

 'Cookie: "user=4reqrerqwr;userlogin=123adsfjlk324"'

On Fri, Jul 29, 2011 at 6:35 AM,  wrote:

> With cURL, I can successfully log into the website I ultimately want
> have Nagios test by passing --cookies.
>
> Something like this: curl --cookie
> "user=4reqrerqwr;userlogin=123adsfjlk324"
> http://mysite.com/home/index.aspx -v | grep Welcome
>
> I know it is successful because, 1, I can visually see the rendered
> code and 2, the grep search for Welcome would only be seen if the
> authentication was successful.
>
> I am trying to mimic this in Nagios with check_http like so:
>
> ./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
> follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
> -v
>
> One big difference I see is that in cURL the cookie is set on 1 line
> but the verbose response from check_http shows the cookie on two
> lines.
>
> Cookie: user=4reqrerqwr;userlogin=123adsfjlk324 vs
>
> Cookie: user=4reqrerqwr
> userlogin=123adsfjlk324
>
> I am open to suggestions and of course alternatives. I have checked
> out WebInject but this seems to be SO close I hate to drop it.
>
> Lastly, I have tried check_curl, and extended it to support cookies.
> This DOES work but I am getting (null) on the responses and the grep
> never causes Nagios to fail regardless of a valid result being
> returned.
>
>
> --
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> ___
> 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
>



-- 
Gary Every
"Pay it Forward!"
--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey___
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] check_http + headers

2011-07-29 Thread af . at . work

With cURL, I can successfully log into the website I ultimately want
have Nagios test by passing --cookies.

Something like this: curl --cookie
"user=4reqrerqwr;userlogin=123adsfjlk324"
http://mysite.com/home/index.aspx -v | grep Welcome

I know it is successful because, 1, I can visually see the rendered
code and 2, the grep search for Welcome would only be seen if the
authentication was successful.

I am trying to mimic this in Nagios with check_http like so:

./check_http -H mysite.com -u http://mysite.com/home/index.aspx -f
follow -s Welcome -k 'Cookie: user=4reqrerqwr;userlogin=123adsfjlk324'
-v

One big difference I see is that in cURL the cookie is set on 1 line
but the verbose response from check_http shows the cookie on two
lines.

Cookie: user=4reqrerqwr;userlogin=123adsfjlk324 vs

Cookie: user=4reqrerqwr
userlogin=123adsfjlk324

I am open to suggestions and of course alternatives. I have checked
out WebInject but this seems to be SO close I hate to drop it.

Lastly, I have tried check_curl, and extended it to support cookies.
This DOES work but I am getting (null) on the responses and the grep
never causes Nagios to fail regardless of a valid result being
returned.

--
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
___
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] check_http plugin times out with urls using self-signed certs

2011-07-06 Thread Traiano Welcome

Hi List


I use the standard check_http plugin to check  a number of websites, testing 
for a string returned by a cgi script hosted on the site. Similar to the 
following example:

---
 /usr/local/libexec/nagios/check_http -I 196.666.666.666 -a x:y -u 
http://monkey.donkey.net/cgi-bin/nagios.cgi -s Operational
---

One of these sites uses as self-signed cert, which causes check_http to 
timeout. I assume this behavour is identical to what happens when you browse to 
such a url using a browser, i.e you get a prompt saying something like:

---
SSL error:self signed certificate-Continue? (y) 
---

At which point the check_http plugin would wait for timeout, not being able to 
answer with a "y". Is there any way I can get the plugin to somehow bypass this 
(maybe passing a "y" in response to the prompt), or some way of importing the 
self-signed cert so the prompt does not appear in the first place? We're stuck 
with the self signed cert for some time until we can get a 'proper' one.

Thanks in Advance,
Traiano Welcome
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
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

Re: [Nagios-users] check_http encrypted link

2011-05-09 Thread Mike Chesnut

On 05/09/2011 07:20 AM, Tristan Drinkwater wrote:
> I’m struggling to check a http link that’s encrypted.
>
> The full url works ok in a browser but I get ‘unable to open a TCP
> socket’ error when I run ‘check_http –H domain/encrypted link’ from the
> command line.
>
> I’ve also tried ‘check_http –H domain –u /encrypted link” but that’s not
> working either.
>
> Is check_http even able to check such a thing?

If by encrypted you mean served over SSL (i.e., https), then all you 
should have to do is include the "-S" parameter to check_http.

You probably would want to do "-p 443" also.

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
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] check_http encrypted link

2011-05-09 Thread Tristan Drinkwater

Hey guys,

I'm struggling to check a http link that's encrypted.

The full url works ok in a browser but I get 'unable to open a TCP socket' 
error when I run 'check_http -H domain/encrypted link' from the command line.

I've also tried 'check_http -H domain -u /encrypted link" but that's not 
working either.

Is check_http even able to check such a thing?

Thanks in advance :)




Micro Peripherals Limited.
Registered Office: Shorten Brook Way, Altham Business Park, Altham,
Accrington, Lancs. BB5 5YJ. Tel: (01282) 776776 Fax: (01282) 858790
Micro Peripherals Limited. Registered in England No. 1511931. VAT No. GB 864 
4387 91

DISCLAIMER:
This e-mail and attachments are confidential and are intended solely for the 
use of the individual to
whom it is addressed. Any views or opinions presented are solely those of the 
author and do not
necessarily represent those of Micro Peripherals Limited.
If you are not the intended recipient, be advised that you have received this 
Email in error and that
any use, dissemination, forwarding, printing, or copying of this Email is 
strictly prohibited. If this
transmission is received in error please notify the sender immediately and 
delete this message from
your E-mail system.
All electronic transmissions to and from Micro Peripherals Ltd are recorded and 
may be monitored.
--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd___
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

Re: [Nagios-users] check_http with auth issue

2011-01-20 Thread Ray Kiddy


On Jan 20, 2011, at 1:35 PM, stan wrote:

> Hi,
> We're having problems with Nagios3 (3.2.0) reporting 'HTTP WARNING HTTP/1.1 
> 401 Unauthorized' for check_http queries to a several switched CDUs of the 
> same type. All these CDUs have HTTP Server = enabled, Authentication= Basic. 
> 
> Running check_http from the command line returns an OK status:
> /usr/lib/nagios/plugins/check_http -I ppcr23ps1 --authorization=user:passwd
> HTTP OK HTTP/1.1 200 OK - 763 bytes in 0.267 seconds
> 

We had a similar problem. We have several CNAME entries for different names for 
some of our hosts. We were using a host definition that included the IP 
address. Then we switched to a host definition that was using the DNS name only.

Also, be careful of certain characters in your password digest. If an ampersand 
appears in the password digest (and they seem to pop up about 1/3 of the time), 
you have to protect it with a backslash. We were running the check_http command 
the same way, but were of course putting single-quotes around the password 
digest and, gee, there is no problem.

These may not be your issue, but they may point you to something else. Good 
luck.

cheers - ray

> check_http is reporting OK status for all the other devices we're checking 
> from this Nagios3 server.
> 
> This Nagios3 server is an internal server in a distributed nagios 
> configuration, and we have 1 identical CDU configured on the main nagios 
> server outside the firewall (the external nagios is 3.1.0). The check_http on 
> the Nagios 3.1.0 server (external) does not give the WARNING 401 Unauthorized 
> message. It displays HTTP OK HTTP 1.1 200 OK. 
> 
> To verify that the CDU config was not the problem or the firmware version
> wasn't the problem on the 2 new CDUs being configd for the internal server, 
> we added the external CDU
> (already reporting OK on nagios 3.1.0) to the Nagios3 configuration & did a 
> check_http. Like the other 2 units, the command line reports HTTP OK but 
> nagios displays the 401 warning.
> 
> We've run from the command line check_http -v and it's identical on both 
> servers (everything is OK). 
> However, the header on the devices that do not get the 401 warning start
> with a Server: descrip and Connection: close before the Content-Type 
> 
> CDU:
> 
> STATUS: HTTP/1.1 200 OK
>  HEADER 
> Content-Type: text/html
> (the rest of the header info follows)
> 
> All other devices:
> 
> STATUS: HTTP/1.1 200 OK
>  HEADER 
> Server: Embedded Web Server(or whatever server description per device)
> Connection: close
> Content-Type: text/html
> (the rest of the header info follows)
> 
> Any ideas why it works on 3.1.0 and not 3.2.0?
> Thanks
> 
> 
> -- 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> --
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> ___
> 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
> 


--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
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] check_http with auth issue

2011-01-20 Thread stan

Hi,
We're having problems with Nagios3 (3.2.0) reporting 'HTTP WARNING HTTP/1.1 401 
Unauthorized' for check_http queries to a several switched CDUs of the same 
type. All these CDUs have HTTP Server = enabled, Authentication= Basic. 

Running check_http from the command line returns an OK status:
/usr/lib/nagios/plugins/check_http -I ppcr23ps1 --authorization=user:passwd
HTTP OK HTTP/1.1 200 OK - 763 bytes in 0.267 seconds

check_http is reporting OK status for all the other devices we're checking from 
this Nagios3 server.

This Nagios3 server is an internal server in a distributed nagios 
configuration, and we have 1 identical CDU configured on the main nagios server 
outside the firewall (the external nagios is 3.1.0). The check_http on the 
Nagios 3.1.0 server (external) does not give the WARNING 401 Unauthorized 
message. It displays HTTP OK HTTP 1.1 200 OK. 

To verify that the CDU config was not the problem or the firmware version
wasn't the problem on the 2 new CDUs being configd for the internal server, we 
added the external CDU
(already reporting OK on nagios 3.1.0) to the Nagios3 configuration & did a 
check_http. Like the other 2 units, the command line reports HTTP OK but nagios 
displays the 401 warning.

We've run from the command line check_http -v and it's identical on both 
servers (everything is OK). 
However, the header on the devices that do not get the 401 warning start
with a Server: descrip and Connection: close before the Content-Type 

CDU:

STATUS: HTTP/1.1 200 OK
 HEADER 
Content-Type: text/html
(the rest of the header info follows)

All other devices:

STATUS: HTTP/1.1 200 OK
 HEADER 
Server: Embedded Web Server(or whatever server description per device)
Connection: close
Content-Type: text/html
(the rest of the header info follows)

Any ideas why it works on 3.1.0 and not 3.2.0?
Thanks


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
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

Re: [Nagios-users] check_http and authentication

2011-01-20 Thread Edwin Zoeller

I am having the same type of problem but mine is that when I enter a
UID/PWD and change it to test it is always successful. What am I doing
wrong. 

-Original Message-
From: stan [mailto:st...@panix.com] 
Sent: Thursday, January 20, 2011 8:45 AM
To: nagios List
Subject: [Nagios-users] check_http and authentication

I have 2 Nagios instances at the moment. On one I am using the chck_http
pluging version 1.4.13, and on the other I have version 1.4.14. On both
systems I am check agains Server Tecnology PDU's. The older one works
fine.
The newer plugin reports a warning "HTTP Warning HTTP/1.1 401
Unauthorized
412 bytes ..." But when run from the command line you get status OK, and
a return code of 0. From the coomand line we are executing"check_http -H
"hostname" --authorization=:xxx".

I think that maybe the newer plugin requires a different set of options
to work with these units?

Any sugestions as to debuging this?

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
Protect Your Site and Customers from Malware Attacks Learn about various
malware tactics and how to avoid them. Understand malware threats, the
impact they can have on your business, and how you can protect your
company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
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

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
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] check_http and authentication

2011-01-20 Thread stan

I have 2 Nagios instances at the moment. On one I am using the chck_http
pluging version 1.4.13, and on the other I have version 1.4.14. On both
systems I am check agains Server Tecnology PDU's. The older one works fine.
The newer plugin reports a warning "HTTP Warning HTTP/1.1 401 Unauthorized
412 bytes ..." But when run from the command line you get status OK, and a
return code of 0. From the coomand line we are executing"check_http -H
"hostname" --authorization=:xxx".

I think that maybe the newer plugin requires a different set of options to
work with these units?

Any sugestions as to debuging this?

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
___
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

Re: [Nagios-users] check_http requests - SSL Not available

2010-11-12 Thread Kevin Davison

Yes. openssl-devel is installed.

Package openssl-devel-0.9.8e-12.el5_4.6.x86_64 already installed and latest 
version
Package openssl-devel-0.9.8e-12.el5_4.6.i386 already installed and latest 
version



From: Assaf Flatto [mailto:nag...@flatto.net]
Sent: November-12-10 12:27 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_http requests - SSL Not available

On 12/11/10 17:15, Kevin Davison wrote:
I've been digging at this one for a while and not getting any closer to 
resolution.

Has anyone else encountered problems with getting check_http to  work with the 
-S/--ssl option?

Nagios 3.2.1 running on a CentOS box.
I have openssl and openssl-devel installed


Package openssl-0.9.8e-12.el5_4.6.x86_64 already installed and latest version
Package openssl-0.9.8e-12.el5_4.6.i686 already installed and latest version
Nothing to do

Package openssl-devel-0.9.8e-12.el5_4.6.x86_64 already installed and latest 
version
Package openssl-devel-0.9.8e-12.el5_4.6.i386 already installed and latest 
version
Nothing to do

I recompiled my plugins and got confirmation of openssl
--with-apt-get-command:
   --with-ping6-command: /bin/ping6 -n -U -w %d -c %d %s
   --with-ping-command: /bin/ping -n -U -w %d -c %d %s
   --with-ipv6: yes
   --with-mysql: no
   --with-openssl: yes
   --with-gnutls: no
   --enable-extra-opts: no
   --with-perl: /usr/bin/perl
   --enable-perl-modules: no
   --with-cgiurl: /nagios/cgi-bin
   --with-trusted-path: /bin:/sbin:/usr/bin:/usr/sbin
   --enable-libtap: no

For some reason, after this, I'm still not able to get a response to -ssl 
checks using check_http.

[r...@nagios nagios-plugins-1.4.14]# /usr/local/nagios/libexec/check_http --ssl 
-H 
check_http: Invalid option - SSL is not available



Kevin Davison
Network Administrator

I am able to run the check_http  with the -S option

 ~/libexec/check_http -H 10.0.X.XX  -S
HTTP WARNING: HTTP/1.1 401 Authorization Required - 1726 bytes in 0.036 second 
response time |time=0.035854s;;;0.00 size=1726B;;;0

openssl might be installed , but do you have the devel package - it will be 
required for the compilation to work .




--

Never,Ever Cut A Deal With a Dragon





Next year I will be doing the London to Paris bike ride to

raise money for the DogTrust (www.dogstrust.co.uk<http://www.dogstrust.co.uk>) .

Please Sponsor me at http://www.justgiving.com/Assaf-Flatto
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
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

Re: [Nagios-users] check_http requests - SSL Not available

2010-11-12 Thread Assaf Flatto


 On 12/11/10 17:15, Kevin Davison wrote:


I've been digging at this one for a while and not getting any closer 
to resolution.


Has anyone else encountered problems with getting check_http to  work 
with the --S/--ssl option?


Nagios 3.2.1 running on a CentOS box.

I have openssl and openssl-devel installed

Package openssl-0.9.8e-12.el5_4.6.x86_64 already installed and latest 
version


Package openssl-0.9.8e-12.el5_4.6.i686 already installed and latest 
version


Nothing to do

Package openssl-devel-0.9.8e-12.el5_4.6.x86_64 already installed and 
latest version


Package openssl-devel-0.9.8e-12.el5_4.6.i386 already installed and 
latest version


Nothing to do

I recompiled my plugins and got confirmation of openssl

--with-apt-get-command:

   --with-ping6-command: /bin/ping6 -n -U -w %d -c %d %s

   --with-ping-command: /bin/ping -n -U -w %d -c %d %s

   --with-ipv6: yes

   --with-mysql: no

   --with-openssl: yes

   --with-gnutls: no

   --enable-extra-opts: no

   --with-perl: /usr/bin/perl

   --enable-perl-modules: no

   --with-cgiurl: /nagios/cgi-bin

   --with-trusted-path: /bin:/sbin:/usr/bin:/usr/sbin

   --enable-libtap: no

For some reason, after this, I'm still not able to get a response to 
--ssl checks using check_http.


[r...@nagios nagios-plugins-1.4.14]# 
/usr/local/nagios/libexec/check_http --ssl -H 


check_http: Invalid option - SSL is not available

Kevin Davison

Network Administrator



I am able to run the check_http  with the -S option

 ~/libexec/check_http -H 10.0.X.XX  -S
HTTP WARNING: HTTP/1.1 401 Authorization Required - 1726 bytes in 0.036 
second response time |time=0.035854s;;;0.00 size=1726B;;;0


openssl might be installed , but do you have the devel package - it will 
be required for the compilation to work .



--
Never,Ever Cut A Deal With a Dragon


Next year I will be doing the London to Paris bike ride to
raise money for the DogTrust (www.dogstrust.co.uk) .
Please Sponsor me at http://www.justgiving.com/Assaf-Flatto

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
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] check_http requests - SSL Not available

2010-11-12 Thread Kevin Davison

I've been digging at this one for a while and not getting any closer to 
resolution.

Has anyone else encountered problems with getting check_http to  work with the 
-S/--ssl option?

Nagios 3.2.1 running on a CentOS box.
I have openssl and openssl-devel installed

Package openssl-0.9.8e-12.el5_4.6.x86_64 already installed and latest version
Package openssl-0.9.8e-12.el5_4.6.i686 already installed and latest version
Nothing to do

Package openssl-devel-0.9.8e-12.el5_4.6.x86_64 already installed and latest 
version
Package openssl-devel-0.9.8e-12.el5_4.6.i386 already installed and latest 
version
Nothing to do

I recompiled my plugins and got confirmation of openssl
--with-apt-get-command:
   --with-ping6-command: /bin/ping6 -n -U -w %d -c %d %s
   --with-ping-command: /bin/ping -n -U -w %d -c %d %s
   --with-ipv6: yes
   --with-mysql: no
   --with-openssl: yes
   --with-gnutls: no
   --enable-extra-opts: no
   --with-perl: /usr/bin/perl
   --enable-perl-modules: no
   --with-cgiurl: /nagios/cgi-bin
   --with-trusted-path: /bin:/sbin:/usr/bin:/usr/sbin
   --enable-libtap: no

For some reason, after this, I'm still not able to get a response to -ssl 
checks using check_http.

[r...@nagios nagios-plugins-1.4.14]# /usr/local/nagios/libexec/check_http --ssl 
-H 
check_http: Invalid option - SSL is not available



Kevin Davison
Network Administrator
Innosphere SDG Ltd.
147 Wyndham St. N., Ste 306
Guelph, ON, N1H 4E9
(519) 766-9726 X223
Email: kdavi...@innosphere.ca
Website: www.innosphere.ca

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev___
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

Re: [Nagios-users] Check_http

2010-10-20 Thread Jonathan Angliss

On 10/20/10 01:08, Rajesh Kumar wrote:
> Hi All
>  I have configured Nagios Core in CentOS. I did
> remotehost(retpro) services of cpu, memory, user, ssh and ping also but
> unable to config check_http.
>  How to configure remotehost http (url) and Notification Alert (If
> http down). Pls verify my cfg file in
> /usr/local/nagios/etc/objects/retpro.cfg

Monitoring remote services like HTTP, SSH, and the likes are covered in 
the manual, and there is probably already a sample setup in the default 
configs with CentOS:

   http://nagios.sourceforge.net/docs/3_0/monitoring-publicservices.html

But basically, it'll most likely look something like this:

define service {
use generic-service
host_name   retpro
service_description HTTP
check_command   check_http
}

If you're looking to monitor a specific page loads, you may need to 
create a new command, something like this:

define command {
   command_name check_http_url
   command_line $USER1$/check_http -H $HOSTADDRESS$ -u $ARG1$
}

define service {
{usual service stuff}
check_command   check_http_url!/testpage.php
}

> define service{
>  use generic-service
>  host_name   retpro
>  service_description   Root Partition
>  check_command  check_local_disk!20%!10%!/
>  }

As Robert Wolfe pointed out, this command is probably not doing what you 
think it is.  check_local_disk will most likely be doing disk checks 
against the server running nagios, making this a duplicate of a monitor 
you may already have in place.  You will need to use something like 
NRPE, or check_by_ssh to check remote hosts.  Your services for those 
real checks will likely look something like:

define service {
use generic-service
host_name   retpro
service_description root partition
check_command   check_nrpe!check_disk!20!10
}

This assumes a check_nrpe command has been defined.

-- 
Jonathan Angliss


--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
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

Re: [Nagios-users] Check_http

2010-10-20 Thread Robert Wolfe

It doesn't look like you have check_http configured in this setup
(unless I am totally blind and don't see it).  Also, the other checks
(like the checks for disk space, users, etc) should be run using nrpe on
the remote host with nrpe returning that data back to Nagios (this is
how I have it set up both here at home and at work for our VoIP
monitoring server which runs the latest Nagios).

 

From: Rajesh Kumar [mailto:ras.kuma...@gmail.com] 
Sent: Wednesday, October 20, 2010 2:08 AM
To: Nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Check_http

 

Hi All 
I have configured Nagios Core in CentOS. I did
remotehost(retpro) services of cpu, memory, user, ssh and ping also but
unable to config check_http. 
How to configure remotehost http (url) and Notification Alert (If
http down). Pls verify my cfg file in
/usr/local/nagios/etc/objects/retpro.cfg
 
define host{
uselinux-server
host_name retpro
alias  retpro
address 192.168.1.116
}

define service{
use  generic-service
host_name   retpro 

service_descriptionPING
check_command   check_ping!100.0,20%!500.0,60%
normal_check_interval   5
}
define service{
use generic-service
host_name   retpro

service_description   Root Partition
check_command  check_local_disk!20%!10%!/
}

define service{
use generic-service
host_name   retpro

service_description   SSH
check_command  check_ssh
notifications_enabled 1
}
define service{
use  generic-service
host_name   retpro
service_descriptionTotal Processes
check_command   check_local_procs!250!400!RSZDT
}

define service{
use   generic-service
host_nameretpro

service_description Current Load
check_command
check_local_load!5.0,4.0,3.0!10.0,6.0/4.0
}
 
Thanks & Regards
 
B.Rajeshkumar
09894943041.

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev___
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] Check_http

2010-10-19 Thread Rajesh Kumar

Hi All
I have configured Nagios Core in CentOS. I did
remotehost(retpro) services of cpu, memory, user, ssh and ping also but
unable to config check_http.
How to configure remotehost http (url) and Notification Alert (If http
down). Pls verify my cfg file in /usr/local/nagios/etc/objects/retpro.cfg

define host{
uselinux-server
host_name retpro
alias  retpro
address 192.168.1.116
}
define service{
use  generic-service
host_name   retpro
service_descriptionPING
check_command   check_ping!100.0,20%!500.0,60%
normal_check_interval   5
}
define service{
use generic-service
host_name   retpro
service_description   Root Partition
check_command  check_local_disk!20%!10%!/
}
define service{
use generic-service
host_name   retpro
service_description   SSH
check_command  check_ssh
notifications_enabled 1
}
define service{
use  generic-service
host_name   retpro
service_descriptionTotal Processes
check_command   check_local_procs!250!400!RSZDT
}
define service{
use   generic-service
host_nameretpro
service_description Current Load
check_command
check_local_load!5.0,4.0,3.0!10.0,6.0/4.0
}

Thanks & Regards

B.Rajeshkumar
09894943041.
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev___
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

Re: [Nagios-users] check_http started failing on one monitor

2010-10-18 Thread Peters, Paul

Well it just started working again.  I will see what I can find since it
makes no sense. 

-Original Message-
From: Peters, Paul 
Sent: Monday, October 18, 2010 11:51 AM
To: Nagios Users List
Subject: [Nagios-users] check_http started failing on one monitor

I have a monitor that has been using "check_http --ssl -H hostname" for
over a year, and it just started failing today for some reason.  It was
working fine up until an hour ago.  I have other hosts using the same
check without issue.  I have checked the same host through a wget,
telnet, and using "check_tcp -p 443 -H hostname", and they all work
fine.  I keep getting a socket connection timeout even if I extend that
to 30 seconds.  The certificate is even good for another 18 days.  Any
ideas?

-prp
___

RBC Wealth Management does not accept buy, sell, or cancel orders by
e-mail, or any instructions by e-mail that would require your
signature. Information contained in this communication is not
considered an official record of your account and does not supersede
normal trade confirmations or statements. Any information provided has
been prepared from sources believed to be reliable but is not
guaranteed, does not represent all available data necessary for making
investment decisions and is for informational purposes only.
This message is intended only for residents of the states
in which the sender is registered as applicable to the content.

This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use,
or copying of this e-mail or the information it contains by other than
an intended recipient is unauthorized. If you receive this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.

Information received by or sent from this system is subject to review
by supervisory personnel, is retained and may be produced to
regulatory authorities or others with a legal right to the information.

Unless specified by the sender, e-mail messages are not encrypted. 
As such, client sensitive information sent to or received from your RBC
Wealth Management Financial Consultant electronically may not be secure.

With respect to the companies that are the subject of an equity
research report not authored by our firm that is included in this
electronic mail message, RBC Wealth Management is required to disclose
to you certain conflicts of interest.  Any such disclosures may be
obtained by either accessing our web site at

https://www.rbccm.com/GLDisclosure/PublicWeb/DisclosureLookup.aspx?Entit
yID=2  

or by mailing a request for such information to RBC Wealth Management
Research Publishing, 60 South Sixth Street, Mailstop P18, Minneapolis,
MN 55402.

RBC Wealth Management, a division of RBC Capital Markets Corporation.
Member NYSE/FINRA/SIPC.

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that
run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
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

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
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] check_http started failing on one monitor

2010-10-18 Thread Peters, Paul


I have a monitor that has been using "check_http --ssl -H hostname" for
over a year, and it just started failing today for some reason.  It was
working fine up until an hour ago.  I have other hosts using the same
check without issue.  I have checked the same host through a wget,
telnet, and using "check_tcp -p 443 -H hostname", and they all work
fine.  I keep getting a socket connection timeout even if I extend that
to 30 seconds.  The certificate is even good for another 18 days.  Any
ideas?

-prp
___

RBC Wealth Management does not accept buy, sell, or cancel orders by
e-mail, or any instructions by e-mail that would require your
signature. Information contained in this communication is not
considered an official record of your account and does not supersede
normal trade confirmations or statements. Any information provided has
been prepared from sources believed to be reliable but is not
guaranteed, does not represent all available data necessary for making
investment decisions and is for informational purposes only.
This message is intended only for residents of the states
in which the sender is registered as applicable to the content.

This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use,
or copying of this e-mail or the information it contains by other than
an intended recipient is unauthorized. If you receive this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.

Information received by or sent from this system is subject to review
by supervisory personnel, is retained and may be produced to
regulatory authorities or others with a legal right to the information.

Unless specified by the sender, e-mail messages are not encrypted. 
As such, client sensitive information sent to or received from your RBC
Wealth Management Financial Consultant electronically may not be secure.

With respect to the companies that are the subject of an equity
research report not authored by our firm that is included in this
electronic mail message, RBC Wealth Management is required to disclose
to you certain conflicts of interest.  Any such disclosures may be
obtained by either accessing our web site at

https://www.rbccm.com/GLDisclosure/PublicWeb/DisclosureLookup.aspx?EntityID=2  

or by mailing a request for such information to RBC Wealth Management
Research Publishing, 60 South Sixth Street, Mailstop P18, Minneapolis,
MN 55402.

RBC Wealth Management, a division of RBC Capital Markets Corporation.
Member NYSE/FINRA/SIPC.


--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
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

Re: [Nagios-users] check_http (bogus) setup

2010-04-16 Thread Gerard Petersen

Dear Marc,

Thanx for you elaborate feedback. The joke is somewhat on me, but more on 
that in a second. You're documentation is good and to the point!

The configuration I used was a apt-get installed nagios3 on Ubuntu 9.10 
which seems a recipe from a modern kitchen.

I ofcourse totally agree with you that you can't be responsible for how 
other distro's deploy your (marvelous piece of) software.

Then for laughs .. I have set up a major Nagios cluster in the past. You can 
check here whether or not my Nagios knowledge is good enough:

http://www.gerardjp.com/2007/05/12/nagios-remote-eventhandling-for-init-scripts/
(RFE'd the $MAX_CHECK_ATTEMPTS$ which was incorporated in a newer release btw)

Anyway, in that aformentioned nagios setup, I used to check for a list of 
urls, from 2 different nodes running nrpe. It must be pure coincidence that 
these two nodes did run a webserver themselves. I now realize that I never 
checked the intended urls, but just the websites running on these nodes.

Ah well .. one lives and learns :)

Thanx again!

On 15-04-10 14:45, Marc Powell wrote:
>
> On Apr 15, 2010, at 3:50 AM, Gerard Petersen wrote:
>
>> Hi All,
>>
>> I've been testing with the check_http service. I always was under the
>> assumption that the setup below would check www.example.com
>
> Why did you make this assumption? It's not documented to work like this.
>
>>  check_command   check_http!www.example.com!/
>
>> With this service definition (as often installed out of the box):
>>
>> define command{
>>  command_namecheck_http
>>  command_line   /usr/lib/nagios/plugins/check_http -H '$HOSTADDRESS$'
>>  }
>
> It's not been like this in a long time I believe. Perhaps you've installed 
> from a distribution specific package and they've deviated from current 
> nagios? If so, there's nothing that we can do about that. This is what the 
> official package uses --
>
> # 'check_http' command definition
> define command{
>  command_namecheck_http
>  command_line$USER1$/check_http -I $HOSTADDRESS$ $ARG1$
>  }
>
> Note that your assumed configuration still wouldn't work here but the 
> official documentation expects this definition. See 'Monitoring HTTP' at 
> http://nagios.sourceforge.net/docs/3_0/monitoring-publicservices.html.
>
>> Wrong! It would check for a webserver on myhost1. Since there's nothing
>> running at myhost1:80 i got a TCP error. Somewhat baffled I've been tailing
>> the access.log of www.example.com to see when I actually got a hit.
>
>
>> The funny thing is this (with no additional parms) even returns ok, would
>> you have a webserver listening on myhost1:80
>>
>> check_command   check_http
>
> This is because your command_line doesn't use any of the params you think 
> you're passing it ($ARG1$, $ARG2$).
>
>> So, you would be wise to turn the command syntax into this:
>>
>> command_line/usr/lib/nagios/plugins/check_http -H '$ARG1$' -u '$ARG2$'
>
> Or follow the example documented use of the plugin. In general, you can't 
> make assumptions about how a plugin works without looking at, and 
> understanding, the defined command_line for that plugin. Every one is 
> different.
>
>> Then this will actually test www.example.com:
>>
>>   check_command   check_http!www.example.com!/
>>
>> Is it me or is this check_http setup misleading? (ubuntu 9.10 in this case)
>
> No, but that would depend on the documentation you're referencing to use the 
> plugin. If the ubuntu documentation says that your format works with their 
> packaged version of the check_http command definition, then that is 
> misleading and they should correct that. Otherwise it looks like you made an 
> incorrect assumption about how something worked without understanding it. If 
> I buy a car from a dealer and they tell me it runs on diesel, fill it up with 
> diesel and it doesn't, then that's their fault. If they don't tell me 
> anything about it and I assume it does without reading the manual, that's my 
> fault.
>
> For a new admin, the simplest use case is just to check that a web server is 
> listening on a host. That's what your definition does and what the official 
> definition does if no additional parameters are passed. As an admin becomes 
> more familiar with the plugin and more sophisticated in what they want to do 
> they need to edit either one or both of the command_line and check_command in 
> your case but only the check_command in the official case. I think the 
> official way provides the most flexibility all around, IMHO.
>
> --
> Marc
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>

Re: [Nagios-users] check_http (bogus) setup

2010-04-15 Thread Morris, Patrick

Gerard Petersen wrote:
> Hi All,
>
> I've been testing with the check_http service. I always was under the 
> assumption that the setup below would check www.example.com
>
> define service{
>  use generic-service
>  host_name   myhost1
>  service_description http - www.example.com
>  check_command   check_http!www.example.com!/
>  }
>
> With this service definition (as often installed out of the box):
>
> define command{
>  command_namecheck_http
>  command_line   /usr/lib/nagios/plugins/check_http -H '$HOSTADDRESS$'
>  }
>
> Wrong! It would check for a webserver on myhost1. Since there's nothing 
> running at myhost1:80 i got a TCP error. Somewhat baffled I've been tailing 
> the access.log of www.example.com to see when I actually got a hit.
>   

Why would you assume it would check www.example.com?  Your service 
definition clearly tells it to check $HOSTADDRESS$, which is the address 
of the host the service is defined on.
> The funny thing is this (with no additional parms) even returns ok, would 
> you have a webserver listening on myhost1:80
>
> check_command   check_http
>
> So, you would be wise to turn the command syntax into this:
>
> command_line/usr/lib/nagios/plugins/check_http -H '$ARG1$' -u '$ARG2$'
>
> Then this will actually test www.example.com:
>
>   check_command   check_http!www.example.com!/
>
> Is it me or is this check_http setup misleading? (ubuntu 9.10 in this case)
>   

It's you.  The plugin's parameters, and the value of Nagios's macros, 
are all very well-defined and well-documented.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
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

Re: [Nagios-users] check_http (bogus) setup

2010-04-15 Thread Marc Powell

On Apr 15, 2010, at 3:50 AM, Gerard Petersen wrote:

> Hi All,
> 
> I've been testing with the check_http service. I always was under the 
> assumption that the setup below would check www.example.com

Why did you make this assumption? It's not documented to work like this.

> check_command   check_http!www.example.com!/

> With this service definition (as often installed out of the box):
> 
> define command{
> command_namecheck_http
> command_line   /usr/lib/nagios/plugins/check_http -H '$HOSTADDRESS$'
> }

It's not been like this in a long time I believe. Perhaps you've installed from 
a distribution specific package and they've deviated from current nagios? If 
so, there's nothing that we can do about that. This is what the official 
package uses --

# 'check_http' command definition
define command{
command_namecheck_http
command_line$USER1$/check_http -I $HOSTADDRESS$ $ARG1$
}

Note that your assumed configuration still wouldn't work here but the official 
documentation expects this definition. See 'Monitoring HTTP' at 
http://nagios.sourceforge.net/docs/3_0/monitoring-publicservices.html.

> Wrong! It would check for a webserver on myhost1. Since there's nothing 
> running at myhost1:80 i got a TCP error. Somewhat baffled I've been tailing 
> the access.log of www.example.com to see when I actually got a hit.

> The funny thing is this (with no additional parms) even returns ok, would 
> you have a webserver listening on myhost1:80
> 
> check_command   check_http

This is because your command_line doesn't use any of the params you think 
you're passing it ($ARG1$, $ARG2$).

> So, you would be wise to turn the command syntax into this:
> 
> command_line/usr/lib/nagios/plugins/check_http -H '$ARG1$' -u '$ARG2$'

Or follow the example documented use of the plugin. In general, you can't make 
assumptions about how a plugin works without looking at, and understanding, the 
defined command_line for that plugin. Every one is different.

> Then this will actually test www.example.com:
> 
>  check_command   check_http!www.example.com!/
> 
> Is it me or is this check_http setup misleading? (ubuntu 9.10 in this case)

No, but that would depend on the documentation you're referencing to use the 
plugin. If the ubuntu documentation says that your format works with their 
packaged version of the check_http command definition, then that is misleading 
and they should correct that. Otherwise it looks like you made an incorrect 
assumption about how something worked without understanding it. If I buy a car 
from a dealer and they tell me it runs on diesel, fill it up with diesel and it 
doesn't, then that's their fault. If they don't tell me anything about it and I 
assume it does without reading the manual, that's my fault.

For a new admin, the simplest use case is just to check that a web server is 
listening on a host. That's what your definition does and what the official 
definition does if no additional parameters are passed. As an admin becomes 
more familiar with the plugin and more sophisticated in what they want to do 
they need to edit either one or both of the command_line and check_command in 
your case but only the check_command in the official case. I think the official 
way provides the most flexibility all around, IMHO.

--
Marc

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
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] check_http (bogus) setup

2010-04-15 Thread Gerard Petersen

Hi All,

I've been testing with the check_http service. I always was under the 
assumption that the setup below would check www.example.com

define service{
 use generic-service
 host_name   myhost1
 service_description http - www.example.com
 check_command   check_http!www.example.com!/
 }

With this service definition (as often installed out of the box):

define command{
 command_namecheck_http
 command_line   /usr/lib/nagios/plugins/check_http -H '$HOSTADDRESS$'
 }

Wrong! It would check for a webserver on myhost1. Since there's nothing 
running at myhost1:80 i got a TCP error. Somewhat baffled I've been tailing 
the access.log of www.example.com to see when I actually got a hit.

The funny thing is this (with no additional parms) even returns ok, would 
you have a webserver listening on myhost1:80

check_command   check_http

So, you would be wise to turn the command syntax into this:

command_line/usr/lib/nagios/plugins/check_http -H '$ARG1$' -u '$ARG2$'

Then this will actually test www.example.com:

  check_command   check_http!www.example.com!/

Is it me or is this check_http setup misleading? (ubuntu 9.10 in this case)

If you do have a webserver running at myhost1 that's the url you check. So 
you might see an OK status and think you're testing www.example.com .. but 
you would never touch it.

Anybody experienced this?

Regards,

Gerard.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
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

Re: [Nagios-users] check_http issue

2010-04-08 Thread Shashank Kamble

Bingo, thanx Assaf. It worked.

Cheers,
Shashank

On Thu, Apr 8, 2010 at 10:14 AM, Assaf Flatto  wrote:

> Shashank Kamble wrote:
> >
> > Hello,
> >
> >
> >
> > I am newbie to Nagios. I successfully installed Nagios and its
> > monitoring most of our windows and Linux servers. Currently, I am
> > having issues with the one of the website we support for our client. I
> > defined a host and also defined an http service to monitor the website:
> >
> >
> >
> > Here is host and service definition to monitor a website.
> >
> >
> >
> > define host{
> >
> >  use  windows-server
> >
> >  host_name   illinoistollway
> >
> >  aliasillinoistollway
> >
> >  addresswww.illinoistollway.com
> > 
> >
> >  contact_groups  admins
> >
> >  }
> >
> >
> >
> > define service {
> >
> > use   local-service
> >
> > host_name   IllionisHighway
> >
> > service_description HTTP
> >
> > check_command  check_http
> >
> > }
> >
> >
> >
> > But I am getting an error that host is down and service is not
> > monitored as well.
> >
> >
> >
> > Could you please guide me how to resolve this issue?
> >
> >
> >
> > Thanks,
> >
> > Shashank
> >
> > 
>
> Before you added the host , did you make sure you can ping it ?
> did you also try to manually as the user nagios can execute the
> check_http script and get a proper response ?
>
> By default check_host_alive and check_http expect an IP address in the "
> address " Feild , not a FQDN .
> and that might be what is throwing your nagios of game.
>
> Change the "address"  to the IP address and see what response you get .
>
> Assaf
>
>
> --
> Never,Ever Cut A Deal With a Dragon
>
>
> I am doing a Charity Bike ride On the 27 of June for the
> Capital to Coast Charity. Please help by Donating
> http://www.justgiving.com/Lovefilm-capital-to-coast
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> 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
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
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

1 2 3 4 >

1 - 100 of 318 matches

Mail list logo