Assuming you’re referring to command_endpoint: Both the master as well as the satellite instance need to have the same command definition. This because rather than just sending the command line to the satellite the master sends the following information:
A) the command name B) whatever macros the satellite needs to execute the command The rationale for this is that constants might have different values on the master and the satellite (e.g. PluginDir) which is why we can’t just send the command line as a string. The added bonus is that the master can’t just execute arbitrary commands on the satellite (like NRPE with „don’t blame NRPE“ enabled). The satellite also needs the command definition because it really just fills in the macros it got from the master and executes that command. On 03/02/15 13:47, "Marcio Moreira" <[email protected]> wrote: >Hi, > >Is it mandatory to have the same commands defined in file commands.conf >on bofh >both the client and the master server to check the remote client ? > >It's not possible just define the commands in master side ? > > > >Best Regards >-- >Márcio Filipe Mendes Moreira <[email protected]> >Administrador de Sistemas >Eurotux Informatica, SA | www.eurotux.com >Tel: (+351) 253680300 - Suporte: (+351) 253680301 >Fax: (+351) 253680319 -- Gunnar Beutner Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | [email protected] ** CeBIT 2015 - 16.-20. März 2015 - http://www.netways.de/cebit ** ** OSDC 2015 - April - osdc.de ** ** Puppet Camp Berlin 2015 - April - netways.de/puppetcamp ** ** OSBConf 2015 - September - osbconf.org ** _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
