Trying to start the Director Daemon v1.7.2 - "DB configuration is not valid"

[darkounet]

Expected Behavior

Trying to start the Director Daemon v1.7.2

Current Behavior

root@icingaweb2:/# icingacli director daemon run 
DB configuration is not valid

Steps to Reproduce (for bugs)

root@icingaweb2:/# icingacli director daemon run --debug --trace
Running without systemd
DB configuration is not valid

^CShutting down
DB has been disconnected, shutdown finished

Your Environment

Docker

• Director version (System - About): v1.7.2
• Icinga Web 2 version and modules (System - About):
• Icinga 2 version (icinga2 --version):
• Operating System and version: Debian Buster
• Webserver, PHP versions: php7.3

root@icingaweb2:/# dpkg -l |grep icingaweb2
ii  icingaweb2                    2.7.3-1.buster               all          simple and responsive web interface for Icinga
ii  icingaweb2-common             2.7.3-1.buster               all          simple and responsive web interface for Icinga - common files
ii  icingaweb2-module-doc         2.7.3-1.buster               all          simple and responsive web interface for Icinga - documentation module
ii  icingaweb2-module-monitoring  2.7.3-1.buster               all          simple and responsive web interface for Icinga - monitoring module

root@icingaweb2:/# icingacli module list
MODULE         VERSION   STATE     DESCRIPTION
director       1.7.2     enabled   Director - Config tool for Icinga 2
incubator      0.5.0     enabled   Incubator provides bleeding-edge libraries
ipl            v0.3.0    enabled   The Icinga PHP library
itop           0.1.1     enabled   iTop for Icinga Director
monitoring     2.7.3     enabled   Icinga monitoring module
reactbundle    0.7.0     enabled   ReactPHP-based 3rd party libraries
setup          2.7.3     enabled   Setup module

My director is working fine, except for the background daemon.

The DB is correct and all migrations are done, no pending one. try with root, non root ( icingadirector user )

I have a docker for icinga2 master & a docker for icingaweb2. What am I doing wrong ?

Thanks

[bahamut45]

👍

[bahrpatrick]

I have the same problem.

[darkounet]

up ?

[stevie-sy]

Because this is a bug tracker for the developers. Possible it's a configuration problem. So you should ask the question in the community https://community.icinga.com ;-)
I think you get there faster a answer how to fix it. I'm not in common with docker, so I can't help you. I can only give you this hint. Because we got/foun some help/Solutions there for our Problems.

[darkounet]

Please ... help ... 🆘

[Thomas-Gelf]

Please provide:

• the path to your Icinga Web 2 configuration if different from /etc/icingaweb2
• the output of echo $ICINGAWEB_CONFIGDIR

[Thomas-Gelf]

As you're running docker, could you please share your Dockerfile? How is the director daemon started?

[darkounet]

The icingaweb2 path is /etc/icingaweb2 the $ICINGAWEB_CONFIGDIR is not set.

The Dockerfile run the daemon with :

/usr/bin/icingacli director daemon run

[preske87]

Not sure if this helps, but I am facing the same issue...

Does anyone have a solution for it meanwhile?

[preske87]

I meanwhile found the issue, and it was rather frustrating.

In my environment I was setting the password for the icinga director through docker-compose file. This password unfortunately as I spotted contained some special characters, I assume the "%" is the trap. This led into the experienced issue. Setting another password and all is fine.

docker-compose with environment variable ICINGA2_FEATURE_DIRECTOR_PASS set to directorPassword: all good

docker-compose with environment variable ICINGA2_FEATURE_DIRECTOR_PASS set to a more complex password yJzas!CC*x%a: