openITCOCKPIT 4.8.7 released

🚀 The release 4.8.7 of openitcockpit is a special release, that fixes some important bugs, that have been reported to us. 🚀

Bugfixes

inconsistency with host and service groups

There were several issues in the handling of containers and the resolution of certain elements, but these have now been resolved.

Initially, there was the “Main” container, which included the sub-containers “A” and “B.” Hosts were located in both “A” and “B.” When creating a host group in “Main,” hosts from both sub-containers “A” and “B” could be selected, which worked correctly.

However, an issue arose when creating a service group in “Main”: it was not possible to select services from hosts in either “A” or “B.” If the service group was created in “A,” only hosts and services from “A” could be selected. This behavior has now been corrected.

Another problem was that elements of a location (Location CT_LOCATION) were not resolved because the location type was not correctly registered. This issue has also been addressed.

Additionally, there was a limitation where only certain container types were resolved. The following three container types were correctly processed:

CT_GLOBAL CT_TENANT CT_NODE Now, all container types, including the CT_LOCATION location type, are properly resolved, and the system is functioning as expected.

The issues affected the following areas:

Host groups Service groups Host escalations Service escalations Imported host groups

With the corrections made, these issues have now been fully resolved, and all elements and groups are being correctly resolved.

Import Module: ManageEngine OpManager - Outdated service identifier issue

Currently, there is an issue where the interface index in OpManager changes, while the name remains the same. This causes the service in openITCOCKPIT not to update automatically, and the status can no longer be queried. To prevent the loss of historical data, the service should not be deleted and recreated. Instead, only the identifier should be updated to resolve the issue.

Add Requires Gearmand to Naemon Systemd Service configuration

It has been observed that when all services are restarted, and this includes the Gearman job server, it can cause Naemon to fail to start. As a result, Naemon stops functioning, and monitoring becomes unavailable. To prevent this, a “Requires” dependency should be set to ensure that Naemon is only restarted after the Gearman job server has been successfully started.

Linux versions with openITCOCKPIT End-of-Life

As announced in our blog post on release 4.8.1, support and the provision of packages for Debian 11 and Ubuntu Focal ends with release 4.8.6.

🛠️ Changelog

For a complete list of new features, fixed bugs and improvements, please see the changelog

How to Update

Please see the official documentation of how to update openITCOCKPIT.

Have fun with this brand new openITCOCKPIT release - Your openITCOCKPIT Team 🚀🔍📊