Hello Eliezer,
thanks for your reply.
On Mon, Jan 14, 2013 at 05:41:28PM +0200, Eliezer Croitoru wrote:
> I would try to run a basic script which logs the nrpe environment into a
> file.
> it will make sure what is available to you and what not.
>
> test if:
> [...]
> modify the above to make s
I would try to run a basic script which logs the nrpe environment into a
file.
it will make sure what is available to you and what not.
test if:
there are environment vars..
there is a STDOUT\IN\ERR available etc..
#!/usr/bin/env ruby
f = File.open("/tmp/nrpetest.log","a")
f.sync = true
f.puts
Hello all,
following up to myself ...
On Mon, Oct 08, 2012 at 08:31:21PM +0200, Florian Ernst wrote:
> [...]
> However, it got weirder: if I strace the nrpe process, everything works
> as desired:
> [...]
> I found no further hints in the strace log, but this led me to assume
> that there is some
Hello John / Tech Support,
thanks for your reply, and sorry for the delay in answering.
On Wed, Oct 10, 2012 at 03:10:13PM -0400, Tech Support wrote:
> Whenever I've had a problem with a plugin, and was trying to figure out
> what was going on, I've had 100% success using a little PERL script
enius is in its simplicity.
Regards;
John
-Original Message-
From: Florian Ernst [mailto:florian_er...@gmx.net]
Sent: Tuesday, October 09, 2012 2:14 PM
To: Nagios Users List
Subject: Re: [Nagios-users] NRPE: Unable to read output; but works when run
under strace ...
Hello Peter,
thanks
> -Oorspronkelijk bericht-
> Van: Florian Ernst [mailto:florian_er...@gmx.net]
> Verzonden: dinsdag 9 oktober 2012 20:14
> Aan: Nagios Users List
> Onderwerp: Re: [Nagios-users] NRPE: Unable to read output; but works
> when run under strace ...
>
> Hello Pet
Hello Peter,
thanks for your reply.
However, as previously written, I know of the peculiarities that might
arise once sudo joins the team, and in the issue at hand sudo is no more
involved than being used for illustration purposes while the issue
itself doesn't even remotely touch sudo at all.
Fu
Lol... had me going for a while to... for me the awnser was in the sudo config
(visudo)... it required a user on a tty... I believe the directive was
"requiretty". Disable that line and you'll be fine I think.
Peter
Van: Florian Ernst [florian_er...@gmx.
