I am trying to install the notifications module and have run into an issue where the ipl and icinga-php-thirdparty modules show version 0.0.0, even though they are correctly installed.
My System:
OS: SUSE Linux Enterprise
Icinga Web 2 Version: 2.12.5
Problem:
ipl is required to be ≥0.15.0, but shows 0.0.0.
icinga-php-thirdparty is required to be ≥0.12.0, but shows 0.0.0.
Troubleshooting Steps Taken:
Cloned the modules fresh from GitHub (ipl and icinga-php-thirdparty).
Checked out the correct version tags (v0.15.0 for ipl, v0.12.0 for thirdparty).
Manually created the .version files using echo "0.15.0" > .../.version.
Verified with cat that the .version files exist and contain the correct content.
Set file ownership recursively to wwwrun:icingaweb2 with chown, matching other working modules.
Restarted apache2 multiple times.
Manually cleared the Icinga Web 2 cache by running rm -rf /var/cache/icingaweb2/*.
Despite all these steps, icingacli module list continues to report the versions as 0.0.0.
May I ask how you come to that conclusion? None of the steps you showed are recommended let alone the installation method. Did you follow a guide from somewhere on the internet?
Cloned the modules fresh from GitHub (ipl and icinga-php-thirdparty).
They’re not modules. I’ll get to that below.
Checked out the correct version tags (v0.15.0 for ipl, v0.12.0 for thirdparty).
Okay, for a git installation required.
Manually created the .version files using echo "0.15.0" > .../.version.
What is a .version file? Why do you think this has any effect?
Despite all these steps, icingacli module list continues to report the versions as 0.0.0 .
Yeah, well, because they’re not modules. They’re libraries, and those are handled differently. Again, what installation guide did you follow? Or why did you choose to clone the git repositories?
Libraries have to be put in /usr/share/icinga-php/ by default. This is also documented in each repository’s README.md.
Honestly, I think you’re better off using packages.