Director background service not starting after switching to new database server

Icinga 2 Icinga DB
,
1

I am running icinga version: r2.14.3-1

Actually i have a issue with the background service.
After relocating my icinga databases to a new mariadb server my director background service stopped.
Reinstalling the service didn’t fix the problem.
Switching back to the old databases didn’t work either.
As director names a PID, is there an other method as Background-Daemon
to revive the background service.

icinga2 feature list
Disabled features: compatlog debuglog elasticsearch gelf icingadb influxdb influxdb2 journald opentsdb syslog
Enabled features: api checker command graphite ido-mysql livestatus mainlog notification perfdata

2

Can you just start the director background service with this?

systemctl enable --now icinga-director

afterwards you might want to verify the status:

systemctl status icinga-director
3

Job for icinga-director.service failed because the control process exited with error code. See “systemctl status icinga-director.service” and “journalctl -xe” for details.

– Unit icinga-director.service has begun starting up.
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: PHP Fatal error: Uncaught Error: Call to a member function translate() on null in /usr/share/php/Icinga/Application/functions.php:35
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: Stack trace:
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #0 /usr/share/php/Icinga/Application/Config.php(329): t(‘Cannot read con…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #1 /usr/share/php/Icinga/Application/Config.php(398): Icinga\Application\Config::fromIni(‘/etc/icingaweb2…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #2 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(555): Icinga\Application\Config::app()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #3 /usr/share/php/Icinga/Application/Cli.php(42): Icinga\Application\ApplicationBootstrap->loadConfig()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #4 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(388): Icinga\Application\Cli->bootstrap()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #5 /usr/bin/icingacli(7): Icinga\Application\ApplicationBootstrap::start(‘/usr/share/icin…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #6 {main}
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: thrown in /usr/share/php/Icinga/Application/functions.php on line 35
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: Fatal error: Uncaught Error: Call to a member function translate() on null in /usr/share/php/Icinga/Application/functions.php:35
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: Stack trace:
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #0 /usr/share/php/Icinga/Application/Config.php(329): t(‘Cannot read con…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #1 /usr/share/php/Icinga/Application/Config.php(398): Icinga\Application\Config::fromIni(‘/etc/icingaweb2…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #2 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(555): Icinga\Application\Config::app()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #3 /usr/share/php/Icinga/Application/Cli.php(42): Icinga\Application\ApplicationBootstrap->loadConfig()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #4 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(388): Icinga\Application\Cli->bootstrap()
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #5 /usr/bin/icingacli(7): Icinga\Application\ApplicationBootstrap::start(‘/usr/share/icin…’)
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: #6 {main}
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de icingadirector[36170]: thrown in /usr/share/php/Icinga/Application/functions.php on line 35
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de systemd[1]: icinga-director.service: main process exited, code=exited, status=255/n/a
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de systemd[1]: Failed to start Icinga Director - Monitoring Configuration.
– Subject: Unit icinga-director.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit icinga-director.service has failed.

– The result is failed.
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de systemd[1]: Unit icinga-director.service entered failed state.
Jan 30 15:24:11 chv-m001-ic01.chv-intern.de systemd[1]: icinga-director.service failed.
Jan 30 15:24:20 chv-m001-ic01.chv-intern.de icingaweb2[10329]: Failed to load pending migrations: UnexpectedValueException in /usr/share/php/Icinga/Application/Hook/DbMigrationHook.php:306 with message: DirectoryItera
lines 1555-1600/1600 (END)

4

● icinga-director.service - Icinga Director - Monitoring Configuration
Loaded: loaded (/etc/systemd/system/icinga-director.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Do 2025-01-30 15:25:12 CET; 14s ago
Docs: Introduction - Icinga Director
Process: 36723 ExecStart=/usr/bin/icingacli director daemon run (code=exited, status=255)
Main PID: 36723 (code=exited, status=255)
CGroup: /system.slice/icinga-director.service

Jan 30 15:25:12 chv-m001-ic01.chv-intern.de systemd[1]: Failed to start Icinga Director - Monitoring Configuration.
Jan 30 15:25:12 chv-m001-ic01.chv-intern.de systemd[1]: Unit icinga-director.service entered failed state.
Jan 30 15:25:12 chv-m001-ic01.chv-intern.de systemd[1]: icinga-director.service failed.