Unable to start daemon after setup

[ChristianMoritz]

after the upgrade to the new director version 1.60 i want to install the new vsperhdb plugin...
db is created modeule is downloaded with git.
module is activated.
db shema is done.
but im unable to start the daemon.

Current Behavior

root@smon03:/usr/bin# icingacli vspheredb daemon run
PHP Fatal error: Uncaught Error: Class 'React\EventLoop\Factory' not found in /usr/share/icingaweb2/m odules/vspheredb/library/Vspheredb/Daemon/Daemon.php:75
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Modul e\Vspheredb\Daemon\Daemon->run()
#1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAc tion()
#2 /usr/share/php/Icinga/Application/Cli.php(149): Icinga\Cli\Loader->dispatch()
#3 /usr/share/php/Icinga/Application/Cli.php(139): Icinga\Application\Cli->dispatchOnce()
#4 /usr/bin/icingacli(7): Icinga\Application\Cli->dispatch()
#5 {main}
thrown in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php on line 75

Fatal error: Uncaught Error: Class 'React\EventLoop\Factory' not found in /usr/share/icingaweb2/module s/vspheredb/library/Vspheredb/Daemon/Daemon.php:75
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Modul e\Vspheredb\Daemon\Daemon->run()
#1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAc tion()
#2 /usr/share/php/Icinga/Application/Cli.php(149): Icinga\Cli\Loader->dispatch()
#3 /usr/share/php/Icinga/Application/Cli.php(139): Icinga\Application\Cli->dispatchOnce()
#4 /usr/bin/icingacli(7): Icinga\Application\Cli->dispatch()
#5 {main}
thrown in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php on line 75
root@smon03:/usr/bin#

root@smon03:/# php -i | grep pcntl
pcntl
pcntl support => enabled

Possible Solution

Steps to Reproduce (for bugs)

Your Environment

• VMware vCenter®/ESXi™-Version: 6.5
• Version/GIT-Hash of this module: 1.6
• Icinga Web 2 version: 2.6.2
• Operating System and version: ubuntu 16.04
• Webserver, PHP versions: 7.0

[Thomas-Gelf]

Please double-check the requirements, especially reactbundle. The shown hint is important, you MUST check out or download a tagged release and not the master branch for reactbundle, ipl and incubator.

[ChristianMoritz]

retested...

ipl 0.1.1, incubator 0.1.1 & reactbundle 0.4.1are all installed.
here is the error...

COMMAND: systemctl start icinga-vspheredb

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

COMMAND: systemctl status icinga-vspheredb.service

● icinga-vspheredb.service - Icinga vSphereDB Daemon
Loaded: loaded (/etc/systemd/system/icinga-vspheredb.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2018-12-17 16:27:29 CET; 7s ago
Docs: https://icinga.com/docs/icinga-vsphere/latest/
Process: 30663 ExecStart=/usr/bin/icingacli vspheredb daemon run (code=exited, status=217/USER)
Main PID: 30663 (code=exited, status=217/USER)

systemd[1]: icinga-vspheredb.service: Main process exited, code=exited, status=217/USER
systemd[1]: Failed to start Icinga vSphereDB Daemon.
systemd[1]: icinga-vspheredb.service: Unit entered failed state.
systemd[1]: icinga-vspheredb.service: Failed with result 'exit-code'.

daemon service file is copied to: /etc/systemd/system/
daemon service is reloaded as well.

COMMAND: journalctl -xe

-- Subject: Unit icinga-vspheredb.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has finished shutting down.
Dec 17 16:33:15 smon03 systemd[1]: Starting Icinga vSphereDB Daemon...
-- Subject: Unit icinga-vspheredb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has begun starting up.
Dec 17 16:33:15 smon03 systemd[2248]: icinga-vspheredb.service: Failed at step USER spawning /usr/bin/icingacli: No such process
-- Subject: Process /usr/bin/icingacli could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- The process /usr/bin/icingacli could not be executed and failed.

-- The error number returned by this process is 3.
Dec 17 16:33:15 smon03 systemd[1]: icinga-vspheredb.service: Main process exited, code=exited, status=217/USER
Dec 17 16:33:15 smon03 systemd[1]: Failed to start Icinga vSphereDB Daemon.
-- Subject: Unit icinga-vspheredb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has failed.

-- The result is failed.
Dec 17 16:33:15 smon03 systemd[1]: icinga-vspheredb.service: Unit entered failed state.
Dec 17 16:33:15 smon03 systemd[1]: icinga-vspheredb.service: Failed with result 'exit-code'.
Dec 17 16:33:45 smon03 systemd[1]: icinga-vspheredb.service: Service hold-off time over, scheduling restart.
Dec 17 16:33:45 smon03 systemd[1]: Stopped Icinga vSphereDB Daemon.
-- Subject: Unit icinga-vspheredb.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has finished shutting down.
Dec 17 16:33:45 smon03 systemd[3172]: icinga-vspheredb.service: Failed at step USER spawning /usr/bin/icingacli: No such process
-- Subject: Process /usr/bin/icingacli could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- The process /usr/bin/icingacli could not be executed and failed.

-- The error number returned by this process is 3.
Dec 17 16:33:45 smon03 systemd[1]: Starting Icinga vSphereDB Daemon...
-- Subject: Unit icinga-vspheredb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has begun starting up.
Dec 17 16:33:45 smon03 systemd[1]: icinga-vspheredb.service: Main process exited, code=exited, status=217/USER
Dec 17 16:33:45 smon03 systemd[1]: Failed to start Icinga vSphereDB Daemon.
-- Subject: Unit icinga-vspheredb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit icinga-vspheredb.service has failed.

-- The result is failed.
Dec 17 16:33:45 smon03 systemd[1]: icinga-vspheredb.service: Unit entered failed state.
Dec 17 16:33:45 smon03 systemd[1]: icinga-vspheredb.service: Failed with result 'exit-code'.
Dec 17 16:33:52 smon03 sshd[3381]: Connection closed by 127.0.0.1 port 54490 [preauth]
lines 1792-1854/1854 (END)

[Thomas-Gelf]

status=217/USER -> guess there is no icingaweb2 user on your system. As mentioned here the sample Unit-file we ship expects such. Alternatively please change the Unit-file and tell systemd to use a user allowed read /etc/icingaweb2. The documentation mentions some possible options.

NB: Whenever modifying a Unit-file please do not forget to systemctl daemon-reload.

[ChristianMoritz]

thx for the tip... ive changed insight the "icinga-vspheredb.service" file the user to apache.. now it works like a charm.

[Thomas-Gelf]

Glad to hear that, you're welcome!