On 06/02/2011 02:43 PM, Craig Stewart wrote:
> All,
>
> SELinux was enabled (DOH!) and has been now disabled. Didn't fix my
> problem though. Thanks for that Clint, I don't know HOW many times
> SELinux has bitten me. Should know by now.
>
> I ran the strace as suggested by Justin and saw THIS
The placement of the option may be significant if that option is set
somewhere else in the file, or in another file referenced by
"cfg_file" or "cfg_dir" options.
Our nagios-spawned environment has 6K of data, and
NAGIOS_SERVICEGROUPMEMBERS, in particular, is about 1k of that.
Justin
On Thu, Jun
All,
Just an update:
Appending "enable_environment_macros=0" to the end of the nagios.cfg
file as opposed to putting it just after all the file declarations
appears to have fixed it. I didn't think it was that sensitive to
placement in the config file.
Thanks all!
Craig
--
Craig Stewart
System
Justin,
I ran across that one as well and set the following in nagios.cfg:
enable_environment_macros=0
This didn't help. I do have a fairly large config (about 8k hosts and
12k service checks) but I didn't think it was THAT big.
Actually the check_dig command isn't the only one that isn't work
Ah, I think it may be due to a ngaios setting of
"enable_environment_macros":
nagios.sourceforge.net/docs/3_0/configmain.html
Nagios [can] export all sorts of data relating to the state of the
check, and that can be useful, but it seems as if your configuration
is too big or complicated or such to
Giorgio,
I appreciate all your guesses.
As far as the ulimits.conf file was, this system didn't have one! I did
run the ulimits -a as the nagios user anf got this:
-bash-4.2$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority
We are making guesses, so check ulimits.conf
Ciao,
Giorgio
Il giorno 02/giu/2011, alle ore 15:58, Craig Stewart
ha scritto:
> Giorgio,
>
> It's bash.
>
> [root@nms tmp]# ls -l /bin/sh
> lrwxrwxrwx. 1 root root 4 May 31 11:39 /bin/sh -> bash
> [root@nms tmp]#
>
> I've been doing a bit of re
Giorgio,
It's bash.
[root@nms tmp]# ls -l /bin/sh
lrwxrwxrwx. 1 root root 4 May 31 11:39 /bin/sh -> bash
[root@nms tmp]#
I've been doing a bit of reading and it looks like the maximum arguments
is a kernel setting built at compile time. I'm having a hard time
wrapping my head around how the che
Check wether your shell is a Dash or a Bash. That means, check where the
/bin/sh symlink is pointing to.
Ciao,
Giorgio
Il giorno 02/giu/2011, alle ore 14:43, Craig Stewart
ha scritto:
> All,
>
> SELinux was enabled (DOH!) and has been now disabled. Didn't fix my
> problem though. Thanks f
All,
SELinux was enabled (DOH!) and has been now disabled. Didn't fix my
problem though. Thanks for that Clint, I don't know HOW many times
SELinux has bitten me. Should know by now.
I ran the strace as suggested by Justin and saw THIS little tidbit flash by:
11769 execve("/bin/sh", ["sh", "-
Hi
Just wondering if SE Linux is disabled on your system? If not check your
audit log and see if access to the plugin is being denied
On Thu, Jun 2, 2011 at 8:15 AM, Justin T Pryzby wrote:
> You can also strace the main nagios process:
> strace -fs999 -e execve -p PID_OF_NAGIOS
> or
> sudo stra
You can also strace the main nagios process:
strace -fs999 -e execve -p PID_OF_NAGIOS
or
sudo strace -fs999 -e execve -p `ps o pid h -C nagios3 --sort start_time |sed
q` 2>&1 |grep -Fw execve |grep -Fw check_dig
127 is the return status of the shell when a command isn't found:
justinp@justinp:~$
I understand your confusion. Undortunately I will be om holiday until monday
and I won't be able to use a real computer for some tests.
Anyway, I will think about it.
Ciao,
Giorgio
Il giorno 01/giu/2011, alle ore 21:23, Craig Stewart
ha scritto:
> Giorgio
>
> As apache user:
>
> bash-4.2$
Matin,
Not quite sure what you mean. As far as I know I don't have a password
variable in my command definition.
Craig
--
Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
Xplornet - Broadband, Everywhere
On 06/01/2011 02:11 PM, M
Giorgio
As apache user:
bash-4.2$ /usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l
www.xplornet.com -a 142.166.86.46 -w 0.5 -c 1 -t 5
DNS OK - 0.096 seconds response time (www.xplornet.com. 864 IN A
142.166.86.46)|time=0.095553s;0.50;1.00;0.00
You understand my confusion.
Crai
Hi,
I'm curious. Please, do a su - as the apache user and execute the check as that
user.
Ciao,
Giorgio
Il giorno 01/giu/2011, alle ore 20:50, Craig Stewart
ha scritto:
> Giorgio,
>
> Here's the final command:
>
> [1306952706.565337] [2048.1] [pid=3753] Done. Final output:
> '/usr/lib/
Giorgio,
Here's the final command:
[1306952706.565337] [2048.1] [pid=3753] Done. Final output:
'/usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l www.xplornet.com
-a 142.166.86.46 -w 0.5 -c 1 -t 5'
I assume that's what you meant?
I'm also seeing this in the debug log:
[1306952721.202757
Please,
Switch on debug and paste here the "final command"
Ciao,
Giorgio
Il giorno 01/giu/2011, alle ore 16:47, Craig Stewart
ha scritto:
> Good day folks,
>
> I've spent the better part of a week using Google and combing forums for
> an answer to this question without much luck. First the
Hi Craig,
Not sure if it will help you but when I had a check reporting a similar plug-in
error that ran just fine from the terminal I removed the password variable from
the comd def and hard-coded the pwd in there instead. Worked for me.
Martin T. Hugo
Network Administrator
Hilliard City Scho
19 matches
Mail list logo
