[EMAIL PROTECTED] schrieb am 28.11.2005 14:06:26:
I have about 20 servers, for which I have no specific services to
monitor, but
which I am interested in their host status, ie the check_command in the
host
entry in the hosts.cfg file is set to check-host-alive.
However, it appears that
[EMAIL PROTECTED] schrieb am 12.12.2005 16:22:34:
I am using Nagios 2.0b6, but also experienced this issue in 2.0b4.
Nagios escalations do not seem to work when the state changes after a
maximum notifications level has been reached. For example, if a
You are mislead. Your escalations are only
[EMAIL PROTECTED] schrieb am 04.01.2006 11:18:58:
However the web interface doesnt seem to allow the cgi's to execute. I
can
get to http://serverIP/nagios/
The index page and documentation loads fine but i get the following
errors
when trying to load ANY of the cgi's:
Premature end
[EMAIL PROTECTED] schrieb am 04.01.2006 18:40:10:
Doing rpm -q nagios shows nagios-1.2-2.1.el3.rf
How do I remove that?
Doing rpm -e nagios
Shows:
error reading information on service nagios: No such file or directory
error: %preun(nagios-1.2-2.1.el3.rf) scriptlet failed, exit status
[EMAIL PROTECTED] schrieb am 05.01.2006 10:56:11:
Is it seen as recommended behaviour to use Antwort: instead of Re:?
Especially when sending mail to a mailing list that runs in english?
SCNR ;-)
I didn't take any offense ;)
But it's not something I can do anything about.
Lotus Notes sets
[EMAIL PROTECTED] schrieb am
20.03.2006 16:01:10:
I am using check_ssh to check if the ssh is runing on some hosts.
On a number of hosts the check is running ok, on others I am
getting check_ssh: Could not parse arguments. I can log on using
ssh that are giving me the parsing error.
Can
Gordon Stewart [EMAIL PROTECTED] schrieb am
20.03.2006 16:23:22:
The command line I am having the trouble with is
define command{
command_name check_ssh
command_line $USER1$/check_ssh
-t 10 -p 99 $HOSTADDRESS$
}
As I said it works with some hosts but not all hosts.
[EMAIL PROTECTED] stucky]# /usr/local/nagios/libexec/check_dig -w 1 -c 2 -H
{nameserver} -l {fqdn} -a {ip}
DNS WARNING - 0.011 seconds response time ({fqdn} 38400 IN A
{ip})|time=0.
011227s;1.00;2.00;0.00
Have I totally gone nuts or did I not just tell check_dig to only warn
[EMAIL PROTECTED] schrieb am 17.05.2006 20:09:16:
I am still butting up against very high latency issues with my Nagios
setup. I feel like I must be missing something obvious because it
doesn't seem like I have so many services that the servers cannot keep
up.
nag2: 193/1743
Machine
(repost from nagios-devel)
Hi folks,
I'm currently using Nagios 2.0b3 (never change a running system ;)) and
ran into the following problem:
Service went critical
SMS and emails got dispatched
found problem, decided to reboot the machine to fix it
scheduled downtime for host
rebooted host
[EMAIL PROTECTED] schrieb am 31.07.2006 19:42:08:
Pardon me. But what is the problem? You have a problem. It triggers an
alert. You act and 'fix' it by scheduling downtime. Then you bring the
system alive within the allocated maintenance window.
I'm sorry, but I got a hard time to pardon such
[EMAIL PROTECTED] schrieb am 02.08.2006 18:04:06:
The problem is that it sounds like you're using scheduled downtimes
incorrectly. It's not meant to be used for *un*scheduled downtimes; thus
the name. It's meant to supress alerts from a machine during the
specified window, and that's exactly
[EMAIL PROTECTED] schrieb am 02.08.2006 18:36:18:
I think you might want to rethink your process so that it matches the
paradigm of the tool you are using. It already can do what you want if
you just work with the way it was designed, rather than forcing a
process that breaks the paradigm.
I
[EMAIL PROTECTED] schrieb am 02.08.2006 18:42:56:
Or you could temporarily disable notifications for the host during the
reboot. The Nagios docs are pretty clear that [w]hen a host a service
is in a period of scheduled downtime, notifications for that host or
service will be suppressed.
[EMAIL PROTECTED] schrieb am 02.09.2006 18:06:47:
To make things clearer, the setup I'm proposing is this:
1. # /usr/local/sbin/visudo
...
nagios ALL=(ALL) NOPASSWD: /usr/local/nagios/libexec/check_logfiles -f
/usr/local/nagios/etc/check_logfiles.cfg
2. # vi
[EMAIL PROTECTED] schrieb am 18.10.2006 04:26:19:
/usr/bin/printf %b * Nagios *\n\nNotification Type:
$NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress:
$HOSTADDRESS$\n$HOSTNOTES$\n\nInfo: $HOSTOUTPUT$\n\nDate/Time:
$LONGDATETIME$\n | /usr/bin/mail -s Host $HOSTSTATE$
[EMAIL PROTECTED] schrieb am 19.10.2006 11:04:19:
I am monitoring some hosts on the Internet for informational reasons.
Since these hosts quite frequently have failed services, I'd like my
Nagios to refrain from notifying me if a service is down at the first
notification. Subsequent
[EMAIL PROTECTED] schrieb am 19.10.2006 11:08:58:
Hi,
in the Nagios 2.x docs, a serviceescalation item can be configured for
a host name and a service description. Is there any possibility to
define escalation items that automatically apply for all members of a
service group?
Example:
18 matches
Mail list logo
