Director deploments hangs "Unknown, waiting for the result of the configuration check"

Hello,

my Icinga2 installation looks like this:

icinga2 - The Icinga 2 network monitoring daemon (version: r2.10.3-1)

System information:
Platform: Debian GNU/Linux
Platform version: 10 (buster)
Kernel: Linux
Kernel version: 4.19.0-16-amd64
Architecture: x86_64

Enabled features: api checker compatlog ido-mysql mainlog notification

Icinga Web 2 Version 2.6.2

director: master
incubator: 0.6.0
ipl: 0.4.0
reactbundle: 0.7.0

If I want to roll out changes from the activity log, the process is permanently under Deployments. The command

icingacli director config deploy --force --debug --benchmark

produces further pending deployments and the following output:

Config matches active stage, deploying anyway
Config 'b175ca0562434deeb4fb1fc03fd80cd7361b56df' has been deployed
+--------------+------------------------------------------+-------------+---------------+-------------+-------------+
| Time         | Description                              |    Off (ms) |      Dur (ms) |  Mem (diff) | Mem (total) |
+--------------+------------------------------------------+-------------+---------------+-------------+-------------+
| 12:14:23.702 | Bootstrap, autoloader registered         |       0.001 |         0.001 |  556.73 KiB |  556.73 KiB |
| 12:14:23.706 | Dispatching CLI command                  |       3.935 |         3.934 |  400.82 KiB |  957.55 KiB |
| 12:14:23.717 | Prepare "endpoint" Template Tree         |      15.426 |        11.491 |    2.09 MiB |    3.03 MiB |
| 12:14:23.718 | "endpoint" Template Tree ready           |      15.607 |         0.181 |    848.00 B |    3.03 MiB |
| 12:14:23.722 | Prefetching zone                         |      20.112 |         4.505 |  684.08 KiB |    3.70 MiB |
| 12:14:23.722 | Generating zones: 5                      |      20.413 |         0.301 |   41.74 KiB |    3.74 MiB |
| 12:14:23.722 | zones done                               |      20.432 |         0.019 |   1112.00 B |    3.74 MiB |
| 12:14:23.722 | Prefetching endpoint                     |      20.433 |         0.001 |    816.00 B |    3.74 MiB |
| 12:14:23.723 | Generating endpoints: 2                  |      20.528 |         0.095 |    5.19 KiB |    3.74 MiB |
| 12:14:23.723 | endpoints done                           |      20.533 |         0.005 |   1056.00 B |    3.74 MiB |
| 12:14:23.723 | Prefetching command                      |      20.534 |         0.001 |    736.00 B |    3.75 MiB |
| 12:14:23.724 | Generating commands: 216                 |      21.728 |         1.194 |  510.66 KiB |    4.24 MiB |
| 12:14:23.724 | commands done                            |      22.018 |         0.290 |    736.00 B |    4.24 MiB |
| 12:14:23.724 | Prefetching timePeriod                   |      22.019 |         0.001 |    816.00 B |    4.25 MiB |
| 12:14:23.724 | Prefetching hostGroup                    |      22.274 |         0.255 |   38.04 KiB |    4.28 MiB |
| 12:14:23.725 | Prefetching host                         |      22.539 |         0.265 |   55.25 KiB |    4.34 MiB |
| 12:14:23.725 | Prefetching serviceGroup                 |      23.194 |         0.655 |   87.01 KiB |    4.42 MiB |
| 12:14:23.725 | Prefetching service                      |      23.380 |         0.186 |   28.18 KiB |    4.45 MiB |
| 12:14:23.726 | Prefetching serviceSet                   |      23.961 |         0.581 |  159.42 KiB |    4.60 MiB |
| 12:14:23.726 | Prefetching userGroup                    |      24.453 |         0.492 |   78.62 KiB |    4.68 MiB |
| 12:14:23.727 | Prefetching user                         |      24.629 |         0.176 |   28.22 KiB |    4.71 MiB |
| 12:14:23.727 | Prefetching notification                 |      24.798 |         0.169 |   27.76 KiB |    4.74 MiB |
| 12:14:23.727 | Prefetching dependency                   |      25.096 |         0.298 |   43.66 KiB |    4.78 MiB |
| 12:14:23.727 | Prefetching scheduledDowntime            |      25.500 |         0.404 |   73.09 KiB |    4.85 MiB |
| 12:14:23.729 | Rest Api, sending                        |      26.534 |         1.034 | -387.34 KiB |    4.47 MiB |
| 12:14:23.775 | Rest Api, got response                   |      73.281 |        46.747 |    672.00 B |    4.47 MiB |
| 12:14:23.776 | Rest Api, sending config/packages        |      73.610 |         0.329 |   16.52 KiB |    4.49 MiB |
| 12:14:23.776 | Rest Api, got response                   |      74.150 |         0.540 |    4.16 KiB |    4.49 MiB |
| 12:14:23.776 | Rest Api, sending config/packages        |      74.193 |         0.043 |   -4.12 KiB |    4.49 MiB |
| 12:14:23.777 | Rest Api, got response                   |      74.582 |         0.389 |    416.00 B |    4.49 MiB |
| 12:14:23.777 | Rest Api, sending config/packages        |      75.029 |         0.447 |    3.59 KiB |    4.49 MiB |
| 12:14:23.777 | Rest Api, got response                   |      75.389 |         0.360 |    416.00 B |    4.49 MiB |
| 12:14:23.777 | Rest Api, sending config/stages/director |      75.496 |         0.107 |    8.79 KiB |    4.50 MiB |
| 12:14:23.779 | Rest Api, got response                   |      76.762 |         1.266 |   -2.09 KiB |    4.50 MiB |
| 12:14:23.810 | All done                                 |     108.502 |        31.740 |  -10.95 KiB |    4.49 MiB |
+--------------+------------------------------------------+-------------+---------------+-------------+-------------+

These deployment processes never end and do not show any final deployment details. How can the problem be solved?

Best regards

Andy

Is the background daemon of the Director running? With 1.8.0 it got mandatory and is used to get data from Icinga 2!

How I can verify the background daemon of the Direktor? Is there a special command?

I followed this manual https://icinga.com/docs/icinga-director/latest/doc/75-Background-Daemon/, but the deployment processes are still running.

When I start the background daemon I will see

 # systemctl status icinga-director.service
● icinga-director.service - Icinga Director - Monitoring Configuration
   Loaded: loaded (/etc/systemd/system/icinga-director.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2021-04-28 17:20:29 CEST; 4min 35s ago
     Docs: https://icinga.com/docs/director/latest/
 Main PID: 29252 (icingacli)
   Status: "running, db: no configuration"
    Tasks: 1 (limit: 4915)
   Memory: 10.5M
   CGroup: /system.slice/icinga-director.service
           └─29252 icinga::director: running, db: no configuration

Apr 28 17:20:28 monitor systemd[1]: Starting Icinga Director - Monitoring Configuration...
Apr 28 17:20:29 monitor systemd[1]: Started Icinga Director - Monitoring Configuration.
Apr 28 17:20:29 monitor icingadirector[29252]: DB configuration is not valid

And the problem is still the same.

There seems to be some problem with the daemon getting the database configuration.

Hmm,
your answer isn’t not really helpful, because I can also read log files. The question is why the daemon doesn’t get a database configuration. In the docs of the director module the explanations or the correct way are missing.
I found something very hidden this solution:

usermod -a -G nagios,www-data icingadirector
chmod 0755 /etc/icingaweb2/modules/director
systemctl restart icinga2.service
systemctl start icinga-director.service