Endpoint "XXX" does not accept commands

This forum was archived to /woltlab and is now in read-only mode.
  • Hello everyone,



    I have a little question that I couldn't find a solution for when I googled.


    I am recently trying to automate the configuration of an icinga2-client.


    Everything seems to work fine, but I have a problem that stops me from finishing this thing.


    When I run my config scripts all the conf-Files in Icinga2 seem just fine, but in Icingaweb2 I can still only see:


    Quote

    Endpoint ''myserver.domain.de" does not accept commands.


    When I run the node wizard manually it works like a charm.


    So hers is the point, the node wizard asks me to:


    - Accept config from master? [y/N]:


    - Accept commands from master? [y/N]:


    Both times "no" is the default, but I actually want it to do so.


    So the question is: Where do I set this if I don't/can't do it in the node wizard?



    Tl;dr: Where can I configure my Client to accept conf and commands from master? (Not using the node wizard?)



    thanks in advance,


    kind regards


  • try looking here:

     /etc/icinga2/features-enabled/api.conf 


    mine looks like this:

    Code
    1. /** Icinga 2 Config - proposed by Icinga Director */
    2. object ApiListener "api" {
    3. cert_path = SysconfDir + "/icinga2/pki/<hostname>.crt"
    4. key_path = SysconfDir + "/icinga2/pki/<hostname>.key"
    5. ca_path = SysconfDir + "/icinga2/pki/ca.crt"
    6. accept_commands = true
    7. accept_config = true
    8. }

    Linux is dead, long live Linux


    Remember to NEVER EVER use git repositories in a productive environment if you CAN NOT control them