entsprechende (beispiel)configs und logs zur naeheren erlaeuterung des problems waeren hilfreich.
Einer der betroffenen Services:
define service {
#NAGIOSQL_CONFIG_NAME chk_esxi
hostgroup_name cat_srv_esx,cat_srv_esxi
service_description chk_esxi_cpuusage
display_name chk_esxi_cpuusage
use sh_standard_service,srv-pnp
check_command check_esxi!-l cpu -s usagemhz
register 1
}
Und die benutzten Templates:
define service {
name sh_standard_service
max_check_attempts 3
check_interval 5
retry_interval 5
check_period 24x7
notification_interval 30
notification_period 24x7
contact_groups admins
register 0
}
define service {
name srv-pnp
action_url /pnp4nagios/index.php/graph?host=$HOSTNAME$&srv=$SERVICEDESC$' class='tips' rel='/pnp4nagios/index.php/popup?host=$HOSTNAME$&srv=$SERVICEDESC$
register 0
}
Wobei die Checks ja genau das getan haben wie sie sollten, nur das Acknowledgen und Schduled Downtimes nicht funktioniert haben.
Im (bereinigten, ich habe Meldungen, die für andere Hosts/Services kamen rausgefiltert, sowie Notifikationen, die nicht an mich bzw. Icingaadmin gingen) Event Log stellt sich das so dar:
Service Notification[08-03-2012 01:49:37] SERVICE NOTIFICATION: icingaadmin;srv_vms5_ka;chk_esxi_cpuusage;UNKNOWN;notify-service-by-email

Service Check Timed Out)Service Notification[08-03-2012 01:49:37] SERVICE NOTIFICATION: sh_benzj;srv_vms5_ka;chk_esxi_cpuusage;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:49:37] SERVICE NOTIFICATION: sh_speckt;srv_vms5_ka;chk_esxi_cpuusage;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:49:36] SERVICE NOTIFICATION: sms_speckt;srv_vms5_ka;chk_esxi_cpuusage;UNKNOWN;notify-service-by-email

Service Check Timed Out)External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_vmfs;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_status;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_mem;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_io;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_cpuusage;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:28:02] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_cpu;1343950069;1343975269;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_vmfs;2;1;0;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_status;2;1;0;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_mem;2;1;0;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_io;2;1;0;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_cpuusage;2;1;0;Icinga Admin;
External Command[08-03-2012 01:27:34] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_cpu;2;1;0;Icinga Admin;
Service Notification[08-03-2012 01:25:27] SERVICE NOTIFICATION: icingaadmin;srv_vms5_ka;chk_esxi_mem;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:25:27] SERVICE NOTIFICATION: sh_speckt;srv_vms5_ka;chk_esxi_mem;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:25:26] SERVICE NOTIFICATION: sms_speckt;srv_vms5_ka;chk_esxi_mem;UNKNOWN;notify-service-by-email

Service Check Timed Out)
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_vmfs;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_status;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_mem;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_io;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_cpuusage;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:25:14] EXTERNAL COMMAND: SCHEDULE_SVC_DOWNTIME;srv_vms5_ka;chk_esxi_cpu;1343949901;1343975101;1;0;7200;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_vmfs;2;1;0;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_status;2;1;0;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_mem;2;1;0;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_io;2;1;0;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_cpuusage;2;1;0;Icinga Admin;
External Command[08-03-2012 01:24:43] EXTERNAL COMMAND: ACKNOWLEDGE_SVC_PROBLEM;srv_vms5_ka;chk_esxi_cpu;2;1;0;Icinga Admin;
Service Notification[08-03-2012 01:21:57] SERVICE NOTIFICATION: icingaadmin;srv_vms5_ka;chk_esxi_status;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:21:56] SERVICE NOTIFICATION: sh_speckt;srv_vms5_ka;chk_esxi_status;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Service Notification[08-03-2012 01:21:56] SERVICE NOTIFICATION: sms_speckt;srv_vms5_ka;chk_esxi_status;UNKNOWN;notify-service-by-email

Service Check Timed Out)
Bis dato habe ich bei Icinga eigentlich an jeden Ausfall ein ACK bzw. eine scheduled Downtime setzen können, sowas wie heute nacht ist uns noch nie passiert.
Ich habe dann heute im Laufe des Tages auch nochmal versucht, mit dem User des Kollegen, der heute nacht Bereitschaft hatte ACk zu setzen und auch das hat wieder einwandfrei funktioniert.
Edit: kann man die Umwandlung von ";"+"(" in das

Smiley eigentlich verhindern?