So far I'm not able to reproduce your problem. All seems to be just as
described in the documentation.
Please give some details about your environment.
Which Icinga version do you use? Which os?
Am 12.02.2012 17:20, schrieb daniel.duf...@ec.europa.eu:
Hello Everybody,
I'm currently making some tests with External command
SCHEDULE_HOST_SVC_DOWNTIME
/usr/bin/printf "[%lu]
SCHEDULE_HOST_SVC_DOWNTIME;cris_oracle_dev3;1329019200;1329087600;0;0;60;dufouda;Automatic
WE Database Refresh\n" `date +%s` > /usr/local/icinga/var/rw/icinga.cmd
The result in log file is
[1329060680] EXTERNAL COMMAND:
SCHEDULE_HOST_SVC_DOWNTIME;cris_oracle_dev3;1329019200;1329087600;0;0;60;dufouda;Automatic
Database WE Refresh
[1329060680] Error: Could not find host '1329019200' provided in
external command!
If I add 1 parameter between SCHEDULE_HOST_SVC_DOWNTIME and HOSTNAME
(For example I add ";x;"in second position) Everything is working fine.
/usr/bin/printf "[%lu]
SCHEDULE_HOST_SVC_DOWNTIME*;x;*cris_oracle_dev3;1329019200;1329087600;0;0;60;dufouda;Automatic
WE Database Refresh\n" `date +%s`> /usr/local/icinga/var/rw/icinga.cmd
The result in log file is
[1329061131] EXTERNAL COMMAND:
SCHEDULE_HOST_SVC_DOWNTIME*;x;*cris_oracle_dev3;1329019200;1329087600;0;0;60;dufouda;Automatic
Database WE Refresh
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;oracle_sessions;STARTED; Service has entered a period
of scheduled downtime
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;oracle_connect;STARTED; Service has entered a period
of scheduled downtime
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;oracle_backup;STARTED; Service has entered a period
of scheduled downtime
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;invalid_objects;STARTED; Service has entered a period
of scheduled downtime
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;dbms_scheduler;STARTED; Service has entered a period
of scheduled downtime
[1329061131] SERVICE DOWNTIME ALERT:
cris_oracle_dev3;cris_r6_permissions;STARTED; Service has entered a
period of scheduled downtime
According to Icinga 1.6 Documentation, this second parameter should be
hostname:
**SCHEDULE_HOST_SVC_DOWNTIME**
|SCHEDULE_HOST_SVC_DOWNTIME;|<host_name>;<start_time>;<end_time>;<fixed>;<trigger_id>;<duration>;<author>;<comment>
Schedules downtime for all services associated with a particular host.
If the "fixed" argument is set to one (1), downtime will start and end
at the times specified by the "start" and "end" arguments. Otherwise,
downtime will begin between the "start" and "end" times and last for
"duration" seconds. The "start" and "end" arguments are specified in
time_t format (seconds since the UNIX epoch). The service downtime
entries can be triggered by another downtime entry if the "trigger_id"
is set to the ID of another scheduled downtime entry. Set the
"trigger_id" argument to zero (0) if the downtime for the services
should not be triggered by another downtime entry.
Could you help me? Is it a bug? Is it an undocumented parameter?
Thanks in advance,
Regards,
*Daniel Dufour*//
European Commission, DEVCO
Information Technology and Infrastructure (Unit R6)
PRODUCTION Team - Head of Section
Building L41 8/33 - 1049 Brussels, Belgium
Phone: +32 2 29 55730, Email:daniel.duf...@ec.europa.eu//
//
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
