Posts by ts2010

    Yes, I understand your point but in my case AWS create and delete hosts in a given name range dependent on the load / traffic and we don't know when. Therefore for me auto-deployment is necessary and it seems that I've misunderstood the parameter 'purge'.


    I think the cron job with the above mentioned CLI will not frequently restart the tcp sessions cause a positive sync happens in my case only one or two times per day. Even though I run the cron job every 5 minutes from my point of view the CLI first checking changes against the database and respond with 'Config matches active stage, nothing to do' without do anything. The disadvantage is, that you have take care each time you develop new structures in Icinga.

    Maybe I did not express myself correctly. I created a sync rule with 'replace' and 'purge=yes' and I thought that each time the sync rule trigger to import new or deleted hosts to my template the changes will automatically deployed by Director (purge=yes). In my case Director shows me only that the config was changed but does not deploy the changes directly. I have to manually trigger the changes and I think this is not the point of the function. My second comment was only a workaround for me if there is a bug or a misunderstanding.

    I dig deeper into the Director specification and the only way to solve this issue could be to initialize a cron job for each minute that start the following command on the Icinga2 host:


    Code
    1. icingacli director config deploy


    Would this be really the only solution or is it rather a bug in the sync functionality?

    Dear Icinga-community,

    --

    I use:

    Icinga2: 2.7.0-1

    Director: 1.3.2

    aws-module for Director: 0.0.1

    --


    I created an import and sync rule to identify new hosts in my AWS account. The sync rule has the policy "replace". The job has the policy to process any changes directly. In the background the icinga job 'icingacli director jobs run --forever' is running.


    Each time the sync rule recognized any changes to replace my configuration the changes are not automatically deployed by Icinga Director. Why Icinga Director is not automatically deployed the new imported changes?




    Thanks in advance for any help.


    Best, Ray

    Can anybody support me in this issue? First I created a dedicated template for the AWS autoscaling group. Then I created an import source (1) followed by a sync rule (2). After sync run the scaling group was imported (3) but if I look at the hosts only the scaling group is listed like a host (4).


    As far as I understand this module the hosts should be dynamically requested from the scaling groups but this seems not to be the case.

    Dear Icinga-community,


    I use:

    Icinga2: 2.7.0-1

    Director: 1.3.2

    aws-module for Director: 0.0.1


    My goal is to monitor a dynamic amount of AWS hosts based on an AWS Autoscaling Group. Each time a new host is automatically created by the AWS autoscaling parameters the host should be activated automatically for monitoring with all necessary services in Icinga2. If the host is shut down by the process the host should automatically deactivated in Icinga2 too.


    I installed the latest aws module for Director from GitHub and followed the tutorial of Thomas Gelf on https://github.com/Icinga/icin…ob/master/doc/02-Usage.md. All works fine and the sync was also successful. But the last step of the tutorial I stuck and the sync only creates one host with the name of the autoscaling group. I expect that all hosts are automatically appear. What are I'm doing wrong?


    Has anybody successful running this module in Director and can provide me with a hint or an external source where I get more help?


    Thanks in advance and best regard,

    Ray

    Dear Renzzoo,


    in my case I installed Icinga2 version 2.7 new from scratch. Afterwards I installed the latest Director plugin (version 1.3.2) from tarball and it works. The only trouble I had was the problem with the notification due to I followed the latest video tutorial to get the Director running. I solved it (see: A simple created check in Director lead to the validation error "Object 'mail-host-notification' of type 'NotificationCommand' does not exist").


    Best, Ray

    Dear Wolfgang, dear Kevin,


    first of all thank you both to lead me on the right path. I've solved the problem!


    The reason for this problem was, that Christian Stein recommended in his latest video tutorial 'Icinga Director: Installation und Einrichtung' after installation of the director module to delete all conf-files under '/etc/icinga2/conf.d/' expect of 'api-users.conf'. I followed this guide and of course I deleted also the file 'command.conf'. After restore this file and start the kickstarter now it works.


    Thanks for your support, Ray

    Dear Kevin,


    thanks for your reply. I still know that Icinga have trouble with the command but what is the reason for?


    I'm still working since several weeks (not the whole time ;)) on Icinga and try to get it running. The concept of the product, the ui and all its modules is great and I love it but for me it's not possible to get it final running with notifications (BTW I followed also your tutorial without success). Now I installed a clean and, from my point of view, non-spectacular installation and I stuck once again. In addition the latest Director video tutorial ends in front of the topic 'notifications'. Bad!


    Can anybody tell me why the command is not known for Director? Has anybody got notifications working without move Director inside out? Could it be really a problem of the pre-release of Director?


    If the community needs more information I will provide.


    Thx, Ray

    Dear Icinga-Community,


    due to a lot of problems in the past with notifications I dropped my current Icinga2+Director environment and set it up once again with Icinga2 (v 2.7.0-1) and Director (1.3.2 from tarball). To get a proper and stable system I followed the latest video tutorial for Director ( Icinga Director: Installation und Einrichtung (Teil 1) (Webinar vom 28. Juni 2017) ). All looks fine until I created the first notification check to receive an email if the host goes down or up. The validator failed with:



    Currently I've only one simple host. To identify the identification type I added a data list.

    Code
    1. object Host "xxxx.xxxxxxx.com" {
    2. import "generic-hosts"
    3. display_name = "TS Icinga Monitoring Host"
    4. address = "127.0.0.1"
    5. groups = [ "tsu" ]
    6. vars.notification = "email"
    7. }

    For notifications I created following objects in Director:

    • a time range template
    • a time range object with all the time ranges
    • a user template
    • a group and user object
    • a notification template for host notification
    • and the following notification object
    Code
    1. apply Notification "check-hosts" to Host {
    2. import "first-level-host-tmpl"
    3. assign where host.vars.notification == "email"
    4. states = [ Down, Up ]
    5. types = [ Problem, Recovery ]
    6. user_groups = [ "first-level-grp" ]
    7. }


    Can anybody give me a hint how to solve the problem?


    Thanks in advance and best regards,

    Ray

    Dear Icinga-community,


    I use:

    Icinga2: 2.6.3

    Director: 1.3.2


    Due to many trouble with notifications under Icinga Director 1.3.1 I upgraded to the pre release version 1.3.2. Unfortunately now my host and service definitions are no longer accessible. If I want to access the following message appear:


    Trying to set invalid icinga_service key "check_timeout". DB schema change?


    I ran 'icingacli director migration run --verbose' without success. Is there any migration script for the database available?


    BTW: I've seen Icinga 2.7 was rolled out. Is there something special to take care or can I proceed the existing documentation under 'https://www.icinga.com/docs/icinga2/latest/doc/16-upgrading-icinga-2/' ?


    Thanks in advance and best regards,

    Ray

    OK, now it works.


    There were three mandatory steps for me to get it compiled on Amazon Linux AMI 2017.03:

    • You must be 'root'. Otherwise the compile process ends with '/usr/bin/ld: cannot find -lexecinfo'
    • Don't make any changes on CMAKE_OPTS parameters. Leave it as it is.
    • In my case 'yum install postgresql-devel' installed version 9.2 instead of the latest 9.5. Therefore better install 'yum install postgresql95-devel'.

    Finally here are my steps to complete:


    dnsmichi, thank you for your awesome help. If it would be helpful for you, I can support you with the created Amazon Linux AMI 2017.03 rpm's to promote these on the Icinga website. Please let me know.


    Best, Ray

    OK, I'll follow strict your guide soon. Here my versions of c++ and cmake:

    Dear dnsmichi,


    first of all I will thank you for the lot of changes you've prepared regarding this issue.


    I followed up your suggestions but I'll get still the same error on the AMI 2017.03 and the rpm's are not created (see details in the attached logfile).

    Code
    1. /usr/bin/ld: cannot find -lexecinfo

    To understand what I've done on my machine here my steps:


    1. Preparation of my build environment (I build the rpm with the Amazon Linux default user 'ec2-user' due to the recommendation to build not with 'root')

    Code
    1. sudo yum install rpmdevtools boost-devel flex cmake bison gcc-c++ nagios-plugins-all openssl-devel \
    2. perl-Nagios-Plugin libedit-devel ncurses-devel postgresql-devel mysql-devel \
    3. libstdc++-devel selinux-policy-devel checkpolicy selinux-policy selinux-policy-do
    4. sudo yum groupinstall Development
    5. mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
    6. echo '%_topdir %(echo $HOME)/rpmbuild' > ~/.rpmmacros

    2. I copied the latest spec file from the repo and grab the source.

    Code
    1. curl https://raw.githubusercontent.com/Icinga/icinga2/master/icinga2.spec -o $HOME/rpmbuild/SPECS/icinga2.spec
    2. cd $HOME/rpmbuild/SOURCES
    3. spectool -g ../SPECS/icinga2.spec

    3. I modified the spec-file as mentioned by you. In addition I wraped all the conditions for the depricated gui you recommended here https://github.com/Icinga/icinga2/pull/5303. In addition I added the following cmake parameter to the spec-file:

    Code
    1. ..
    2. -DICINGA2_WITH_MYSQL=OFF \
    3. -DICINGA2_WITH_PGSQL=OFF \
    4. -DINSTALL_SYSTEMD_SERVICE_AND_INITSCRIPT=ON \
    5. ..

    Btw: I found a typo here https://github.com/Icinga/icinga2/pull/5304/files in line 184.

    4. Then I start the build process.

    Code
    1. cd $HOME/rpmbuild/
    2. rpmbuild -ba SPECS/icinga2.spec


    It seems that we're a glimpse away from the rpm's but what the h**l is execinfo. If I search the ldconfig library the .so is not installed. It seems that Amazon Linux or EPEL doesn't supply this lib.

    Code
    1. ldconfig --print-cache | grep execinfo

    Any further ideas?


    Best , Ray

    Files