My icingaweb 2 will automatically update. And after this icingaweb will breaked. I will turn off all module and work will fine. But old modules: pnp, cube, buisnessprocess, idoreports, nagvis, vsphere not work. It typed: Unmet dependencies found! Module can’t be enabled unless all dependencies are met.
Модули monitoring>=2.4.1 * (not installed)
What i must do to work with modules, what i used all this time?
I,m upgrade incubator from git to 0.6.0 and enable modules in console, now work fine. In web text " Unmet dependencies found! Module can’t be enabled unless all dependencies are met.
Модули monitoring>=2.4.1 * (not installed)" will state, but modules work. Platform Centos8 stream 64x
Just some quick notes:
Facing the same issues running at Ubuntu 18 (LTS).
Yes.
Additionally, problems with the icinga.min.css occur (saying wrong MIME-Type, because “text/html” was set and not “text/css”).
Icingaweb2 is unusable so (due a lack of time) I will restore a backup.
No, not on purpose. It seems that it disappeared after the upgrade via apt.
It was in the nightly backup, so it could be simply restored.
However, I couldn’t see any operations in the apt history or the deb-packages I looked at, which may have caused this.
Maybe I missed something, but I am quite sure that you can ignore my previous answer.
Upgrade to last git will help. But many modules not “disable/enable” from web, it will not see monitoring plugin or director(master). But it can enabled from console “icingacli module enable …”
Icinga Web 2 Version 2.9.0 introduced dependency checks for modules. If a module requires a dependency, this dependency needs to be installed and enabled first in order to enable the module.
If the Director is the dependency, and you have installed the master, consider installing the latest release instead. If you really have to use the master, your only chance is to enable the requiring module using the CLI tool.
The big pie charts are due to the use of an outdated stylesheet by your browser. Icinga Web 2 provides its own cache for this, so if you have your own cache set up, add an exclude rule for the stylesheet (and JS). If you don’t have an extra cache, Logout/Login may help as @aaron mentioned. You can also perform a force-refresh.
I have the same issue, even the login doesn’t look good. Neither a reboot, logout, and login nor clear the cache doesn’t work.
I also tried a different browse (IE) and got the same picture.
I can Update the whole system but non of this packeges:
icingacli/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
icingaweb2-common/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
icingaweb2-module-doc/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
icingaweb2-module-monitoring/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
icingaweb2/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
php-icinga/icinga-focal,icinga-focal 2.9.0-1.focal all [aktualisierbar von: 2.8.2-1.focal]
The missing style (broken login) may be due the use of the businessprocess module < v2.3.1 or the vspheredb module < v1.0.4. Upgrade those and the style should be ok again.
If the monitoring module is also gone in your case, please show a full apt upgrade log.