Posts by passpes

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

    Hi folks,


    I have 3 nodes running (icinga-master, icinga agent, icingaweb2) and the implemetation of these icinga2 nodes is done by puppet using the module puppet-icinga2 for puppet CA purpose,


    Now that everything is working okay, I added the module director to icingaweb2 with director DB resource which is perfectly connected to the module.


    The problem "Unable to authenticate, please check your API credentials" appears when I try to run the import.


    From my perspectives puppet-icinga2 doesn't have the conf.d/api-users.conf file, so I added it simply to let the director connect to icinga2 using API and the credentials in the file api-users.conf but the problem still there.

    Hey folks,


    I have an icinga2 solution for distributed top-bottom setup, I wanted to automate the monitoring of new hosts using puppet but all I found is just exported resources using PuppetDB to send them to the master, this configuration is a bit tricky cause we have to export also the autosigning certificate, hostname and ip address and put them in the right way in zones.conf..
    Is there any concrete solution or starting point so that we can develop this module to Icinga community?

    I have an error sendinf a check from icingaweb2 :


    Can't send external Icinga command to the local command file "/var/run/icinga2/cmd/icinga2.cmd": No such file or directory.


    Hi folks,
    I managed to install those two modules "talamoig/icingaweb2" and "talamoig/icinga" in different hosts with connection to a remote MySql server, now that I can authenticate through icingaweb2 with my admin credentials for which I granted the permissions to everything "*".


    Now when I activate the modules "setup" or "monitoring" a problem occurs and I can't find a clue for that..


    For setup module:

    Code
    1. Could not enable module "setup"
    2. While operation the following error occurred:
    3. Cannot enable module "setup". Check the permissions for the enabledModules directory: /etc/icingaweb2/enabledModules
    4. This could have one or more of the following reasons:
    5. No file permissions to write into module directory
    6. Errors on filesystems: Mount points, operational errors
    7. General application error
    8. Details can be seen in your application log (if you don't have access to this file, call your administrator in this case).


    for monitoring module:


    Code
    1. Could not enable module "monitoring"
    2. While operation the following error occurred:
    3. Cannot enable module "monitoring". Check the permissions for the enabledModules directory: /etc/icingaweb2/enabledModules
    4. This could have one or more of the following reasons:
    5. No file permissions to write into module directory
    6. Errors on filesystems: Mount points, operational errors
    7. General application error
    8. Details can be seen in your application log (if you don't have access to this file, call your administrator in this case).

    Hey folks,
    I'm currently performing some API tests and now I'm stucked with this dashing-Icinga2 https://github.com/icinga/dashing-icinga2
    So everything works good but the dashboard doesn't show metrics, it's empty. I even adjusted the credentials settings in jobs/Icinga2.erb


    Man it depends on the infrastructure you are working on, if the data are highly sensitive and that you have to secure your monitoring system very well and even for my case so Radius + otp is fair enough to implement.

    Hey folks,
    I want to setup a highly secured method for login to Icinga2, so I have an authentication service (RADIUS/ LDAP/ OTP) and in the other hand Icinga2 configured with LDAP.
    But the question is: how can I send Icinga2 credentials (Password+otp) to that Radius server ?


    Thanks,


    Paranoid SysAdm