You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If i type the following command: /usr/bin/icingacli vspheredb daemon run. The Daemon dont start and give errors. Also with systemctl start icinga-vspheredb. The same output. The Output is:
`PHP Fatal error: Uncaught Error: Class 'gipfl\SystemD\NotifySystemD' not found in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php:80
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Module\Vspheredb\Daemon\Daemon->run() #1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAction() #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 80
Fatal error: Uncaught Error: Class 'gipfl\SystemD\NotifySystemD' not found in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php:80
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Module\Vspheredb\Daemon\Daemon->run() #1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAction() #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 80
`
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Your Environment
VMware vCenter®/ESXi™-Version: ESXi 6.7 and ESXi 6.5
Version/GIT-Hash of this module:
Icinga Web 2 version: 2.5.0
Operating System and version: Debian 9.4
Webserver, PHP versions: Apache 2.4, PHP 7.0
The text was updated successfully, but these errors were encountered:
Expected Behavior
If i type the following command: /usr/bin/icingacli vspheredb daemon run. The Daemon dont start and give errors. Also with systemctl start icinga-vspheredb. The same output. The Output is:
`PHP Fatal error: Uncaught Error: Class 'gipfl\SystemD\NotifySystemD' not found in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php:80
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Module\Vspheredb\Daemon\Daemon->run()
#1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAction()
#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 80
Fatal error: Uncaught Error: Class 'gipfl\SystemD\NotifySystemD' not found in /usr/share/icingaweb2/modules/vspheredb/library/Vspheredb/Daemon/Daemon.php:80
Stack trace:
#0 /usr/share/icingaweb2/modules/vspheredb/application/clicommands/DaemonCommand.php(26): Icinga\Module\Vspheredb\Daemon\Daemon->run()
#1 /usr/share/php/Icinga/Cli/Loader.php(265): Icinga\Module\Vspheredb\Clicommands\DaemonCommand->runAction()
#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 80
`
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: