Mailinglist
Subject: Re: [Nagios-users] check_http issues...
On Jun 9, 2008, at 1:48 PM, Victor Lanza wrote:
> Hi all,
>
> Sooo I upgraded from 3.0.1 to 3.0.2 in the hopes that the fix for
> the extra
> $ would be fixed in it but it doesn't seem to be.
From http://www.nagios.o
On Jun 9, 2008, at 1:48 PM, Victor Lanza wrote:
> Hi all,
>
> Sooo I upgraded from 3.0.1 to 3.0.2 in the hopes that the fix for
> the extra
> $ would be fixed in it but it doesn't seem to be.
From http://www.nagios.org, naigos-3.0.2 was released on 5/19. The
bug report was submitted to nagi
58 PM
To: nagios Mailinglist
Subject: Re: [Nagios-users] check_http issues...
On Jun 5, 2008, at 2:49 PM, Victor Lanza wrote:
> I'm using Nagios 3.0.1 with Plugins 1.4.11
>
> Ah..
>
> Well on another note if I were to use this password, where would I
> need to
> put
On Jun 5, 2008, at 2:49 PM, Victor Lanza wrote:
> I'm using Nagios 3.0.1 with Plugins 1.4.11
>
> Ah..
>
> Well on another note if I were to use this password, where would I
> need to
> put the escape character?
>
> The password is: 123$45!
If the debian supplied patch works as expected to
On Thu, Jun 05, 2008 at 03:49:24PM -0400, Victor Lanza wrote:
> Well on another note if I were to use this password, where would I need to
> put the escape character?
>
> The password is: 123$45!
You might need to escape both the $ and the !; both have special
meaning to a shell, in addition to a
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marc Powell
Sent: Thursday, June 05, 2008 3:39 PM
To: nagios Mailinglist
Subject: Re: [Nagios-users] check_http issues...
On Jun 5, 2008, at 2:08 PM, Victor Lanza wrote:
> The password is: 123$45!
>
&
On Jun 5, 2008, at 2:08 PM, Victor Lanza wrote:
> The password is: 123$45!
>
> The reason why I was passing it in single quotes was because the
> check_http
> plugin seemed to be able to pass it on to the site to authenticate
> with it
> just fine. If I removed the quotes, I got an access den
L PROTECTED] On Behalf Of Marc Powell
Sent: Thursday, June 05, 2008 2:46 PM
To: nagios Mailinglist
Subject: Re: [Nagios-users] check_http issues...
On Jun 5, 2008, at 1:28 PM, Victor Lanza wrote:
> Okit gets weirder..
>
> When I run the command again with that debug script, the log f
On Jun 5, 2008, at 1:28 PM, Victor Lanza wrote:
> Okit gets weirder..
>
> When I run the command again with that debug script, the log file
> doesn't
> get written. All users have access to write to the tmp directory by
> default
> so I don't know why it is not writing the log.
> /usr/lo
riginal Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Quintin
Sent: Thursday, June 05, 2008 1:18 PM
To: Victor Lanza
Cc: nagios Mailinglist
Subject: Re: [Nagios-users] check_http issues...
And the host address for mdfbbsw01 is defined as 10.10.4.10?
If so, I would
: nagios Mailinglist
> Subject: Re: [Nagios-users] check_http issues...
>
> You're using -I and the command line and -H in your conf. This makes
> a difference. I haven't figured out all the details yet, but I
> believe it affects what gets sent in the header...
>
&g
agios Mailinglist
Subject: Re: [Nagios-users] check_http issues...
You're using -I and the command line and -H in your conf. This makes
a difference. I haven't figured out all the details yet, but I
believe it affects what gets sent in the header...
On Thu, Jun 5, 2008 at 11:57 AM, Victo
You're using -I and the command line and -H in your conf. This makes
a difference. I haven't figured out all the details yet, but I
believe it affects what gets sent in the header...
On Thu, Jun 5, 2008 at 11:57 AM, Victor Lanza <[EMAIL PROTECTED]> wrote:
> I feel like this plugin hates me!...
>
I feel like this plugin hates me!...
I get a critical status with a (Null) Status Information and I can't seem to
figure out what I am doing wrong.
My command looks like this:
define command{
command_namecheck_http_arg
command_line$USER1$/check_http -H $HOSTADDRES
14 matches
Mail list logo
