I tried that too. Works quite well. The downtime gets scheduled. but it's not visible on the master, just on the slaves?
Anybody knows how to make it visible on the master? Maybe by seding it to the masters nagios.cmd file? -- kind regards, Henry On Mi, 2011-02-23 at 12:00 +0100, Simone Felici wrote: > Yes I'm sending only SCHEDULE_HOST_DOWNTIME and SCHEDULE_SVC_DOWNTIME. > Meanwhile I've tested it and > it works perfectly. BTW thank you for your answer. this give me additional > trust I'm not making > problems on my system :-) > > Have a nice day! > > Simon > > Il 23/02/2011 10:09, Ton Voon ha scritto: > > Simon, > > > > What's the Nagios command you are creating for downtimes? > > > > We only propagate certain commands down to the slave. This is done via our > > broker module called > > altinity_distributed_commands.o. This intercepts commands sent to Nagios > > and writes to the > > slave_commands.cache file for delivery by opsviewd. > > > > However, some commands are "not distributable" because they may reference > > an internal id that is not > > necessarily consistent between master and slaves (eg, downtime ids). Hence > > asking what command you > > are using. > > > > FYI, the downtime commands used through the UI, SCHEDULE_HOST_SVC_DOWNTiME, > > etc, are distributed. > > The full list is here (near the bottom): > > https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-base/patches/altinity_distributed_commands.c > > > > Ton > > > > > > On 21 Feb 2011, at 11:53, Simone Felici wrote: > > > >> > >> Okay, auto-solved. > >> > >> For who is interested in, the commands are written into this file in > >> nagios external command syntax: > >> > >> /usr/local/nagios/var/slave_commands.cache > >> > >> The file is created by nagios user, then opsviewd parse this file every 15 > >> seconds (more or less) > >> and deleted after. Internal routines send the commands to all slaves. > >> > >> It's a personal interpretation, also use it at your own risk :) > >> Maybe some opsview-guru could confirm or correct what above. > >> > >> Bye, Simon > >> > >> > >> Il 21/02/2011 10:24, Simone Felici ha scritto: > >>> > >>> Hello! > >>> > >>> I'm trying to set-up a scheduled downtime at specific dates. > >>> If I put in downtime a host/service from OPSView GUI I can see the > >>> downtime is propagated from > >>> master to slaves too. But what if I would insert a scheduled downtime via > >>> cron? > >>> The script is not an issue, I've made some tests and it works. The > >>> problem is, the scheduled > >>> downtime triggered via cron from the master is *not* propagated to slaves > >>> and having the > >>> notifications sent from slaves for this host (it's monitored there), the > >>> notifications are sent and > >>> the downtime not considered. > >>> How does OPSView the sync of these informations? How could I propagated a > >>> downtime started via CRON > >>> to slaves? > >>> > >>> Thank's for the hints! > >>> > >>> Simon > >>> _______________________________________________ > >>> Opsview-users mailing list > >>> [email protected] <mailto:[email protected]> > >>> http://lists.opsview.org/lists/listinfo/opsview-users > >> _______________________________________________ > >> Opsview-users mailing list > >> [email protected] <mailto:[email protected]> > >> http://lists.opsview.org/lists/listinfo/opsview-users > > > > > > Ton Voon > > Product Architect > > > > > > > > > > Global Headquarters: Unit 69 Suttons Business Park | Reading | Berkshire | > > RG6 1AZ | UK > > > > UK:+44 (0) 845 057 7887 > > USA: +1 866 879 9184 > > Email: [email protected] <mailto:[email protected]> > > Skype: tonvoon > > Web: www.opsview.com <http://www.opsview.com/> > > > > This e-mail is confidential, intended only for the named recipient(s) above > > and may contain > > information that is privileged and confidential. If you receive this > > message in error, or are not > > the named recipient(s), please notify the sender at the phone number above, > > do not copy this > > message, do not disclose its contents to anyone, and delete this e-mail > > message from your computer. > > Although we routinely screens for viruses, addressees should scan this > > e-mail and any attachments > > for viruses. Opsera makes no representation or warranty as to the absence > > of viruses in this e-mail > > or any attachments. > > > > > > > > _______________________________________________ > > Opsview-users mailing list > > [email protected] > > http://lists.opsview.org/lists/listinfo/opsview-users > > > -- > Simone Felici > Divisione Tecnica: Progettazione e Sviluppo > > tel. +39 0461.030.111 > fax. +39 0461 030.112 > Via Fersina, 23 - 38123 Trento > > ------------- > MC-link S.p.A. > Sede Direzionale e Amministrativa > Via Carlo Perrier, 9/a - 00157 Roma > Sede Legale > Via Fersina, 23 - 38123 Trento > > http://www.mclink.it > > Save a tree. Don't print this e-mail unless it's really necessary > > Informativa ai sensi del Codice della proprietà industriale e del Codice dei > dati personali. > Le informazioni contenute in questa e-mail e negli eventuali allegati, > possono contenere > informazioni confidenziali e coperte da segreto commerciale/industriale. Esse > vengono comunicate nei > limiti giuridici dei rapporti in essere fra le parti e pertanto nessun > ulteriore diritto di > proprietà intellettuale o industriale può essere rivendicato dal ricevente. > Le informazioni contenute in questa e-mail e negli eventuali allegati sono > indirizzate > esclusivamente a coloro che figurano come destinatari. > Se avete ricevuto per errore questa e-mail siete pregati di informarci > (rispedendola al mittente) e > di provvedere alla sua rimozione, a non farne utilizzo e a non conservarne > alcuna copia. > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/lists/listinfo/opsview-users _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
