Hello everybody,
When I am testing nagios with nagios -v I have a warning with this message
that I don't understand :
Warning: Nothing specified for illegal_macro_output_chars variable!
Have a good year
Jean Frontin
System team
I R I T
Université Paul-Sabatier
118, rte de Narbonne
31062
Jean Frontin wrote:
When I am testing nagios with nagios -v I have a warning with this
message that I don't understand :
Warning: Nothing specified for illegal_macro_output_chars variable!
Have a look at the docs...
Hi,
I have setup
dependencies which all seem to work fine to a point.
Example : I have 1
host with 3 services
HOST A
|
Service
A(master service)
|
---
||
Service
BService
C
If service A
fails, checks and notifications are suppressed for Service B and
-Original Message-
From: [EMAIL PROTECTED] [mailto:nagios-users-
[EMAIL PROTECTED] On Behalf Of Greg Martin
Sent: Friday, January 06, 2006 9:06 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check spamhaus lasso
I would like to use check_http or similar
Does anyone have other recommendations for web-based Nagios
configuration besides fruity, monarch, or creating my own? Fruity
doesn't want to import my escalations or my generic host/service
template and monarch gives me an error about not being able to create
the table it wants to create in the
Hi,
I have setup
dependencies which all seem to work fine to a point.
Example : I have 1
host with 3 services
HOST A
|
Service
A(master service)
|
---
||
Service
BService
C
If service A
fails, checks and notifications are suppressed for Service B and
host check_command from the command line as the nagios user you may
see additional information. If you're
not running the latest plugins, upgrade and/or try using check_icmp
instead. If you search the archives
for /bin/ping -n (use the quotes) you'll see similar instances of
notifications not
If Service B happens to be queued to be checked before Service A is, you'll
get notified of it's problem first, so that's why it's only sometimes that
you get this behavior.
As for simple solution to your question, increase the max_check_attempts of
Service B/C, so that Service A will error out
On a downed host, ping service alerts will get suppressed by host
alerts if you're also using ping to
check the host.
If you're using the standard ping-based check_host_alive, you should
only get ping-service problem
notifications when the host is still pingable but packetloss/RTT is in
In order to try to diagnose the nagios problem whereby it enteres the
wait state indefinitely, i added some debugging code to commands.c, and
rebuilt nagios 2.0rc1. I am now getting a very strange error
/Warning: Attempting to execute the command /check_ping -H 4400::34 -w
3000.0,80% -c
I have Nagios configured to send notifications after 4 CRITICAL service
checks. However, if the service check returns socket timeout, Nagios
immediately sends the page without doing another 3 checks.
Google searches and searching the documentation/FAQ for socket timeout
only explain what the
Hi, list i know this question has been repeated many times on this list
but I still need your help and suggestion.
Here is the related text from nagios FAQ..
#Nagios command obj
# 'host-notify-by-gnokii' command definition
define command{
command_name host-notify-by-gnokii
[EMAIL PROTECTED] wrote:
Hi,
define serviceescalation{
host_name xxx01
service_description check_http
first_notification 1
** last_notification 60**
notification_interval 10
contact_groups Admins
escalation_period
13 matches
Mail list logo