Posts by bodsch

    Moin Moin!


    I have an strange problem with the creating of (satellite) certificates at the CLI.


    i wrote a small script to create these certificates:


    this script runs perfectly with all icinga2 versions < 2.8


    since yesterday, is icinga 2.8 for Alpine available.


    now i get this result:


    when i look into the Icinga Sourcecode, i found this position:

    https://github.com/Icinga/icin…rpcconnection-pki.cpp#L84


    i my current fall, all certificates are fresh, the CA is created with 2.8 few minutes ago.


    It is possible, that my old way is now unsupported?

    test your database connection via command-line.


    mysql -uroot -p -h localhost ...

    mysql -uicinga2 -p -h localhost ...


    please use the correct passwords!


    if this fails, configure the database properly


    but ... you should learn the basics before doing anything more complex!

    ohh ... hirn
    please ... use your brain and not copy-paste! :)

    add a slash in front of usr: /usr/sbin/apache2 -V | grep MPM

    thats look like an apache missconfiguration


    please try first this

    Code
    1. apache2ctl configtest

    then, look, which apache mpm are installed:

    Code
    1. /usr/sbin/apache2 -V | grep MPM


    (sorry, i use primary nginx, thats was (and is) easesier for me ;) )

    good morning guys!


    i will try to exchange my full static configuration with an dynamic part.

    thats include some servicegroups like this:

    Code
    1. object ServiceGroup "heap-memory" {
    2. display_name = "Heap Memory"
    3. assign where match("HeapMemory*", service.name)
    4. }


    i try it with this curl styled and hot-needled code:

    Code
    1. curl \
    2. -v \
    3. -u $ICINGA2_API_USER:$ICINGA2_API_PASSWORD \
    4. -H 'Accept: application/json' \
    5. -X PUT \
    6. -k "https://$ICINGA2_HOST:$ICINGA2_API_PORT/v1/objects/servicegroups/group_dummy_1" \
    7. -d '{ "attrs": { "display_name": "group_dummy_1", "assign": "match(\"HeapMemory*\", service.name)" } }' | python -m json.tool

    but i becomes this error back:


    after a googleling and inspect some icinga lines of code i found nothing to do this. :(


    without the assign part, the curl command works.


    please, can you help me!?

    Moin!


    I will modify an simple service check over the API:

    Code
    1. curl -k -uroot:icinga -H 'Accept: application/json' -H 'Content-Type: application/json' -H 'X-HTTP-Method-Override: POST' https://172.17.0.2:5665/v1/objects/services --data '{"templates":["generic-service"], "attrs": { "check_interval": 60, "vars": { "http_url":"/acces
    2. s/login", "http_address":"10.41.80.63"}}, "filter":"service.name==\"new_http\""}'

    But my result are empty:

    Code
    1. {"results":[]}

    when i turned on the Debug Log, i see the connection and nothing else:


    I have this never seen before and i'm confused.


    Is my curl call wrong?

    Das kommt mir seltsam vor:


    Code
    1. <Timeout exceeded.><Terminated by signal 9 (Killed).>

    oder das

    Code
    1. Notification command for object 'Rzjmon01!load' (PID: 15352, arguments: '/etc/icinga2/scripts/mail-service-notification.sh') terminated with exit code 127, output: /etc/icinga2/scripts/mail-service-notification.sh: 20: /etc/icinga2/scripts/mail-service-notification.sh: mail: not found
    2. /usr/bin/printf: Schreibfehler: Datenübergabe unterbrochen (broken pipe)

    Ansonsten sehe ich gerade keine Probleme.


    Ich gehe davon aus, dass die mit 'Backend läuft nicht' die Ausgabe im IcingaWeb2 meinst?

    Wie verbindest du dich denn mit dem Backend? Also, wie ist es konfiguriert.

    Es gibt m.W.n. die Möglichkeit, das Webinterface mittels API-User zu verbinden.


    System -> Modules -> monitoring -> Backend -> (Monitoring Backends|Command Transports)


    Kontrolliere mal bitte deren Einstellungen!

    Über 'show resource configuration' kannst du auch ein 'Validate' anwerfen.

    Auch mal testen.