Hi Michael,

Thank you for your answers. 

Just one more thing, I define the same checkcommands in both sides, but as a 
test I 
remove one of checkcommands in the client, and the check associated is still OK 
in 
master web interface. Why does this happen ? The state should not change to 
UNKNOWN for example ?

The only difference I saw was the "Last Check Time" for the service in web 
interface 
stayed the same, not change.


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
On Tuesday 03 February 2015 17:59:28 Michael Friedrich wrote:


No, both ends require the same checkcommand. That way you can restrict certain 
arguments on the remote client - a bit tad more secure than nrpe command args.


Michael

Am Dienstag, 3. Februar 2015 schrieb Marcio Moreira :


Hi,

But it's possible with icinga2 remote client, just define the commands inmaster 
with 
plugins in client side ?

The master send the command to execute to the client and the client executethat 
command, sending the result back to the master.



Best Regards--Márcio Filipe Mendes Moreira <[email protected][1]>Administrador 
de SistemasEurotux Informatica, SA | www.eurotux.com[2]
[email protected][1]> 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[2]
http://www.netways.de[3] | [email protected][1]
http://www.netways.de/cebit[4] **> ** OSDC 2015 - April - osdc.de[5] **> ** 
Puppet 
Camp Berlin 2015 - April - netways.de/puppetcamp[6] **> ** OSBConf 2015 - 
September - osbconf.org[7] **> _______________________________________________> 
icinga-users mailing list> [email protected][1]
https://lists.icinga.org/mailman/listinfo/icinga-users[8]



--------
[1] javascript:;
[2] http://www.eurotux.com
[3] http://www.netways.de
[4] http://www.netways.de/cebit
[5] http://osdc.de
[6] http://netways.de/puppetcamp
[7] http://osbconf.org
[8] https://lists.icinga.org/mailman/listinfo/icinga-users

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to