Icinga Web 2.6.3

Icinga Web 2.6.3

We are happy to announce a new bugfix release for Icinga Web 2. Official packages are available on packages.icinga.com. Community repositories might need a while to catch up.

You can find issues related to this release on our Roadmap.

 

PHP 7.3

Now supported.

 

LDAP – Community contributions, that’s the spirit

With the help of our users we’ve finally fixed the issue that defining multiple hostnames and enabling STARTTLS has never properly worked. Also, they’ve identified that defining multiple hostnames caused a customized port not being utilized and fixed it themselves.

There has also a rare case been fixed that caused no group members being found in case object classes had a different casing than what we expected. (Good news for all the non-OpenLdap and non-MSActiveDirectory users)

  • LDAP connection fails with multiple servers using STARTTLS #3639
  • LDAPS authentication ignores custom port setting #3713
  • LDAP group members not found #3650

 

We take care about your data even better now

With this are newlines and HTML entities (such as  ) in plugin output and custom variables meant. Sorry if I’ve teased some data security folks now.

  • Newlines in plugin output disappear #3662
  • Windows path separators are converted to newlines in custom variables #3636
  • HTML entities in plugin output are not resolved if no other HTML is there #3707

 

You’ve wondered how you got into a famous blue police box?

Don’t worry, not only you and the european union are sometimes unsure what’s the correct time.

  • Set client timezone on DB connection #3525
  • Ensure a valid default timezone is set in any case #3747
  • Fix that the event detail view is not showing times in correct timezone #3660

 

UI – The portal to your monitoring environment, improved

The collapsible sidebar introduced with v2.5 has been plagued by some issues since then. They’re now fixed. Also, the UI should now flicker less and properly preserve the scroll position when interacting with action links. (This also allows the business process module to behave more stable when using drag and drop in large configurations.)

  • Collapsible Sidebar Issues #3187
  • Fix title when closing right column #3654
  • Preserve scroll position upon form submits #3661

 

Corrected things we’ve broke recently

That’s due to preemptive changes to protect you from bad individuals. Unfortunately this meant that some unforeseen side-effects appeared after the release of v2.6.2. These are now fixed.

  • Multiline values in ini files broken #3705
  • PHP ini parser doesn’t strip trailing whitespace #3733
  • Escaped characters in INI values are not unescaped #3648

Though, if you’ve faced issue #3705 you still need to take manual action (if not already done) as the provided fix does only prevent further occurrences of the resulting error. The required changes involve the transformation of all real newlines in Icinga Web 2’s INI files to literal \n or \r\n sequences. (Files likely having such are the roles.ini and announcements.ini)

Icinga 2 v2.7.2 Release

We just released another minor bugfix release for Icinga 2. In addition to providing a number of documentation enhancements version 2.7.2 addresses a few bugs. A list of changes can be found here.
Packages for Icinga 2 v2.7.2 for the officially supported distributions should be available shortly.

Icinga 2.6.1 Release

We have just released another minor update for Icinga 2. Version 2.6.1 addresses a number of issues we identified in 2.6.0 and is also at the same time the first release after our recent migration to GitHub.
Two of the fixes in this version are for crash bugs which affect reloading Icinga and passing unusually large amounts of command arguments or environment variables to child processes. There are also some documentation changes and a few other smaller bug fixes. Unlike with previous minor releases we decided not to include any ITL changes this time.
An exhaustive list of all tickets solved in 2.6.1 can be found on GitHub. Packages for 2.6.1 should become available shortly.
There’s also a recently-released new version of Icinga Web 2 (2.4.1) which introduces fixes for a few minor problems our users have reported.

Icinga 2 v2.6 and Icinga Web 2 v2.4 released

Icinga 2 v2.6

This time we’re focussing on stability and bugfixes instead of adding a ton of new features. This is not to say that there aren’t any new features at all. One notable feature is the bundled NSClient++ 0.5.0 package on Windows which itself improves stability and also offers a nice REST API for querying metrics.
Previous versions had a bug which caused DowntimeStart notifications to be sent as soon as a downtime was created – rather than when the downtime had actually started. In addition to that those notifications were also re-sent each time Icinga was restarted. In an HA setup a related bug might cause Icinga to crash in those scenarios. Debugging those issues was a lot of fun that was supported by being able to test fixes in customer environments. We’ve also fixed a crash in the HTTP server when querying the REST API for example using Dashing. There also were issues with syncing comment/downtime objects between nodes and syncing objects that were global zones.
A big change coming with this release and future versions is that we have decided to deprecate and remove the “bottom up” client configuration mode. All details for this decision can be found in this issue. From the user’s view it contains design flaws and lots of unfixed bugs. Considering the fact that the Icinga “stack” with Icinga 2, Icinga Web 2 and Icinga Director prefers to use the “top down” approach with config sync and clients with command endpoints, the “bottom up” approach does not fit into this design either.
We are aware of the fact that many of you have their setups already in production. There is a dedicated chapter inside the documentation dealing with migration tips and tricks. The removal of CLI commands such as “node list” and “node update-config” will not harm the cluster communication between the nodes at all. It just removes the possibility to import and generate configuration from the client itself. We’re planning for a grace period of 2 major releases or one year until the functionality is removed entirely. For now you can still use them including deprecation warnings but are advised to plan your migration to “top down” in 2017.
There are changes in the IDO database schema for MySQL and PostgreSQL. Icinga 2 v2.6 requires Icinga Web 2 v2.4, plan your upgrade to include both.
Updated release packages are available soon. Meanwhile make sure to read the Changelog.
 

Icinga Web 2 v2.4

This release adds the possibility to use the Icinga 2 API as command transport for e.g. rescheduling a check or sending a custom notification. If you are planning to put your Icinga Web 2 application on a different web server, you don’t have to fiddle with SSH tunnels opening a file handle for the external command pipe. In addition to that the Icinga 2 API is designed to send HTTP responses which enables proper error handling. No more fire and then grep the icinga2.log file anymore.
Another cool feature addition is the announce banner. If you are for example planning global maintenance tasks, this is the way to tell your users about it. We’ve also added a new command action toolbar on top of the detail view. That allows for scheduling a recheck even more quickly.
Other notable changes are a new icon in the detail view history to separate between SOFT and HARD states or a new clear button for the search field. We’ve also moved the status counts to the bottom of the screen. There also is a new package for SELinux installing proper policies for your secured server.
Updated release packages are available soon. Meanwhile make sure to read the Changelog.
 

Icinga 2 bug fix release 2.3.3

We have just released version 2.3.3. This release fixes a number of bugs and introduces a select few minor features and documentation changes:

  • Feature 8685: Show state/type filter names in notice/debug log
  • Feature 8686: Update documentation for “apply for” rules
  • Feature 8693: New function: parse_performance_data
  • Feature 8740: Add “access objects at runtime” examples to advanced section
  • Feature 8761: Include more details in –version
  • Feature 8816: Add “random” CheckCommand for test and demo purposes
  • Feature 8827: Move release info in INSTALL.md into a separate file
  • Bug 8660: Update syntax highlighting for 2.3 features
  • Bug 8677: Re-order the object types in alphabetical order
  • Bug 8724: Missing config validator for command arguments ‘set_if’
  • Bug 8734: startup.log broken when the DB schema needs an update
  • Bug 8736: Don’t update custom vars for each status update
  • Bug 8748: Don’t ignore extraneous arguments for functions
  • Bug 8749: Build warnings with CMake 3.1.3
  • Bug 8750: Flex version check does not reject unsupported versions
  • Bug 8753: Fix a typo in the documentation of ICINGA2_WITH_MYSQL and ICINGA2_WITH_PGSQL
  • Bug 8755: Fix VIM syntax highlighting for comments
  • Bug 8757: Add missing keywords in the syntax highlighting files
  • Bug 8762: Plugin “check_http” is missing in Windows environments
  • Bug 8763: Typo in doc library-reference
  • Bug 8764: Revamp migration documentation
  • Bug 8765: Explain processing logic/order of apply rules with for loops
  • Bug 8766: Remove prompt to create a TicketSalt from the wizard
  • Bug 8767: Typo and invalid example in the runtime macro documentation
  • Bug 8769: Improve error message for invalid field access
  • Bug 8770: object Notification + apply Service fails with error “…refers to service which doesn’t exist”
  • Bug 8771: Correct HA documentation
  • Bug 8829: Figure out why command validators are not triggered
  • Bug 8834: Return doesn’t work inside loops
  • Bug 8844: Segmentation fault when executing “icinga2 pki new-cert”
  • Bug 8862: wrong ‘dns_lookup’ custom attribute default in command-plugins.conf
  • Bug 8866: Fix incorrect perfdata templates in the documentation
  • Bug 8869: Array in command arguments doesn’t work

You can look up the bug ID in our issue tracker at dev.icinga.com. Updated packages should be available shortly.