-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP ini parser doesn't strip trailing whitespace #3733
Comments
Please take a look into the monitoring module's configuration. ( The resource configured there is probably corrupted somehow. By choosing the correct one it should work. (If you're provisioning this by e.g. puppet you need to fix it there as well.) If it doesn't help please share your |
If I open the Transport Tab I see two Backends: Monitoring and Transport, both named icinga2. This is the configuration before the update (2.6.1-1jessie) This is the configuration after the update (2.6.2-1jessie) If I try to show the resource configuration for icingaweb_db, I get the error "Ressource not found" with this trace:
After setting Resource back to icinga_ido, everything works again. So finally this seems to be a quirk in the update process, not a real bug. |
Neither a quirk nor a bug in Icinga Web 2. Though, a bug in PHP. It's fixed in v7.1.22. Usually not a problem because Web 2 itself doesn't write configuration that will cause this bug. I guess you've defined your configuration somehow else. (Either by hand or with some other tool) Future versions of Icinga Web 2 may include a work-around if the fix will not be backported. |
Affected versions: 5.3.0 - 5.3.14, 5.3.20 - 5.4.4, 5.4.10 - 5.6.40, 7.0.0 - 7.1.23, 7.2.0 - 7.2.11 Seems we need said work-around... |
I upgraded my debian installation with the following versions:
Expected Behavior
The upgrade should worked flawlessly.
Current Behavior
An all pages with icinga data icingaweb shows the following error:
icingacli shows an matching error message:
Possible Solution
I did not find any, but downgrading only the icingaweb2 packages resolves the problem
Steps to Reproduce (for bugs)
Your Environment
icinga2 feature list
):I can validate the connection from the configuration pages in icingaweb2:
Error message screenshot:
The text was updated successfully, but these errors were encountered: