Hi there,
I just upgraded to the new 1.7.x release of Director from GIT (using master), installed the dependencies and ran the DB schema migration scripts. No problems, everything went flawless.
As the new background daemon is mandatory to set up, I followed the instructions in the documentation.
Starting the daemon with service icinga-director start does not immediately return an error, but icingaweb2 complains about the daemon not running.
A check with “service icinga-director status” yields: Oct 07 12:44:52 ifbsapnag systemd[1]: Starting Icinga Director - Monitoring Configuration... Oct 07 12:44:52 ifbsapnag icingadirector[7838]: Started by systemd, notifying watchdog every 5s via /run/systemd/notify Oct 07 12:44:52 ifbsapnag systemd[1]: Started Icinga Director - Monitoring Configuration. Oct 07 12:44:52 ifbsapnag icingadirector[7838]: DB configuration is not valid
But my director DB config seems valid when checking in the ressources section.
What puzzles me most ist that running icingacli director daemon run
as root does obviously start the daemon successfully, as icingaweb2 recognizes the PID and related information.
What can I check to get the process running as icingadirector user as proposed by the documentation?
Manfred,
thanks for your reply.
But as I said above I followed the documentation (and did create the icingadirector user, of course)
Anyway, got it working now - but I am unsure about what did the trick
added nagios group to icingadirector user
added www-data group to icingadirector user
bounced icinga2 service
stopped and startet icinga-director service
Anyway, it’s working now as expected. Problem solved
The RPM package uses the icingaweb2 by default for this purpose. Seems you have modified the permissions or used a different source to install Icinga Web.
