, however you might want to
consider that when your network is going ape, it's really nice to know
that
your Nagios machine doesn't require any external resources.
That's why IÂ chose local auth (htpasswd).
Now matter how much of the brown stuff is flying around, Nagios is up.
Those
I have no idea, but that would seem unlikely. Have you tried my other
suggestion?:
command[check_pdns_config_pub]=/path/to/your/bash-script
in bash-script:
#!/bin/bash
/usr/lib/nagios/plugins/check_procs -w 1:1 -c 1:1 -a pdns_recursor
In effect creating a bash wrapper for the plugin.
After wondering why all of the processes I'm checking with check_procs
were counting an extra, I discovered the bug with /bin/dash under Debian
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626913]
As a workaround (because I'm not interested in changing the default shell
for the entire
I have just installed a new Nagios server and wanting to make sure that
everything
is working. All appears to be ok except I cannot access the Network Outages
page,
I get the error
It appears as though you do not have permission to view information you
requested...
If you believe this
Hi:
I have been trying to track down the fix for this for a while. We have a Nagios
server monitoring a few dozen servers. Most of these servers authenticate users
against a separate (CentOS Directory Server). We ONLY use LDAP for user/group
authentication. It was configured via authconfig
I think it would be more sufficient to not monitor how much swap is in use
but to check if pages are read from swap in some period of time. Such as
warning: if some pages were read out of swap
critical: if in all of the last three measurement-periods pages were read
I can acces the
for this was pretty straightforward:
AuthType Basic
Require valid-user
Allow from 192.168.199.99
Satisfy any
However, although the main Nagios page come up fine, one cannot access any of
the
Monitoring links. You get:
It appears as though you do not have permission to view information for any
.
Doing the apache config for this was pretty straightforward:
AuthType Basic
Require valid-user
Allow from 192.168.199.99
Satisfy any
However, although the main Nagios page come up fine, one cannot access any of
the
Monitoring links. You get:
It appears as though you do not have
We have Nagios monitoring a variety of services on roughly 50 separate servers.
Several of them
are mail servers, but only the main (that contains most of the Nagios
notification recipients)
one has this problem.
The mail server will start to become unresponsive so just about any input (but
Quoting u...@3.am:
We have Nagios monitoring a variety of services on roughly 50
separate servers.nbsp; Several of them
are mail servers, but only the main (that contains most of the
Nagios notification recipients)
one has this problem.
The mail server will start to become unresponsive so
On Fri, Jun 24, 2011 at 11:53, u...@3.am wrote:
Quoting u...@3.am:
We have Nagios monitoring a variety of services on roughly 50
separate servers.nbsp; Several of them
are mail servers, but only the main (that contains most of the
Nagios notification recipients)
one has this problem.
.
It taking the mailserver offline fixes it, at least you know where to look,
I'd also check the mailserver logs. Some aren't too bright about handling
bounces
and if it's misconfiigured, you can end up with an infinite number of bounce
messages for the bounce messages.
Looking for mail loops
/message/jmjeddrzguzm2ekb
--
Ales Rikovsky, CVT UP
+420 585631826
ales.rikov...@upol.cz
Biskupske nam. 1
771 11 Olomouc
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event
13 matches
Mail list logo
