Re: [Nagios-users] check_http confusion / problem

2009-08-29 Thread David Dyer-Bennet
Jon Angliss wrote: On Fri, 28 Aug 2009 14:01:44 -0500, David Dyer-Bennet d...@dd-b.net wrote: [check_http questions] --help usually gives a whole bunch of extra information... Yes, that's where I got the information I had; it's what got me confused in the first place. In

[Nagios-users] check_http confusion / problem

2009-08-28 Thread David Dyer-Bennet
Thanks to various list members for pointing me at various bits of documentation that I hadn't been able to find, which explain that commands can in fact take arguments, and that those and other useful things are called macros. (I've been using macros since 1401 Autocoder, and mostly think of them

Re: [Nagios-users] check_http confusion / problem

2009-08-28 Thread jmoseley
No, it works - you have an '=' character after the '-e' argument. Leave that out or use expect= For more documentation: check_http --help James Moseley David Dyer-Bennet d...@dd-b.net wrote: [...@prcapp00 dev]$ /usr/lib/nagios/plugins/check_http --IP-address=192.168.5.3 -p 8075

Re: [Nagios-users] check_http confusion / problem

2009-08-28 Thread David Dyer-Bennet
On Fri, August 28, 2009 14:25, jmose...@corp.xanadoo.com wrote: No, it works - you have an '=' character after the '-e' argument. Leave that out or use expect= For more documentation: check_http --help That's where I found --expect= in the first place. All my tests showed it not working

Re: [Nagios-users] check_http confusion / problem

2009-08-28 Thread jmoseley
Not sure if regular expressions will work, but here's an example: [r...@plugins]# ./check_http -H www -e HTT HTTP OK HTTP/1.1 200 OK - 318 bytes in 0.004 seconds |time=0.004054s;;;0.00 size=318B;;;0 It finds the 'HTT' in the following status line: STATUS: HTTP/1.1 200 OK so it returns an

Re: [Nagios-users] check_http confusion / problem

2009-08-28 Thread Jon Angliss
On Fri, 28 Aug 2009 14:01:44 -0500, David Dyer-Bennet d...@dd-b.net wrote: Thanks to various list members for pointing me at various bits of documentation that I hadn't been able to find, which explain that commands can in fact take arguments, and that those and other useful things are called