Bonjour,

Je suis entrain d'essayer d'installer Centreon mais j'ai une erreur sur au lancement du script ndo2db (/etc/init.d/ndo2db) :

-bash: /etc/init.d/ndo2db: /bin/sh^M: Bad Interpreter : Aucun fichier ou répertoire de ce type.

Pourtant j'ai recopié le script qui était sur le site et modifié les droits mais je ne vois pas trop mon problème!

Merci, c'est bon! Je continue le tutorial!

En tout cas, tu es trés réactif! Merci!

Aprés Analyse de mon problème, il semblerait qu'il y ait un probleme avec Ndo qui ne met pas d'information dans la base mysql!
Il me renvoit dans le log nagios :

ndomod: Error writing to data sink! Some output may get lost...

J'ai essayé de changer udp en tcp sur les deux fichiers de configurations ndomod.cfg et ndo2db.cfg mais aucun changement!

Si qq'un à une idée je suis preneur!

@Nico: voici le lien sur le wiki pour la partie concernant la base NDO spécifique Centreon.
http://fr.doc.centreon.com/Setup_Fedora_core_8:installation_bdd_ndo/fr

En fait, pour la partie BDD Centreon/CentStorage, tout ceci est effectué dans le Wizard, mais pour la partie NDO c'est un script supplémentaire.
Note: http://trac.centreon.com/browser/branches/centreon-2.0/www/install/createNDODB.sql , il y a une table supplémentaire pour la gestion des ACL via Centreon.

@Marc: Je t'invite a venir sur le forum forum.centreon.com pour les problèmes (surement plus simple a suivre que via le service commentaire du blog (sans vouloir faire fuir les lecteurs :p) )

Finalement, pour ceux que ca pourrait aider, j'ai trouver mon problème.

Déjà pour commencer, il faut penser à bien désinstaller Ndoutils pour éviter d'avoir une installation pas trés propre avec cette commande :

make distclean

Ensuite lors de l'installation il faut préciser qu'il ne faut pas de postgreSQL si on n'en utilise pas (ce qui est d'ailleurs le cas ici! :p)

./configure --prefix=/usr/local/nagios/ --enable-mysql --disable-pgsql --with-mysql-lib=/usr/lib/mysql/

Voila voila, aprés on modifie les fichiers de conf de ndoutils comme indiqué dans le blog de nico et c'est bon.

J'espere ca servira à quelqu'un!

Bonsoir,

Installation de NDOUTILS

J'ai suivi votre process

Je n'ai pas le fichier ndo2db dans le répertoire etc/init.d mais je l'ai dans usr/local/nagois/bin.

Je n'arrive pas à le transférer dans le répertoire etc/init.d

Merci d'avance pour votre aide

Bonjour,

Petit soucis lors du démarrage de ndo2db!
Lorsque je lance la commande /etc/init.d/ndo2db start j'ai le message suivant:

starting ndo:support for the specified database server is either not yet supported, or not found on your system.
done.

j'ai suivis le tutoriel à la lettre
D'où peu venir le soucis?

Merci d'avance!

Bonjour apres l'installation de la base ndo nagios m'affichge des erreurs lorsque je le redemarre. Voici ce que ça affiche:
root@das-desktop:/usr/local/centreon-2.0# /etc/init.d/nagios restart
Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration.
sinon voici la config de nagios.cfg:
##############################################################################
#
# NAGIOS.CFG - Sample Main Config File for Nagios 3.0.6
#
# Read the documentation for more information on this configuration
# file. I've provided some comments here, but things may not be so
# clear without further explanation.
#
# Last Modified: 10-15-2008
#
##############################################################################

# LOG FILE
# This is the main log file where service and host events are logged
# for historical purposes. This should be the first option specified
# in the config file!!!

log_file=/usr/local/nagios/var/nagios.log

# OBJECT CONFIGURATION FILE(S)
# These are the object configuration files in which you define hosts,
# host groups, contacts, contact groups, services, etc.
# You can split your object definitions across several config files
# if you wish (as shown below), or keep them all in a single config file.

# You can specify individual object config files as shown below:
cfg_file=/usr/local/nagios/etc/objects/commands.cfg
cfg_file=/usr/local/nagios/etc/objects/contacts.cfg
cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/objects/templates.cfg

# Definitions for monitoring the local (Linux) host
cfg_file=/usr/local/nagios/etc/objects/localhost.cfg

# Definitions for monitoring a Windows machine
#cfg_file=/usr/local/nagios/etc/objects/windows.cfg

# Definitions for monitoring a router/switch
#cfg_file=/usr/local/nagios/etc/objects/switch.cfg

# Definitions for monitoring a network printer
#cfg_file=/usr/local/nagios/etc/objects/printer.cfg

# You can also tell Nagios to process all config files (with a .cfg
# extension) in a particular directory by using the cfg_dir
# directive as shown below:

#cfg_dir=/usr/local/nagios/etc/servers
#cfg_dir=/usr/local/nagios/etc/printers
#cfg_dir=/usr/local/nagios/etc/switches
#cfg_dir=/usr/local/nagios/etc/routers

# OBJECT CACHE FILE
# This option determines where object definitions are cached when
# Nagios starts/restarts. The CGIs read object definitions from
# this cache file (rather than looking at the object config files
# directly) in order to prevent inconsistencies that can occur
# when the config files are modified after Nagios starts.

object_cache_file=/usr/local/nagios/var/objects.cache

# PRE-CACHED OBJECT FILE
# This options determines the location of the precached object file.
# If you run Nagios with the -p command line option, it will preprocess
# your object configuration file(s) and write the cached config to this
# file. You can then start Nagios with the -u option to have it read
# object definitions from this precached file, rather than the standard
# object configuration files (see the cfg_file and cfg_dir options above).
# Using a precached object file can speed up the time needed to (re)start
# the Nagios process if you've got a large and/or complex configuration.
# Read the documentation section on optimizing Nagios to find our more
# about how this feature works.

precached_object_file=/usr/local/nagios/var/objects.precache

# RESOURCE FILE
# This is an optional resource file that contains $USERx$ macro
# definitions. Multiple resource files can be specified by using
# multiple resource_file definitions. The CGIs will not attempt to
# read the contents of resource files, so information that is
# considered to be sensitive (usernames, passwords, etc) can be
# defined as macros in this file and restrictive permissions (600)
# can be placed on this file.

resource_file=/usr/local/nagios/etc/resource.cfg

# STATUS FILE
# This is where the current status of all monitored services and
# hosts is stored. Its contents are read and processed by the CGIs.
# The contents of the status file are deleted every time Nagios
# restarts.

status_file=/usr/local/nagios/var/status.dat

# STATUS FILE UPDATE INTERVAL
# This option determines the frequency (in seconds) that
# Nagios will periodically dump program, host, and
# service status data.

status_update_interval=10

# NAGIOS USER
# This determines the effective user that Nagios should run as.
# You can either supply a username or a UID.

nagios_user=nagios

# NAGIOS GROUP
# This determines the effective group that Nagios should run as.
# You can either supply a group name or a GID.

nagios_group=nagios

# EXTERNAL COMMAND OPTION
# This option allows you to specify whether or not Nagios should check
# for external commands (in the command file defined below). By default
# Nagios will *not* check for external commands, just to be on the
# cautious side. If you want to be able to use the CGI command interface
# you will have to enable this.
# Values: 0 = disable commands, 1 = enable commands

check_external_commands=1

# EXTERNAL COMMAND CHECK INTERVAL
# This is the interval at which Nagios should check for external commands.
# This value works of the interval_length you specify later. If you leave
# that at its default value of 60 (seconds), a value of 1 here will cause
# Nagios to check for external commands every minute. If you specify a
# number followed by an "s" (i.e. 15s), this will be interpreted to mean
# actual seconds rather than a multiple of the interval_length variable.
# Note: In addition to reading the external command file at regularly
# scheduled intervals, Nagios will also check for external commands after
# event handlers are executed.
# NOTE: Setting this value to -1 causes Nagios to check the external
# command file as often as possible.

#command_check_interval=15s
command_check_interval=-1

# EXTERNAL COMMAND FILE
# This is the file that Nagios checks for external command requests.
# It is also where the command CGI will write commands that are submitted
# by users, so it must be writeable by the user that the web server
# is running as (usually 'nobody'). Permissions should be set at the
# directory level instead of on the file, as the file is deleted every
# time its contents are processed.

command_file=/usr/local/nagios/var/rw/nagios.cmd

# EXTERNAL COMMAND BUFFER SLOTS
# This settings is used to tweak the number of items or "slots" that
# the Nagios daemon should allocate to the buffer that holds incoming
# external commands before they are processed. As external commands
# are processed by the daemon, they are removed from the buffer.

external_command_buffer_slots=4096

# LOCK FILE
# This is the lockfile that Nagios will use to store its PID number
# in when it is running in daemon mode.

lock_file=/usr/local/nagios/var/nagios.lock

# TEMP FILE
# This is a temporary file that is used as scratch space when Nagios
# updates the status log, cleans the comment file, etc. This file
# is created, used, and deleted throughout the time that Nagios is
# running.

temp_file=/usr/local/nagios/var/nagios.tmp

# TEMP PATH
# This is path where Nagios can create temp files for service and
# host check results, etc.

temp_path=/tmp

# EVENT BROKER OPTIONS
# Controls what (if any) data gets sent to the event broker.
# Values: 0 = Broker nothing
# -1 = Broker everything
# = See documentation

event_broker_options=-1

# EVENT BROKER MODULE(S)
# This directive is used to specify an event broker module that should
# by loaded by Nagios at startup. Use multiple directives if you want
# to load more than one module. Arguments that should be passed to
# the module at startup are seperated from the module path by a space.
#
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#
# Do NOT overwrite modules while they are being used by Nagios or Nagios
# will crash in a fiery display of SEGFAULT glory. This is a bug/limitation
# either in dlopen(), the kernel, and/or the filesystem. And maybe Nagios...
#
# The correct/safe way of updating a module is by using one of these methods:
# 1. Shutdown Nagios, replace the module file, restart Nagios
# 2. Delete the original module file, move the new module file into place, restart Nagios
#
# Example:
#
# broker_module= [moduleargs]

#broker_module=/somewhere/module1.o
#broker_module=/somewhere/module2.o arg1 arg2=3 debug=o
broker_module=/usr/local/nagios/bin/ndomod.o
config_file=/usr/local/nagios/etc/ndomod.cfg

# LOG ROTATION METHOD
# This is the log rotation method that Nagios should use to rotate
# the main log file. Values are as follows..
# n = None - don't rotate the log
# h = Hourly rotation (top of the hour)
# d = Daily rotation (midnight every day)
# w = Weekly rotation (midnight on Saturday evening)
# m = Monthly rotation (midnight last day of month)

log_rotation_method=d

# LOG ARCHIVE PATH
# This is the directory where archived (rotated) log files should be
# placed (assuming you've chosen to do log rotation).

log_archive_path=/usr/local/nagios/var/archives

# LOGGING OPTIONS
# If you want messages logged to the syslog facility, as well as the
# Nagios log file set this option to 1. If not, set it to 0.

use_syslog=1

# NOTIFICATION LOGGING OPTION
# If you don't want notifications to be logged, set this value to 0.
# If notifications should be logged, set the value to 1.

log_notifications=1

# SERVICE RETRY LOGGING OPTION
# If you don't want service check retries to be logged, set this value
# to 0. If retries should be logged, set the value to 1.

log_service_retries=1

# HOST RETRY LOGGING OPTION
# If you don't want host check retries to be logged, set this value to
# 0. If retries should be logged, set the value to 1.

log_host_retries=1

# EVENT HANDLER LOGGING OPTION
# If you don't want host and service event handlers to be logged, set
# this value to 0. If event handlers should be logged, set the value
# to 1.

log_event_handlers=1

# INITIAL STATES LOGGING OPTION
# If you want Nagios to log all initial host and service states to
# the main log file (the first time the service or host is checked)
# you can enable this option by setting this value to 1. If you
# are not using an external application that does long term state
# statistics reporting, you do not need to enable this option. In
# this case, set the value to 0.

log_initial_states=0

# EXTERNAL COMMANDS LOGGING OPTION
# If you don't want Nagios to log external commands, set this value
# to 0. If external commands should be logged, set this value to 1.
# Note: This option does not include logging of passive service
# checks - see the option below for controlling whether or not
# passive checks are logged.

log_external_commands=1

# PASSIVE CHECKS LOGGING OPTION
# If you don't want Nagios to log passive host and service checks, set
# this value to 0. If passive checks should be logged, set
# this value to 1.

log_passive_checks=1

# GLOBAL HOST AND SERVICE EVENT HANDLERS
# These options allow you to specify a host and service event handler
# command that is to be run for every host or service state change.
# The global event handler is executed immediately prior to the event
# handler that you have optionally specified in each host or
# service definition. The command argument is the short name of a
# command definition that you define in your host configuration file.
# Read the HTML docs for more information.

#global_host_event_handler=somecommand
#global_service_event_handler=somecommand

# SERVICE INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" service checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all service checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)! This is not a
# good thing for production, but is useful when testing the
# parallelization functionality.
# n = None - don't use any delay between checks
# d = Use a "dumb" delay of 1 second between checks
# s = Use "smart" inter-check delay calculation
# x.xx = Use an inter-check delay of x.xx seconds

service_inter_check_delay_method=s

# MAXIMUM SERVICE CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all services should
# be completed. Default is 30 minutes.

max_service_check_spread=30

# SERVICE CHECK INTERLEAVE FACTOR
# This variable determines how service checks are interleaved.
# Interleaving the service checks allows for a more even
# distribution of service checks and reduced load on remote
# hosts. Setting this value to 1 is equivalent to how versions
# of Nagios previous to 0.0.5 did service checks. Set this
# value to s (smart) for automatic calculation of the interleave
# factor unless you have a specific reason to change it.
# s = Use "smart" interleave factor calculation
# x = Use an interleave factor of x, where x is a
# number greater than or equal to 1.

service_interleave_factor=s

# HOST INTER-CHECK DELAY METHOD
# This is the method that Nagios should use when initially
# "spreading out" host checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all host checks out evenly to minimize CPU load.
# Using the dumb setting will cause all checks to be scheduled
# at the same time (with no delay between them)!
# n = None - don't use any delay between checks
# d = Use a "dumb" delay of 1 second between checks
# s = Use "smart" inter-check delay calculation
# x.xx = Use an inter-check delay of x.xx seconds

host_inter_check_delay_method=s

# MAXIMUM HOST CHECK SPREAD
# This variable determines the timeframe (in minutes) from the
# program start time that an initial check of all hosts should
# be completed. Default is 30 minutes.

max_host_check_spread=30

# MAXIMUM CONCURRENT SERVICE CHECKS
# This option allows you to specify the maximum number of
# service checks that can be run in parallel at any given time.
# Specifying a value of 1 for this variable essentially prevents
# any service checks from being parallelized. A value of 0
# will not restrict the number of concurrent checks that are
# being executed.

max_concurrent_checks=0

# HOST AND SERVICE CHECK REAPER FREQUENCY
# This is the frequency (in seconds!) that Nagios will process
# the results of host and service checks.

check_result_reaper_frequency=10

# MAX CHECK RESULT REAPER TIME
# This is the max amount of time (in seconds) that a single
# check result reaper event will be allowed to run before
# returning control back to Nagios so it can perform other
# duties.

max_check_result_reaper_time=30

# CHECK RESULT PATH
# This is directory where Nagios stores the results of host and
# service checks that have not yet been processed.
#
# Note: Make sure that only one instance of Nagios has access
# to this directory!

check_result_path=/usr/local/nagios/var/spool/checkresults

# MAX CHECK RESULT FILE AGE
# This option determines the maximum age (in seconds) which check
# result files are considered to be valid. Files older than this
# threshold will be mercilessly deleted without further processing.

max_check_result_file_age=3600

# CACHED HOST CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous host check is considered current.
# Cached host states (from host checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to the host check logic.
# Too high of a value for this option may result in inaccurate host
# states being used by Nagios, while a lower value may result in a
# performance hit for host checks. Use a value of 0 to disable host
# check caching.

cached_host_check_horizon=15

# CACHED SERVICE CHECK HORIZON
# This option determines the maximum amount of time (in seconds)
# that the state of a previous service check is considered current.
# Cached service states (from service checks that were performed more
# recently that the timeframe specified by this value) can immensely
# improve performance in regards to predictive dependency checks.
# Use a value of 0 to disable service check caching.

cached_service_check_horizon=15

# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of hosts when it predicts that future dependency logic test
# may be needed. These predictive checks can help ensure that your
# host dependency logic works well.
# Values:
# 0 = Disable predictive checks
# 1 = Enable predictive checks (default)

enable_predictive_host_dependency_checks=1

# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
# This option determines whether or not Nagios will attempt to execute
# checks of service when it predicts that future dependency logic test
# may be needed. These predictive checks can help ensure that your
# service dependency logic works well.
# Values:
# 0 = Disable predictive checks
# 1 = Enable predictive checks (default)

enable_predictive_service_dependency_checks=1

# SOFT STATE DEPENDENCIES
# This option determines whether or not Nagios will use soft state
# information when checking host and service dependencies. Normally
# Nagios will only use the latest hard host or service state when
# checking dependencies. If you want it to use the latest state (regardless
# of whether its a soft or hard state type), enable this option.
# Values:
# 0 = Don't use soft state dependencies (default)
# 1 = Use soft state dependencies

soft_state_dependencies=0

# TIME CHANGE ADJUSTMENT THRESHOLDS
# These options determine when Nagios will react to detected changes
# in system time (either forward or backwards).

#time_change_threshold=900

# AUTO-RESCHEDULING OPTION
# This option determines whether or not Nagios will attempt to
# automatically reschedule active host and service checks to
# "smooth" them out over time. This can help balance the load on
# the monitoring server.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_reschedule_checks=0

# AUTO-RESCHEDULING INTERVAL
# This option determines how often (in seconds) Nagios will
# attempt to automatically reschedule checks. This option only
# has an effect if the auto_reschedule_checks option is enabled.
# Default is 30 seconds.
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_interval=30

# AUTO-RESCHEDULING WINDOW
# This option determines the "window" of time (in seconds) that
# Nagios will look at when automatically rescheduling checks.
# Only host and service checks that occur in the next X seconds
# (determined by this variable) will be rescheduled. This option
# only has an effect if the auto_reschedule_checks option is
# enabled. Default is 180 seconds (3 minutes).
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY

auto_rescheduling_window=180

# SLEEP TIME
# This is the number of seconds to sleep between checking for system
# events and service checks that need to be run.

sleep_time=0.25

# TIMEOUT VALUES
# These options control how much time Nagios will allow various
# types of commands to execute before killing them off. Options
# are available for controlling maximum time allotted for
# service checks, host checks, event handlers, notifications, the
# ocsp command, and performance data commands. All values are in
# seconds.

service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
notification_timeout=30
ocsp_timeout=5
perfdata_timeout=5

# RETAIN STATE INFORMATION
# This setting determines whether or not Nagios will save state
# information for services and hosts before it shuts down. Upon
# startup Nagios will reload all saved service and host state
# information before starting to monitor. This is useful for
# maintaining long-term data on state statistics, etc, but will
# slow Nagios down a bit when it (re)starts. Since its only
# a one-time penalty, I think its well worth the additional
# startup delay.

retain_state_information=1

# STATE RETENTION FILE
# This is the file that Nagios should use to store host and
# service state information before it shuts down. The state
# information in this file is also read immediately prior to
# starting to monitor the network when Nagios is restarted.
# This file is used only if the preserve_state_information
# variable is set to 1.

state_retention_file=/usr/local/nagios/var/retention.dat

# RETENTION DATA UPDATE INTERVAL
# This setting determines how often (in minutes) that Nagios
# will automatically save retention data during normal operation.
# If you set this value to 0, Nagios will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting. If you have disabled
# state retention, this option has no effect.

retention_update_interval=60

# USE RETAINED PROGRAM STATE
# This setting determines whether or not Nagios will set
# program status variables based on the values saved in the
# retention file. If you want to use retained program status
# information, set this value to 1. If not, set this value
# to 0.

use_retained_program_state=1

# USE RETAINED SCHEDULING INFO
# This setting determines whether or not Nagios will retain
# the scheduling info (next check time) for hosts and services
# based on the values saved in the retention file. If you
# If you want to use retained scheduling info, set this
# value to 1. If not, set this value to 0.

use_retained_scheduling_info=1

# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
# The following variables are used to specify specific host and
# service attributes that should *not* be retained by Nagios during
# program restarts.
#
# The values of the masks are bitwise ANDs of values specified
# by the "MODATTR_" definitions found in include/common.h.
# For example, if you do not want the current enabled/disabled state
# of flap detection and event handlers for hosts to be retained, you
# would use a value of 24 for the host attribute mask...
# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24

# This mask determines what host attributes are not retained
retained_host_attribute_mask=0

# This mask determines what service attributes are not retained
retained_service_attribute_mask=0

# These two masks determine what process attributes are not retained.
# There are two masks, because some process attributes have host and service
# options. For example, you can disable active host checks, but leave active
# service checks enabled.
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0

# These two masks determine what contact attributes are not retained.
# There are two masks, because some contact attributes have host and
# service options. For example, you can disable host notifications for
# a contact, but leave service notifications enabled for them.
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0

# INTERVAL LENGTH
# This is the seconds per unit interval as used in the
# host/contact/service configuration files. Setting this to 60 means
# that each interval is one minute long (60 seconds). Other settings
# have not been tested much, so your mileage is likely to vary...

interval_length=60

# AGGRESSIVE HOST CHECKING OPTION
# If you don't want to turn on aggressive host checking features, set
# this value to 0 (the default). Otherwise set this value to 1 to
# enable the aggressive check option. Read the docs for more info
# on what aggressive host check is or check out the source code in
# base/checks.c

use_aggressive_host_checking=0

# SERVICE CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# service checks when it initially starts. If this option is
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of service checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_service_checks=1

# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# service checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_service_checks=1

# HOST CHECK EXECUTION OPTION
# This determines whether or not Nagios will actively execute
# host checks when it initially starts. If this option is
# disabled, checks are not actively made, but Nagios can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of host checks, leave this enabled!
# Values: 1 = enable checks, 0 = disable checks

execute_host_checks=1

# PASSIVE HOST CHECK ACCEPTANCE OPTION
# This determines whether or not Nagios will accept passive
# host checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks

accept_passive_host_checks=1

# NOTIFICATIONS OPTION
# This determines whether or not Nagios will sent out any host or
# service notifications when it is initially (re)started.
# Values: 1 = enable notifications, 0 = disable notifications

enable_notifications=1

# EVENT HANDLER USE OPTION
# This determines whether or not Nagios will run any host or
# service event handlers when it is initially (re)started. Unless
# you're implementing redundant hosts, leave this option enabled.
# Values: 1 = enable event handlers, 0 = disable event handlers

enable_event_handlers=1

# PROCESS PERFORMANCE DATA OPTION
# This determines whether or not Nagios will process performance
# data returned from service and host checks. If this option is
# enabled, host performance data will be processed using the
# host_perfdata_command (defined below) and service performance
# data will be processed using the service_perfdata_command (also
# defined below). Read the HTML docs for more information on
# performance data.
# Values: 1 = process performance data, 0 = do not process performance data

process_performance_data=0

# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed. These commands are executed only if the
# enable_performance_data option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on performance data.

#host_perfdata_command=process-host-perfdata
#service_perfdata_command=process-service-perfdata

# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
# enable_performance_data option (above) is set to 1.

#host_perfdata_file=/tmp/host-perfdata
#service_perfdata_file=/tmp/service-perfdata

# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
# These options determine what data is written (and how) to the
# performance data files. The templates may contain macros, special
# characters (\t for tab, \r for carriage return, \n for newline)
# and plain text. A newline is automatically added after each write
# to the performance data file. Some examples of what you can do are
# shown below.

#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$

# HOST AND SERVICE PERFORMANCE DATA FILE MODES
# This option determines whether or not the host and service
# performance data files are opened in write ("w") or append ("a")
# mode. If you want to use named pipes, you should use the special
# pipe ("p") mode which avoid blocking at startup, otherwise you will
# likely want the defult append ("a") mode.

#host_perfdata_file_mode=a
#service_perfdata_file_mode=a

# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
# These options determine how often (in seconds) the host and service
# performance data files are processed using the commands defined
# below. A value of 0 indicates the files should not be periodically
# processed.

#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0

# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
# These commands are used to periodically process the host and
# service performance data files. The interval at which the
# processing occurs is determined by the options above.

#host_perfdata_file_processing_command=process-host-perfdata-file
#service_perfdata_file_processing_command=process-service-perfdata-file

# OBSESS OVER SERVICE CHECKS OPTION
# This determines whether or not Nagios will obsess over service
# checks and run the ocsp_command defined below. Unless you're
# planning on implementing distributed monitoring, do not enable
# this option. Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over services, 0 = do not obsess (default)

obsess_over_services=0

# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
# This is the command that is run for every service check that is
# processed by Nagios. This command is executed only if the
# obsess_over_services option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ocsp_command=somecommand

# OBSESS OVER HOST CHECKS OPTION
# This determines whether or not Nagios will obsess over host
# checks and run the ochp_command defined below. Unless you're
# planning on implementing distributed monitoring, do not enable
# this option. Read the HTML docs for more information on
# implementing distributed monitoring.
# Values: 1 = obsess over hosts, 0 = do not obsess (default)

obsess_over_hosts=0

# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
# This is the command that is run for every host check that is
# processed by Nagios. This command is executed only if the
# obsess_over_hosts option (above) is set to 1. The command
# argument is the short name of a command definition that you
# define in your host configuration file. Read the HTML docs for
# more information on implementing distributed monitoring.

#ochp_command=somecommand

# TRANSLATE PASSIVE HOST CHECKS OPTION
# This determines whether or not Nagios will translate
# DOWN/UNREACHABLE passive host check results into their proper
# state for this instance of Nagios. This option is useful
# if you have distributed or failover monitoring setup. In
# these cases your other Nagios servers probably have a different
# "view" of the network, with regards to the parent/child relationship
# of hosts. If a distributed monitoring server thinks a host
# is DOWN, it may actually be UNREACHABLE from the point of
# this Nagios instance. Enabling this option will tell Nagios
# to translate any DOWN or UNREACHABLE host states it receives
# passively into the correct state from the view of this server.
# Values: 1 = perform translation, 0 = do not translate (default)

translate_passive_host_checks=0

# PASSIVE HOST CHECKS ARE SOFT OPTION
# This determines whether or not Nagios will treat passive host
# checks as being HARD or SOFT. By default, a passive host check
# result will put a host into a HARD state type. This can be changed
# by enabling this option.
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT

passive_host_checks_are_soft=0

# ORPHANED HOST/SERVICE CHECK OPTIONS
# These options determine whether or not Nagios will periodically
# check for orphaned host service checks. Since service checks are
# not rescheduled until the results of their previous execution
# instance are processed, there exists a possibility that some
# checks may never get rescheduled. A similar situation exists for
# host checks, although the exact scheduling details differ a bit
# from service checks. Orphaned checks seem to be a rare
# problem and should not happen under normal circumstances.
# If you have problems with service checks never getting
# rescheduled, make sure you have orphaned service checks enabled.
# Values: 1 = enable checks, 0 = disable checks

check_for_orphaned_services=1
check_for_orphaned_hosts=1

# SERVICE FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of service results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_service_freshness=1

# SERVICE FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of service check results. If you have
# disabled service freshness checking, this option has no effect.

service_freshness_check_interval=60

# HOST FRESHNESS CHECK OPTION
# This option determines whether or not Nagios will periodically
# check the "freshness" of host results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# Values: 1 = enabled freshness checking, 0 = disable freshness checking

check_host_freshness=0

# HOST FRESHNESS CHECK INTERVAL
# This setting determines how often (in seconds) Nagios will
# check the "freshness" of host check results. If you have
# disabled host freshness checking, this option has no effect.

host_freshness_check_interval=60

# ADDITIONAL FRESHNESS THRESHOLD LATENCY
# This setting determines the number of seconds that Nagios
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).

additional_freshness_latency=15

# FLAP DETECTION OPTION
# This option determines whether or not Nagios will try
# and detect hosts and services that are "flapping".
# Flapping occurs when a host or service changes between
# states too frequently. When Nagios detects that a
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping. Flap detection is very experimental, so read
# the HTML documentation before enabling this feature!
# Values: 1 = enable flap detection
# 0 = disable flap detection (default)

enable_flap_detection=1

# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
# Read the HTML documentation on flap detection for
# an explanation of what this option does. This option
# has no effect if flap detection is disabled.

low_service_flap_threshold=5.0
high_service_flap_threshold=20.0
low_host_flap_threshold=5.0
high_host_flap_threshold=20.0

# DATE FORMAT OPTION
# This option determines how short dates are displayed. Valid options
# include:
# us (MM-DD-YYYY HH:MM:SS)
# euro (DD-MM-YYYY HH:MM:SS)
# iso8601 (YYYY-MM-DD HH:MM:SS)
# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
#

date_format=us

# TIMEZONE OFFSET
# This option is used to override the default timezone that this
# instance of Nagios runs in. If not specified, Nagios will use
# the system configured timezone.
#
# NOTE: In order to display the correct timezone in the CGIs, you
# will also need to alter the Apache directives for the CGI path
# to include your timezone. Example:
#
#
# SetEnv TZ "Australia/Brisbane"
# ...
#

#use_timezone=US/Mountain
#use_timezone=Australia/Brisbane

# P1.PL FILE LOCATION
# This value determines where the p1.pl perl script (used by the
# embedded Perl interpreter) is located. If you didn't compile
# Nagios with embedded Perl support, this option has no effect.

p1_file=/usr/local/nagios/bin/p1.pl

# EMBEDDED PERL INTERPRETER OPTION
# This option determines whether or not the embedded Perl interpreter
# will be enabled during runtime. This option has no effect if Nagios
# has not been compiled with support for embedded Perl.
# Values: 0 = disable interpreter, 1 = enable interpreter

enable_embedded_perl=1

# EMBEDDED PERL USAGE OPTION
# This option determines whether or not Nagios will process Perl plugins
# and scripts with the embedded Perl interpreter if the plugins/scripts
# do not explicitly indicate whether or not it is okay to do so. Read
# the HTML documentation on the embedded Perl interpreter for more
# information on how this option works.

use_embedded_perl_implicitly=1

# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# object types.

illegal_object_name_chars=`~!$%^&*|'"?,()=

# ILLEGAL MACRO OUTPUT CHARACTERS
# This option allows you to specify illegal characters that are
# stripped from macros before being used in notifications, event
# handlers, etc. This DOES NOT affect macros used in service or
# host check commands.
# The following macros are stripped of the characters you specify:
# $HOSTOUTPUT$
# $HOSTPERFDATA$
# $HOSTACKAUTHOR$
# $HOSTACKCOMMENT$
# $SERVICEOUTPUT$
# $SERVICEPERFDATA$
# $SERVICEACKAUTHOR$
# $SERVICEACKCOMMENT$

illegal_macro_output_chars=`~$&|'"

# REGULAR EXPRESSION MATCHING
# This option controls whether or not regular expression matching
# takes place in the object config files. Regular expression
# matching is used to match host, hostgroup, service, and service
# group names/descriptions in some fields of various object types.
# Values: 1 = enable regexp matching, 0 = disable regexp matching

use_regexp_matching=0

# "TRUE" REGULAR EXPRESSION MATCHING
# This option controls whether or not "true" regular expression
# matching takes place in the object config files. This option
# only has an effect if regular expression matching is enabled
# (see above). If this option is DISABLED, regular expression
# matching only occurs if a string contains wildcard characters
# (* and ?). If the option is ENABLED, regexp matching occurs
# all the time (which can be annoying).
# Values: 1 = enable true matching, 0 = disable true matching

use_true_regexp_matching=0

# ADMINISTRATOR EMAIL/PAGER ADDRESSES
# The email and pager address of a global administrator (likely you).
# Nagios never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.

admin_email=nagios@localhost
admin_pager=pagenagios@localhost

# DAEMON CORE DUMP OPTION
# This option determines whether or not Nagios is allowed to create
# a core dump when it runs as a daemon. Note that it is generally
# considered bad form to allow this, but it may be useful for
# debugging purposes. Enabling this option doesn't guarantee that
# a core file will be produced, but that's just life...
# Values: 1 - Allow core dumps
# 0 - Do not allow core dumps (default)

daemon_dumps_core=0

# LARGE INSTALLATION TWEAKS OPTION
# This option determines whether or not Nagios will take some shortcuts
# which can save on memory and CPU usage in large Nagios installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks
# 0 - Disable tweaks (default)

use_large_installation_tweaks=0

# ENABLE ENVIRONMENT MACROS
# This option determines whether or not Nagios will make all standard
# macros available as environment variables when host/service checks
# and system commands (event handlers, notifications, etc.) are
# executed. Enabling this option can cause performance issues in
# large installations, as it will consume a bit more memory and (more
# importantly) consume more CPU.
# Values: 1 - Enable environment variable macros (default)
# 0 - Disable environment variable macros

enable_environment_macros=1

# CHILD PROCESS MEMORY OPTION
# This option determines whether or not Nagios will free memory in
# child processes (processed used to execute system commands and host/
# service checks). If you specify a value here, it will override
# program defaults.
# Value: 1 - Free memory in child processes
# 0 - Do not free memory in child processes

#free_child_process_memory=1

# CHILD PROCESS FORKING BEHAVIOR
# This option determines how Nagios will fork child processes
# (used to execute system commands and host/service checks). Normally
# child processes are fork()ed twice, which provides a very high level
# of isolation from problems. Fork()ing once is probably enough and will
# save a great deal on CPU usage (in large installs), so you might
# want to consider using this. If you specify a value here, it will
# program defaults.
# Value: 1 - Child processes fork() twice
# 0 - Child processes fork() just once

#child_processes_fork_twice=1

# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file. OR values together to log multiple
# types of information.
# Values:
# -1 = Everything
# 0 = Nothing
# 1 = Functions
# 2 = Configuration
# 4 = Process information
# 8 = Scheduled events
# 16 = Host/service checks
# 32 = Notifications
# 64 = Event broker
# 128 = External commands
# 256 = Commands
# 512 = Scheduled downtime
# 1024 = Comments
# 2048 = Macros

debug_level=0

# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
# 1 = More detailed
# 2 = Very detailed

debug_verbosity=1

# DEBUG FILE
# This option determines where Nagios should write debugging information.

debug_file=/usr/local/nagios/var/nagios.debug

# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file. If
# the file grows larger than this size, it will be renamed with a .old
# extension. If a file already exists with a .old extension it will
# automatically be deleted. This helps ensure your disk space usage doesn't
# get out of control when debugging Nagios.

max_debug_file_size=1000000

voilà j'avance et maintenant mon problème est que j'ai créer comme dit dans les précédents post le fichier ndo2db dans /etc/init.d/

j'ai copié le script que NicoLargo a donnée et voilà ce qu'il m'affiche:

# /etc/init.d/ndo2db start
/etc/init.d/ndo2db: line 71: prefix: command not found
/etc/init.d/ndo2db: line 72: exec_prefix: command not found
/etc/init.d/ndo2db: line 73: prefix: command not found
/etc/init.d/ndo2db: line 74: prefix: command not found
Executable file /bin/ndo2db not found. Exiting.

quelqu'un peut m'aider ??

Salut! Nico jte te remercie d'avoir répondue a ma demande sur le précédent billet!! voila mon probleme est le suivant : je ne voie pas apparaitre mes services dans l'interface de Centréon alors qu'il son définie et visible sur l'interface de Nagios .

C'est bon j'ai trouvé, merci à plus.

Where is the RRD perl module installed [RRDs.pm]
default to [/usr/lib/perl5/RRDs.pm]
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/RRDs.pm
Path /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-mulOK
/usr/bin/rrdtool OK
/bin/mail OK

Bonjour,

moi j'ai un soucis je ne peu pas restart nagios. j'ai suivi 2 fois le tuto mais j'ai eu 2 fois la meme chose.

Je fais
# /etc/init.d/ndo2db start
s'en soucis, et ensuite quand je redémarre nagios j'obtiens:

root@ubuntu:/usr/src/ndoutils-1.4b7/db# /etc/init.d/nagios restart
Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration.

Donc j'ai tout recommencé depuis le début mais je me retrouve exactement dans la meme situation.
Comme faire?

merci d'avance

Bonjour

Mon installation s'est parfaitement déroulée, mais c'est au moment ou l'on passe en interface graphique pour la confihuration.
En effet, sur la diapo numero 4 (verifying your configuration), mon composant GD est signalé "critical" : Critical: gd.so not loaded in php.ini

Que faut-il faire pour chargé gd.so dans php.ini ?

Merci par avance

Pour Benjamin, tu n'as pas du installer la librairie php-gd...
Installe là, relance apache, et reprend le setup de Centreon.

A +

j'ai exactement le meme soucis. Quand j'ajoute un host sous centreon, je le vois bien sur l'interface de nagios mais je n'arrive pas a le faire apparaitre sous centreon.

je ne comprend pas

Bonjour, j'ai suivi le tuto à la lettre, aucun message d'erreur.

Par contre, pour l'utilisation, les services me renvoient la valeur (Null). J'ai effectué une commande de services par le terminal et il me renvoi une erreur que je ne trouve nulle part sur le net, enfin une solution... : "NET/snmp.pm". Il ne le trouve pas sur le serveur.

Voilà, si vous pouviez m'aider, merci.

J'ai essayer de réinstaller net-snmp mais le paquet existe plus, j'ai donc fait une install manuelle mais rien.

Bon bah j'ai supprimé l'ancienne version...

Par contre, maintenant j'ai un souci sur default_store.so et Dynaloader.pm

Si quelqu'un pouvait m'aider, là, je suis officiellement bloqué et sans idée...

Dernier post :

Comment je peux supprimer Centreon, NDO, NAgios pour être sûr qu'il n'y ait plus aucun fichier et pouvoir recommencer une install propre ???

sans devoir formater le système... Merci

Bonjour!

Tout d'abord merci pour ce tuto.

En suivant pas à pas les tutos j'ai un Nagios 3 et un Centreon 2 fonctionnels. Jusque là tout fonctionne bien.
Le problème est que lorsque j'importe ma configuration de Nagios dans Centreon, je n'ai plus aucun services de configurés. De même pour mes utilisateurs.
Que dois-je faire ?
Merci d'avance pour votre réponse.

Bonjour, j'ai reussi à resoudre mon premier pblm, mais un autre souci,
quand je fais un export de config j'ai ça

Nagios 3.0.6
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 12-01-2008
License: GPL

Reading configuration data...

Running pre-flight check on configuration data...

Checking services...
Checked 7 services.
Checking hosts...
Checked 1 hosts.
Checking host groups...
Checked 1 host groups.
Checking service groups...
Checked 0 service groups.
Checking contacts...
Checked 4 contacts.
Checking contact groups...
Checked 2 contact groups.
Checking service escalations...
Checked 0 service escalations.
Checking service dependencies...
Checked 0 service dependencies.
Checking host escalations...
Checked 0 host escalations.
Checking host dependencies...
Checked 0 host dependencies.
Checking commands...
Checked 54 commands.
Checking time periods...
Checked 5 time periods.
Checking for circular paths between hosts...
Checking for circular host and service dependencies...
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
- cgi.cfg - movement KO
- checkcommands.cfg - movement KO
- contactgroups.cfg - movement KO
- contacts.cfg - movement KO
- dependencies.cfg - movement KO
- escalations.cfg - movement KO
- hostextinfo.cfg - movement KO
- hostgroups.cfg - movement KO
- hosts.cfg - movement KO
- meta_commands.cfg - movement KO
- meta_contact.cfg - movement KO
- meta_contactgroup.cfg - movement KO
- meta_dependencies.cfg - movement KO
- meta_escalations.cfg - movement KO
- meta_host.cfg - movement KO
- meta_hostgroup.cfg - movement KO
- meta_services.cfg - movement KO
- meta_timeperiod.cfg - movement KO
- misccommands.cfg - movement KO
- nagios.cfg - movement KO
- ndo2db.cfg - movement KO
- ndomod.cfg - movement KO
- resource.cfg - movement KO
- serviceextinfo.cfg - movement KO
- servicegroups.cfg - movement KO
- services.cfg - movement KO
- timeperiods.cfg - movement KO

Running configuration check... CONFIG ERROR! Restart aborted. Check your Nagios configuration.

apres avoir mis a jour c'est passé sinon lors de l'etape 4 verification des composant j'ai "critical so not loaded in php.ini"
Que faire dois-je reprendre l'installation car j'ai installé gd avec xpm et desinstaller no-xpm apres l'avoir remarqué mais lorsque je met recheck il ne vois rien.
Merci d'avance.

J'ai toujours pas de reponse pour mon problème.
sinon dans les logs , j'ai ça:

ndomod: Still unable to connect to data sink. 350627 items lost, 5000 queued items to flush.

qui ne me dit pas grand chose à part que ndomod n'arrive toujours pas à se connecter.

Hello,

j'ai cette erreur :
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual thatcorresponds to your MySQL server version for the right syntax to use near '“ndopassword��' at line 1

quand je lance cette commande :
GRANT ALL ON ndo.* TO ndouser@localhost IDENTIFIED BY “ndopassword”;

Mon mysql est bien installer pourtant !?

Bonjour,
à l'installation de Centreon en suivant le script
je rencontre une erreur CRITICAL

Do you want me to create this directory ? [/usr/local/centreon/bin]
[y/n], default to [n]:
>
Directory /usr/local/centreon/bin does not exists. CRITICAL

quelqu'un a t-il une idée?
merci d'avance

Problème :

J'ai 2 serveurs identiques en configuration sous Windows server 2003.
Les check_host_alive fonctionne sur les 2 !

J'ai voulu créer un service Espace disque C pour les 2 ! Mon premier serveur fonctionne, le 2ème non... J'ai pourtant mis les IP dans la partie Sécurité SNMP sous Windows.

La commande snmpwalk ne fonctionne pas pour le second, il me met Timeout, No response ! Je le ping normalement...

Si quelqu'un a une idée, merci.

Normalement, il faut que tout se mettent à jour avec le Y, il doit en manquer un, essaye d'installer le paquet manquant, et de faire une MaJ en répondant Yes la prochaine fois qu'il te demande.

Pour le gd.so, il faut installer php5-gd, comme je le dis plus haut, quand tu installes le paquet libgd2-noxpm-dev, il désinstalle php5-gd ! Voilà pourquoi tu as le message d'erreur.

Mon problème est toujours le même.
je répond Y, le script me redemande la question.
Do you want me to install/upgrade your PEAR modules
[y/n], default to [y]:
> y
Upgrading PEAR modules
Installing PEAR modules
DB 1.7.6 NOK
DB_DataObject 1.8.4 NOK
DB_DataObject_FormBuilder 1.0.0RC4 NOK
MDB2 2.0.0 NOK
Date 1.4.6 NOK
HTML_Common 1.2.2 NOK
HTML_QuickForm 3.2.5 NOK
HTML_QuickForm_advmultiselect 1.1.0 NOK
HTML_Table 1.6.1 NOK
Auth_SASL 1.0.1 NOK
Image_GraphViz 1.1.0 NOK
Net_SMTP 1.2.8 NOK
Net_Socket 1.0.1 NOK
Net_Traceroute 0.21 NOK
Net_Ping 2.4.1 NOK
Validate 0.6.2 NOK
XML_RPC 1.4.5 NOK
SOAP 0.10.1 NOK
Log 1.9.11 NOK
Check PEAR modules
PEAR 1.5.0 1.7.1 OK
DB 1.7.6 NOK
DB_DataObject 1.8.4 NOK
DB_DataObject_FormBuilder 1.0.0RC4 NOK
MDB2 2.0.0 NOK
Date 1.4.6 NOK
HTML_Common 1.2.2 NOK
HTML_QuickForm 3.2.5 NOK
HTML_QuickForm_advmultiselect 1.1.0 NOK
HTML_Table 1.6.1 NOK
Archive_Tar 1.1 1.3.2 OK
Auth_SASL 1.0.1 NOK
Console_Getopt 1.2 1.2.3 OK
Image_GraphViz 1.1.0 NOK
Net_SMTP 1.2.8 NOK
Net_Socket 1.0.1 NOK
Net_Traceroute 0.21 NOK
Net_Ping 2.4.1 NOK
Validate 0.6.2 NOK
XML_RPC 1.4.5 NOK
SOAP 0.10.1 NOK
Log 1.9.11 NOK

Do you want me to install/upgrade your PEAR modules
[y/n], default to [y]:

de plus la derniere étape de centreon (qui dois me rediriger vers la page d 'authentification de centreon) me renvoi

Warning: require_once(DB.php) [function.require-once]: failed to open stream: No such file or directory in /usr/local/centreon/www/DBconnect.php on line 44

Fatal error: require_once() [function.require]: Failed opening required 'DB.php' (include_path='.:/usr/share/php:/usr/share/pear') in /usr/local/centreon/www/DBconnect.php on line 44

Merci pour l'aide Abdou;
Maintenant c'est bon mais j'ai reçu une erreur de connection avec le ndo que faire?

Salut Nico
Merci pour tes tutos extras!!
Juste je me permet, sa faisait 1 heure que je me prenais la tête avec sa et je risque de ne pas être le seule...
A cette ligne de ton tuto il y a une toute petite faute:

./configure --disable-pgsql —with-mysql-lib=/usr/lib/mysql --with-ndo2db-user=nagios --with-ndo2db-group=nagiosgrp

a remplacer par:

./configure --disable-pgsql --with-mysql-lib=/usr/lib/mysql --with-ndo2db-user=nagios --with-ndo2db-group=nagiosgrp

Voilà bonne continuation et encore merci pour tes tutos.

Bonjour,
Dans le cadre de mon PFE, je travail sur nagios 3.0.6 et centreon 2.0.1, l installation de ces deux dernier est faite avec succé pas de problemes, mais quand j accede a l interface de centreon, a l etape 10: Centreon Configuration File les fichier de configuration ne peuvent pas se créer j ai pas compri le probleme:

Writable Centreon Configuration File Critical: Not Writeable
(centreon.conf.php)
/usr/local/centreon/ root:root (775)
Should be apache:apache (755)

Generate Centreon configuration file Critical: Can't create file
/etc/centreon/centreon.conf.php failed to open stream:
Permission denied

Generate Centstorage configuration file Critical:Can't create
file for ODS
/etc/centreon//conf.pm failed to open stream:
Permission denied
SVP qui peu m aider j en serai vraiment très reconnaissant,
merci et bonne journée

J'ai aussi eu un problème pour monitorer le serveur supportant centreon.
J'ai du décommenter dans le fichier /etc/snmp/snmpd.conf la ligne :
com2sec readonly default public

Critical: gd.so not loaded in php.ini :

resoudre erreur : installer paquet php5-gd puis reboot

Bonjour,
Dans le cadre de mon PFE, je travail sur nagios 3.0.6 et centreon 2.0.1, l installation de ces deux dernier est faite avec succé pas de problemes, mais quand j accede a l interface de centreon, a l etape 10: Centreon Configuration File les fichier de configuration ne peuvent pas se créer j ai pas compri le probleme:

Writable Centreon Configuration File Critical: Not Writeable
(centreon.conf.php)
/usr/local/centreon/ root:root (775)
Should be apache:apache (755)

Generate Centreon configuration file Critical: Can't create file
/etc/centreon/centreon.conf.php failed to open stream:
Permission denied

Generate Centstorage configuration file Critical:Can't create
file for ODS
/etc/centreon//conf.pm failed to open stream:
Permission denied

SVP qui peu m aider j en serai vraiment très reconnaissant,
merci et bonne journée

bonjour,
je trouve pas la partie liée a mon probleme avec centreon, si tu peu nicolargo m indiquer la quel ou me donner un lien.
merci

Bonjour,

J'ai un souci lorsque je me connecte à nagios via l'interface web.
J'ai ce message lorsque je veux consulter "tactical overview, service détail..."

Whoops!

Error: Could not read host and service status information!

The most common cause of this error message (especially for new users), is the fact that Nagios is not actually running. If Nagios is indeed not running, this is a normal error message. It simply indicates that the CGIs could not obtain the current status of hosts and services that are being monitored. If you've just installed things, make sure you read the documentation on starting Nagios.

Some other things you should check in order to resolve this error include:

1. Check the Nagios log file for messages relating to startup or status data errors.
2. Always verify configuration options using the -v command-line option before starting or restarting Nagios!
3. Make sure you've compiled the main program and the CGIs to use the same status data storage options (i.e. text file or database). If the main program is storing status data in a text file and the CGIs are trying to read status data from a database, you'll have problems.

Lorsque je fais un run nagios (-v) j'ai:

Nagios 2.9
Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org)
Last Modified: 04-10-2007
License: GPL

Reading configuration data...

Error in configuration file '/var/www/apache2-default/nagios/etc/nagios.cfg' - Line 106 (UNKNOWN VARIABLE)

***> One or more problems was encountered while processing the config files...

Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.

L'erreur à la ligne 106 est: debug_level=-1

Je galère.....
Merci pour vos réponses!

Bonjour,
Dans le cadre de mon PFE, je travail sur nagios 3.0.6 et centreon 2.0.1, l installation de ces deux dernier est faite avec succé pas de problemes, mais quand j accede a l interface de centreon, a l etape 10: Centreon Configuration File les fichier de configuration ne peuvent pas se créer j ai pas compri le probleme:

Writable Centreon Configuration File Critical: Not Writeable
(centreon.conf.php)
/usr/local/centreon/ root:root (775)
Should be apache:apache (755)

Generate Centreon configuration file Critical: Can't create file
/etc/centreon/centreon.conf.php failed to open stream:
Permission denied

Generate Centstorage configuration file Critical:Can't create
file for ODS
/etc/centreon//conf.pm failed to open stream:
Permission denied
je trouve pas la partie liée a mon probleme avec centreon dans http://forum.nicolargo.com/, si tu peu Nicolargo m indiquer la quel ou me donner un lien.
merci et bonne journée

sv est ce que il ya qlq un qui m'aider svp merci de m'accorder un peu de temps

DBI connect('database=ndo;host=localhost','ndouser',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at ./installdb line 41

Bonjour à tous!
Très bien fait ces billets, je dirai comme d'habitude et s'enchainant mieux que les anciens billets...J'ai deja testé tes tutos et rien à dire mais je trouve juste dommage de ne pas intaller les applis dans un répertoire indépendant plutôt qu'un bout dans /etc un autre /var et /usr...Tout comme FAN, on a plusieurs .htaccess...Un dernier petit trucs qui peut servir à tous, avez vous essayer eyesofnetwork ?
nagios3,nagvis,cacti,nagiosbp,ged tt intégré et gestion access web par sql(+une interface web pour touts les liens avec des outils)!
Perso ça fait 3 mois que je tourne dessus et comme Fan2 est encore en beta...testez!
http://www.eyesofnetwork.com

Bonjours!
Dans un premier temps merci pour ce super turo qui m'a permit d'avancer dans mon projet.
Voila je suis étudiant et je suis en stage dans une entreprise (FAI). je doit faire une map du réseau permettant d'afficher une carte du réseau et son équipement ainsi que l'état de ses interfaces (voyant vert=up orange=problème ou surcharge rouge=down) et mettre des alarmes.
Cependant quand j'arrive dans l'étape 5 de centreon : verifying PHP PEAR Component je suis bloqué et je ne peu plus avancer. Voila ce qui s'affiche:
Component Status
PHP Version 5.x OK (ver 5.2.4-2ubuntu5.6)
PHP Extension
MySQL OK
GD Critical: gd.so not loaded in php.ini
LDAP Warning: ldap.so not loaded in php.ini
SNMP Warning: snmp.so not loaded in php.ini
XML OK
PHP-POSIX OK
PEAR OK
Writable Nagios Config Directory OK

J'ai recherché le fichier mais il reste introuvable.
(je ne suis pas habituer sous ubuntu xD)
Merci d'avance.
Amicalement D.

j'ai essayé plusieurs fois le tuto mais rien n'a faire
sous Ubuntu server et sous debian 4.0
a chaque fois que l'on génére les fichier de conf a partir de Centréon
-->Les hosts et service descende bien dans nagios mais tous les services passent en critical
--> aucun monitoring ne remonte dans centréon

des idées pour ce problème ?

bonjour, je suis en stage et mon projet est la mise en place de nagios et centreon sur le rso internet de l'entreprise
J'ai le meme soucis que hatim:
chown nagios:nagiosgrp /usr/local/nagios/bin/*
-----> chown: groupe invalide: `nagios : nagiosgrp'

merci de votre aide

Hello,

je rejoind Suilkox, le lien pour l'importation de la config nagios vers centreon ne marche plus.

Est ce qqu'un à des infos ou une méthode ? je n'ai pas trouvé grand chose sur le net.

Merci

j'ai installer centreon sous fedora 10, au demarage de centreon j'ai renconter le message d'ereur suivent :
Critical: Not Writeableapache:apache (664)
Should be nagios:apache (775)
aider moi svp

Salut Nicola, le site est très bien fait et il m'a trop aidé. Félicitation mon ami et merci infiniment.
J'ai une question qui concerne un petit probleme, j'ai suivi ton tuto de A à Z, maintenant j'ai tous les services en etat Critical et le Status Information a la valeur (null), SVP nicola j'ai besoin de votre aide, quoi faire ??

Bonjour à tous

merci pour le tuto c'est bien cool !

cependant j'ai un problème au démarrage de ndo2db :

/etc/init.d/ndo2db start
Starting ndo:chown: invalid user: `nagios:nagiosgrp'
Support for the specified database server is either not yet supported, or was not found on your system.
done.

j'ai donc un problème avec les groupes et utilisateurs propriétaires car je n'ai pas laissé nagios:nagiosgrp j'ai mis autre chose mais je ne sais pas ou aller et quoi modifier pour résoudre le problème ...

Merci d'avance

Bonjour , ça va ?? j'ai suivi ce tutoriel qui m'a beaucoup aidé, je le touve super , merci Nico , mais j'ai un problème au niveau de la connection de la base de données ndo quand je suis sur centreon / home il m'affiche toujours le message ""Connection Error to NDO DataBase ! "" , alors que j'ai fais exactement ce que vous avez fait dans votre tutoriel,
Si vous avez une solution n'hésitez pas , Merci a vous tous,
je suis en stage et j'ai comme projet de fin d'étude Nagios 3.0.2 , sous ubuntu 8.10 , sur VMware 6 ,

Bonjour,

J'ai suivie point à point le tuto.
Je n'arrive pas à configurer Centreon
J'ai toujours la ligne " Connection Error to NDO DataBase ! "
Avez vous un petit conseil à me donner

Merci d'Avance

Salut Nico,

Merci tout d'abord pour ton aide supreme concernant l'installation de Nagios.

JJ'ai suivi tres bien les etapes pour installer la base de donnees " NDO ".
Voici l'erreur que j'ai depuis la fin de mon installation:

Veuillez m'aider a m'en sortir s'il vous plait:

###########################################
root@Nagios:~# /etc/init.d/ndo2db restart
Stopping ndo: kill 29691
29697
29702
kill: 160: No such process

kill: 160: No such process

done.
Starting ndo: done.
root@Nagios:~# tail -q /var/log/syslog
Jun 29 14:27:16 Nagios nagios: ndomod: Successfully flushed 86 queued items to data sink.
Jun 29 14:27:16 Nagios ndo2db: Error: Could not connect to MySQL database: Incorrect database name 'ndo^I^I'
Jun 29 14:27:16 Nagios last message repeated 18 times
Jun 29 14:27:16 Nagios nagios: ndomod: Error writing to data sink! Some output may get lost...
Jun 29 14:27:32 Nagios nagios: ndomod: Successfully reconnected to data sink! 0 items lost, 99 queued items to flush.
Jun 29 14:27:32 Nagios nagios: ndomod: Successfully flushed 99 queued items to data sink.
Jun 29 14:27:32 Nagios ndo2db: Error: Could not connect to MySQL database: Incorrect database name 'ndo^I^I'
Jun 29 14:27:32 Nagios last message repeated 18 times
Jun 29 14:27:32 Nagios nagios: ndomod: Error writing to data sink! Some output may get lost...
Jun 29 14:27:41 Nagios ndo2db: Warning: Could not get group entry for 'nagiosgrp^I'
root@Nagios:~#

#######################################

Merci et Cordialement.
Johnny.

bonjour, j'ai un petit probleme je n'arrive pa a editer les fichier de conf suivant les commandes du tuto pourvez-vous m'aider
merci

mysqladmin -u root -p create ndo

# mysql -u root -p mysql

mysql> GRANT ALL ON ndo.* TO ndouser@localhost IDENTIFIED BY “ndopassword”;

Query OK, 0 rows affected (0.00 sec)

mysql> FLUSH PRIVILEGES;

Query OK, 0 rows affected (0.00 sec)

en gros les commande sql ne me donne aucune reponse les query ne s'affiche pas on dirait que la commande reste muet.

Avez-vous résolu le probleme de lhl_974

GRANT SELECT , INSERT , UPDATE , DELETE ON `ndo` . * TO ‘ndouser’@'localhost’ IDENTIFIED BY ‘ndopassword’;

qui renvoi comme erreur:

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"ndo" . * TO "ndouser"@"localhost" IDENTIFIED BY "ndopassword"' at line 1

Je suis dans le meme cas et je ne trouve pas de solution

HELP HELP HELP

URGENT !!!

Salut a tous !

Pourriez vous m'aider a me donner les etapes que J'ai peux utiliser pour migrer ma confguration actuelle que J'ai dans Nagios dans Centreon???

J'arrive meme pas a voir le Local Host dans Centreon apres avoir l'installer !

J'ai suivis tout le procedure d'installation de Nagios et Centreon au sein de cette Forum mais J'arrive pas a faire marcher Centreon sous Nagios.

Veuillez bien m'aider s'il vous plait.

Nico Largo... Please wake up and help !!!!

Cheers.

Johnny

je viens de suivre ce tuto avec une debian 5.02, nagios 3.2 et centreon 2.1-RC8.
Sa passe (presque) tout seul, quelques erreurs à gauche à droite (notamment avec le sudoers non présent. Le reste des erreurs php.gd, copier/coller ndo2db et l'erreur SQL au dessus.)

Le reste c'est des options introduites par la nouvelle version de Centreon. (qui forcement ne sont pas traitées ici )

Donc un grand merci à toi Nico pour un tuto de plus super utile et bien foutu!

bonjour,
j'ai un petit souci. tout aller bien sur nagios et centreon, jai reconfigurer des templates (je ne croit pas avoir touché à autre chose) et maintenant lorsque je veut exporter les config de centreon vers nagios, j'ai ce message qui s'affiche:

Reading configuration data...

Error Invalid max_check_attempts value for host 'diw-appinteg'
Error Could not register host (config file '/usr/local/centreon/filesGeneration/nagiosCFG/1/hosts.cfg',­ starting on line 139)

***> The name of the main configuration file looks suspicious...

Make sure you are specifying the name of the MAIN configuration file on
the command line and not the name of another configuration file. The
main configuration file is typically '/usr/local/nagios/etc/nagios.cfg'

***> One or more problems was encountered while processing the config files...

Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.

Pouvez-vous me donner un coup de main, je ne sait plus trop où chercher.
MERCI D'AVANCE

Bonjour,

Merci pour ce travail, cela m'a bien aidé à déployer le couple Nagios/Centreon.

J'ai juste un petit souci, je n'arrive pas à accéder à l'interface web de centreon à partir d'une autre machine. Je peux me connecter uniquement sur la machine qui héberge centreon.
Question de droits ?
Je n'ai rien trouvé sur le forum ou ailleur.

Merci d'avance

I install nagios and also centreon successfully.
But the problem that i am experiencing now is that centreon can connet to the database.

What i notice is that the default user ndouser withh ndopassword cannot be support whan creating the database during the centreon install process.

What can it be due to ?

Dearly.

Merci au moins 10 milles fois pour ton tuto, ça aurait été impossible autrement

merci merci merci =)

problème lors de l'installation de nagios :"root@thibeau-desktop:/usr/src/nagios-3.2.0# ./configure --with-command-group=nagiosgrp
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
root@thibeau-desktop:/usr/src/nagios-3.2.0# ""

Bonjour,

J'ai fais l'installtion en suivant la procédure qui est très complète. Merci avant tout.

Les services dans centreon de la console etaient au vert. Tout nickel.

J'ai ajouté dans centréon des serveur avec des services. Et ensuite j'ai effectué l'export vers nagios et depuis tous les services sont passés au rouge.

Auriez vous une idée sur ce problème. Seul les hôtes sont au vert et les services sont tous en rouge dans nagios ainsi que dans centreon.

Status service = null

Merci d'avance

David

Bonjour à tous,

Merci pour ce tuto et ce site en général, on trouve des trésors.
L'installation s'est bien passée : nagios 3.20, plugins 1.4.14, ndoutils-1.4b9 et centreon 2.1.4.
En revanche j'ai un soucis lors de la création des hosts à partir de centreon. Pas de pb pour les créer. Je les exporte vers Nagios.
Au niveau de Monitoring/Event logs, ils apparaissent bien mais restent à INITIAL STATE. Ce qui fait qu'ils n'apparaissent pas dans Monotoring/Hosts : il n'y a que le localhost.
De plus, au niveau de Nagios (http://localhost/nagios) j'ai bien tous mes hosts mais tous les services sont en rouge (même le localhost qui est vert sur Centreon...)

J'ai vérifié et revérifié les droits de la base ndo et des dossiers, mais mystère...

Merci pour le coupe de main.

Christophe

Bonjour,

Moi j'ai un tout autre probléme.
Tous fonctionne mais quand j'exporte les fichier de cfg de centreon ils vont ce mettre dans le fichier de conf mais aprés la superviion s'arréte et ne marche plus :/
Quelqu'un peu m'aider ?

bonjour à tous,

j'ai installé Nagios 3.2.0 puis centreon 2.1.5,

j'ai terminé l'installation de centreon puis lors de l'étape :

"Pour cela, il faut aller dans le menu Configuration/Centreon, puis cliquer sur le lien ndo2db.cfg dans le menu de gauche et cliquer sur le lien Principal."

lorsque je clic sur le lien ndo2db.cfg, il ne se passe rien !

idem pour ndomod.cfg et Pollers.

quelqu'un à une idée ?

d'avance merci