Bug Fixes for NetEye 4.27
We fixed a bug when generating resource reports that did not correctly account for customer permissions For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug when generating resource reports that did not correctly account for customer permissions For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug that was doubling the menu entries for Host Problems and Service Problems on customproblemview module when a host or service filter was applied on the user role. For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug that did not allow SLM resource reports to be generated correctly for sending via email. We have updated Icinga Web 2 with the latest bug fix release that brings security fixes. For NetEye 4.27 we updated the following packages:
Read MoreTo identify a NetEye system globally, a unique NUUID (NetEye Universal Unique IDentifier) will be assigned to each NetEye Node. Red Hat Subscriptions are now bound to the NUUID.The feature has been originally released in NetEye 4.27 and is now backported for NetEye versions 4.26, 4.25, and 4.24. For more information on the registration of…
Read MoreWe fixed the default configuration paths used to send SMS messages. For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug that did not allow the RHEL version to be set correctly when the automatic subscription was disabled. For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug where an older version of nginx was installed on the RHEL8 machines. Now nginx will be updated to 1.20.1. We also introduced a logrotate configuration for the neteye nginx logs. For NetEye 4.26 and 4.25 we updated the following packages:
Read MoreWe fixed a bug in El Proxy, for which the verification doesn’t verify the integrity of a log indexed right after one or more missing logs. For NetEye 4.26 we updated the following packages: elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup to version 0.20.4-1
Read MoreWe fixed a bug in El Proxy, for which the verification doesn’t verify the integrity of a log indexed right after one or more missing logs. For NetEye 4.25 we updated the following packages: elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup to version 0.20.4-1
Read MoreWe fixed a bug that was freezing the host page in the director module. Fixed errors that were shown in the director module when clicking on a host template from the preview tab. Fixed the host’s services page of the director module that did not allow more than 100 services to be displayed. For NetEye…
Read MoreWe fixed a bug in the PHP configuration where it would not be read by the services started by systemd. For NetEye 4.24 – 4.26 we updated the following packages: php-neteye-config to version 1.2.1-1
Read MoreWe fixed a bug in El Proxy, for which the automatic verification breaks when the retention of Elasticsearch is applied. The bug fix introduced the concept of blockchain state history and this, if the retention of Elasticsearch already deleted some logs, will throw a warning during the first verification after the update. For NetEye 4.25…
Read MoreWe fixed a bug in El Proxy, for which the automatic verification breaks when the retention of Elasticsearch is applied. The bug fix introduced the concept of blockchain state history and this, if the retention of Elasticsearch already deleted some logs, will throw a warning during the first verification after the update. For NetEye 4.26…
Read MoreSynopsis Important: Multiple Security updates for NetEye 4 Type/Severity Security Advisory: Critical Topic Wuerth Phoenix has released some Critical Patches (CPs) for NetEye 4. These CPs resolve multiple vulnerabilities related to SQL injections, Cross Site Scripting and an unauthenticated remote command execution (RCE) exploit. Description GLPI was affected by: [Critical] RCE using a third-party library script…
Read MoreWe fixed a bug, where on clusters some services could have been started, by some system packages configuration, before the corresponding drbd were mounted. Moreover, we fixed a bug in the Icingaweb2 module Director, which was causing Director deployments to remain blocked in case the automatic deployments done by the Director Jobs were encountering connection…
Read More