Something a little more powerful and generic that can be used in
multiple scenarios
check_multi
See: http://exchange.nagios.org/directory/Plugins/Others/check_multi/details
On 30/05/2011 6:11 PM, quanta wrote:
Take a look at this:
http://www.theillien.com/Sys_Admin_v12/html/v14/i12/a6_l2.htm
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
I've finally gotten a chance to look at this again. Thank you to those that
responded with helpful information. However, I just realized that I am working
on an AIX 5.1 system, and since the binaries I'm using are written for 5.3,
there are compatibility issues which seem to be causing my prob
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
On 2011-06-02, at 01:44, Michael Vaknine wrote:
> I am monitoring some servers on a different site and usuing ADSL line for
> this.
> I have problems with the ADSL Each time I get a notification that a server is
> down and then after 5seconds I get a notification that the server is up again.
>
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", "-
11 matches
Mail list logo
