epa
21st November 2008, 12:08
Bobjour à tous,
J'assemble et deploie des soekris sous OpenBsd et donc je les supervise avec nagios 3 er Centreon 1.426.
Tout fonctionnait bien lorsque qu'un matin je me suis trouvé à avoir tous les hosts DOWN alors que le ping répondait normalement.
J'ai relancer nagios pas de problème.
"---------------------------------------------------------"
Nagios 3.0.3
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 06-25-2008
License: GPL
Reading configuration data...
Warning: aggregate_status_updates directive ignored. All status file updates are now aggregated.
Warning: downtime_file variable ignored. Downtime entries are now stored in the status and retention files.
Warning: comment_file variable ignored. Comments are now stored in the status and retention files.
Running pre-flight check on configuration data...
Checking services...
Checked 14 services.
Checking hosts...
Checked 8 hosts.
Checking host groups...
Checked 2 host groups.
Checking service groups...
Checked 0 service groups.
Checking contacts...
Checked 2 contacts.
Checking contact groups...
Checked 1 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 47 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
Nagios 3.0.3
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 06-25-2008
License: GPL
Warning: aggregate_status_updates directive ignored. All status file updates are now aggregated.
Warning: downtime_file variable ignored. Downtime entries are now stored in the status and retention files.
Warning: comment_file variable ignored. Comments are now stored in the status and retention files.
Timing information on object configuration processing is listed
below. You can use this information to see if precaching your
object configuration would be useful.
Object Config Source: Config files (uncached)
OBJECT CONFIG PROCESSING TIMES (* = Potential for precache savings with -u option)
----------------------------------
Read: 0.004635 sec
Resolve: 0.000013 sec *
Recomb Contactgroups: 0.000027 sec *
Recomb Hostgroups: 0.000063 sec *
Dup Services: 0.000075 sec *
Recomb Servicegroups: 0.000002 sec *
Duplicate: 0.000043 sec *
Inherit: 0.000009 sec *
Recomb Contacts: 0.000001 sec *
Sort: 0.000002 sec *
Register: 0.000342 sec
Free: 0.000047 sec
============
TOTAL: 0.005278 sec * = 0.000254 sec (4.81%) estimated savings
Timing information on configuration verification is listed below.
CONFIG VERIFICATION TIMES (* = Potential for speedup with -x option)
----------------------------------
Object Relationships: 0.000143 sec
Circular Paths: 0.000004 sec *
Misc: 0.000468 sec
============
TOTAL: 0.000615 sec * = 0.000004 sec (0.7%) estimated savings
EVENT SCHEDULING TIMES
-------------------------------------
Get service info: 0.000240 sec
Get host info info: 0.000125 sec
Get service params: 0.000007 sec
Schedule service times: 0.000319 sec
Schedule service events: 0.000007 sec
Get host params: 0.000002 sec
Schedule host times: 0.000145 sec
Schedule host events: 0.000003 sec
============
TOTAL: 0.000848 sec
Projected scheduling information for host and service checks
is listed below. This information assumes that you are going
to start running Nagios with your current config files.
HOST SCHEDULING INFORMATION
---------------------------
Total hosts: 8
Total scheduled hosts: 7
Host inter-check delay method: SMART
Average host check interval: 642.86 sec
Host inter-check delay: 91.84 sec
Max host check spread: 30 min
First scheduled check: Fri Nov 21 10:50:22 2008
Last scheduled check: Fri Nov 21 10:59:33 2008
SERVICE SCHEDULING INFORMATION
-------------------------------
Total services: 14
Total scheduled services: 14
Service inter-check delay method: SMART
Average service check interval: 128.57 sec
Inter-check delay: 9.18 sec
Interleave factor method: SMART
Average services per host: 1.75
Service interleave factor: 2
Max service check spread: 30 min
First scheduled check: Fri Nov 21 10:51:26 2008
Last scheduled check: Fri Nov 21 10:53:25 2008
CHECK PROCESSING INFORMATION
----------------------------
Check result reaper interval: 10 sec
Max concurrent service checks: 20
PERFORMANCE SUGGESTIONS
-----------------------
I have no suggestions - things look okay.
cgi.cfg - déplacement OK
checkcommands.cfg - déplacement OK
contactgroups.cfg - déplacement OK
contacts.cfg - déplacement OK
dependencies.cfg - déplacement OK
escalations.cfg - déplacement OK
hostextinfo.cfg - déplacement OK
hostgroups.cfg - déplacement OK
hosts.cfg - déplacement OK
meta_commands.cfg - déplacement OK
meta_contact.cfg - déplacement OK
meta_contactgroup.cfg - déplacement OK
meta_dependencies.cfg - déplacement OK
meta_escalations.cfg - déplacement OK
meta_host.cfg - déplacement OK
meta_hostgroup.cfg - déplacement OK
meta_services.cfg - déplacement OK
meta_timeperiod.cfg - déplacement OK
misccommands.cfg - déplacement OK
nagios.cfg - déplacement OK
perfparse.cfg - déplacement OK
resource.cfg - déplacement OK
serviceextinfo.cfg - déplacement OK
servicegroups.cfg - déplacement OK
services.cfg - déplacement OK
timeperiods.cfg - déplacement OK
"----------------------------------------------------------"
Seule un nouveau host que j'ai ajouté fonctionne.
La seule différence est que dans la partie obtion j'ai pour les host faussement DOWN : Obsess Over Host = activé
Quelqu-un aurait une piste ??
Cordialement
J'assemble et deploie des soekris sous OpenBsd et donc je les supervise avec nagios 3 er Centreon 1.426.
Tout fonctionnait bien lorsque qu'un matin je me suis trouvé à avoir tous les hosts DOWN alors que le ping répondait normalement.
J'ai relancer nagios pas de problème.
"---------------------------------------------------------"
Nagios 3.0.3
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 06-25-2008
License: GPL
Reading configuration data...
Warning: aggregate_status_updates directive ignored. All status file updates are now aggregated.
Warning: downtime_file variable ignored. Downtime entries are now stored in the status and retention files.
Warning: comment_file variable ignored. Comments are now stored in the status and retention files.
Running pre-flight check on configuration data...
Checking services...
Checked 14 services.
Checking hosts...
Checked 8 hosts.
Checking host groups...
Checked 2 host groups.
Checking service groups...
Checked 0 service groups.
Checking contacts...
Checked 2 contacts.
Checking contact groups...
Checked 1 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 47 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
Nagios 3.0.3
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 06-25-2008
License: GPL
Warning: aggregate_status_updates directive ignored. All status file updates are now aggregated.
Warning: downtime_file variable ignored. Downtime entries are now stored in the status and retention files.
Warning: comment_file variable ignored. Comments are now stored in the status and retention files.
Timing information on object configuration processing is listed
below. You can use this information to see if precaching your
object configuration would be useful.
Object Config Source: Config files (uncached)
OBJECT CONFIG PROCESSING TIMES (* = Potential for precache savings with -u option)
----------------------------------
Read: 0.004635 sec
Resolve: 0.000013 sec *
Recomb Contactgroups: 0.000027 sec *
Recomb Hostgroups: 0.000063 sec *
Dup Services: 0.000075 sec *
Recomb Servicegroups: 0.000002 sec *
Duplicate: 0.000043 sec *
Inherit: 0.000009 sec *
Recomb Contacts: 0.000001 sec *
Sort: 0.000002 sec *
Register: 0.000342 sec
Free: 0.000047 sec
============
TOTAL: 0.005278 sec * = 0.000254 sec (4.81%) estimated savings
Timing information on configuration verification is listed below.
CONFIG VERIFICATION TIMES (* = Potential for speedup with -x option)
----------------------------------
Object Relationships: 0.000143 sec
Circular Paths: 0.000004 sec *
Misc: 0.000468 sec
============
TOTAL: 0.000615 sec * = 0.000004 sec (0.7%) estimated savings
EVENT SCHEDULING TIMES
-------------------------------------
Get service info: 0.000240 sec
Get host info info: 0.000125 sec
Get service params: 0.000007 sec
Schedule service times: 0.000319 sec
Schedule service events: 0.000007 sec
Get host params: 0.000002 sec
Schedule host times: 0.000145 sec
Schedule host events: 0.000003 sec
============
TOTAL: 0.000848 sec
Projected scheduling information for host and service checks
is listed below. This information assumes that you are going
to start running Nagios with your current config files.
HOST SCHEDULING INFORMATION
---------------------------
Total hosts: 8
Total scheduled hosts: 7
Host inter-check delay method: SMART
Average host check interval: 642.86 sec
Host inter-check delay: 91.84 sec
Max host check spread: 30 min
First scheduled check: Fri Nov 21 10:50:22 2008
Last scheduled check: Fri Nov 21 10:59:33 2008
SERVICE SCHEDULING INFORMATION
-------------------------------
Total services: 14
Total scheduled services: 14
Service inter-check delay method: SMART
Average service check interval: 128.57 sec
Inter-check delay: 9.18 sec
Interleave factor method: SMART
Average services per host: 1.75
Service interleave factor: 2
Max service check spread: 30 min
First scheduled check: Fri Nov 21 10:51:26 2008
Last scheduled check: Fri Nov 21 10:53:25 2008
CHECK PROCESSING INFORMATION
----------------------------
Check result reaper interval: 10 sec
Max concurrent service checks: 20
PERFORMANCE SUGGESTIONS
-----------------------
I have no suggestions - things look okay.
cgi.cfg - déplacement OK
checkcommands.cfg - déplacement OK
contactgroups.cfg - déplacement OK
contacts.cfg - déplacement OK
dependencies.cfg - déplacement OK
escalations.cfg - déplacement OK
hostextinfo.cfg - déplacement OK
hostgroups.cfg - déplacement OK
hosts.cfg - déplacement OK
meta_commands.cfg - déplacement OK
meta_contact.cfg - déplacement OK
meta_contactgroup.cfg - déplacement OK
meta_dependencies.cfg - déplacement OK
meta_escalations.cfg - déplacement OK
meta_host.cfg - déplacement OK
meta_hostgroup.cfg - déplacement OK
meta_services.cfg - déplacement OK
meta_timeperiod.cfg - déplacement OK
misccommands.cfg - déplacement OK
nagios.cfg - déplacement OK
perfparse.cfg - déplacement OK
resource.cfg - déplacement OK
serviceextinfo.cfg - déplacement OK
servicegroups.cfg - déplacement OK
services.cfg - déplacement OK
timeperiods.cfg - déplacement OK
"----------------------------------------------------------"
Seule un nouveau host que j'ai ajouté fonctionne.
La seule différence est que dans la partie obtion j'ai pour les host faussement DOWN : Obsess Over Host = activé
Quelqu-un aurait une piste ??
Cordialement