Configuration is:
Icinga Web 2 Version
2.8.2
Git Commit
8a89839af94a247ee2149b2336c73b8251b477c0
PHP-Version
7.2.24-0ubuntu0.18.04.7
Git Commit Datum
2020-08-17
Is the v prefixing the version number triggering the error?
No.
It’s how the ipl is now expected to be integrated into Icinga Web 2. Previously it’s been a module (i.e. what you’ve installed). Now in the master branch it’s expected to be a library. The dependency check looks for the library, not for the module.
Though, it’s only the dependency check that’s complaining. You can circumvent this by enabling the module using the CLI: icingacli module enable icingadb
Oh and before you do that and expect that Icinga DB Web works fine , please install the nightly/master branch of the ipl module instead of the v0.5.0. (Which was created for the RC of Icinga DB)
Hi Johannes,
OK, I got some steps further, but still have to cancel my trys for now.
I replaced the modules/ipl with the current nightly/master
I disabled/enabled ipl
Now I get some errors when using icingacli for missing dependencies for vsphere & director
I enabled icingadb
I started the services icingadb and icingadb-redis
Configuration of icingadb was possible & verified (Connection to redis)
I see the new menu item icingadb
UI was a bit mixed up, I tried clearing the cache
That broke the UI & CSS files were not loaded anymore (Barrier free to it’s best…)
Not sure what caused this, but I reverted the steps & got a running system.
My guess is, that the ipl module/library somehow is not compatible with every other module after being upgraded. Please don’t hesitate, if you want me to look deeper into the issue.
Yes, of course. You’re essentially using a non-stable environment by using a master branch. It’s not guaranteed that this will work out of the box with other modules than Icinga DB Web. If you want to try out the current state of Icinga DB Web, you should setup this in a different (Web) installation than the one you’re using for Director and other modules.
Regarding the CSS issue, please enable the DEBUG log and take a look at it. There should appear some errors by which it’s easier for me to tell what’s wrong.
This error might have occurred because module “icingadb” has unmet dependencies. Please check it’s installation instructions and install missing dependencies.
Hi Johannes,
I’m also not able to configure command transports for the icingadb module.
When clicking on the confoguration tab the following error is shown:
Uncaught Error: Class ‘Icinga\Module\Icingadb\Common\EmptyState’ not found in /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Common/BaseOrderedItemList.php:30
Stack trace: #0 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/HtmlDocument.php(260): Icinga\Module\Icingadb\Common\BaseOrderedItemList->assemble() #1 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/HtmlDocument.php(461): ipl\Html\HtmlDocument->ensureAssembled() #2 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/HtmlDocument.php(304): ipl\Html\HtmlDocument->render() #3 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/BaseHtmlElement.php(255): ipl\Html\HtmlDocument->renderUnwrapped() #4 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/BaseHtmlElement.php(339): ipl\Html\BaseHtmlElement->renderContent() #5 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/HtmlDocument.php(463): ipl\Html\BaseHtmlElement->renderUnwrapped() #6 /usr/share/icingaweb2/modules/ipl/vendor/ipl/html/src/HtmlDocument.php(304): ipl\Html\HtmlDo
This error might have occurred because module “icingadb” has unmet dependencies. Please check it’s installation instructions and install missing dependencies.
I should learn to read… I pulled the master/nightly of IcingaWeb2 & couldn’t see any changes. Today I thought, let try a pull on the icingadbweb & voila: It works!