We 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 errors with Icinga 2.
For NetEye 4.25 we updated the following packages:
httpd-neteye-config, httpd-neteye-config-autosetup to version 1.12.1-1
nginx-neteye-config, nginx-neteye-config-autosetup to version 1.7.1-1
icingaweb2-module-director, icingaweb2-module-director-autosetup to version 1.9.1_neteye1.30.1-1
Davide Sbetti
Hi! I'm Davide and I'm a Software Developer with the R&D Team in the "IT System & Service Management Solutions" group here at Würth IT Italy. IT has been a passion for me ever since I was a child, and so the direction of my studies was...never in any doubt! Lately, my interests have focused in particular on data science techniques and the training of machine learning models.
Author
Davide Sbetti
Hi! I'm Davide and I'm a Software Developer with the R&D Team in the "IT System & Service Management Solutions" group here at Würth IT Italy. IT has been a passion for me ever since I was a child, and so the direction of my studies was...never in any doubt! Lately, my interests have focused in particular on data science techniques and the training of machine learning models.
Important: Keycloak security update Type/Severity NetEye Product Security has rated this update as having a CRITICAL security impact. Topic An update for the keycloak packages is now available for NetEye 4. Security Fix for NetEye 4.50: 26.8.2_neteye1.47.5 Security Fixes CVE-2026-114938 A memory Read More
Alyvix Server-side Error We fixed an issue in Alyvix Service caused by a critical typo on the server side. Updating will prevent future communication problems between Alyvix Service and NetEye. List of updated packages To solve the issue mentioned above, Read More
Disclaimer: The security issues below do not yet have publicly disclosed CVE identifiers, so details regarding their severity, impact, and potential attack vectors are not fully available at this time. This post will be updated as soon as additional information Read More
Bug fix: Elasticsearch nodes can crash On Elasticsearch 9.5.6, Elasticsearch nodes could crash at random times. The cause was a kernel setting that was too low: vm.max_map_count. Elasticsearch memory-maps many files. When the number of memory maps reached the limit, Read More
Disclaimer: The CVEs referenced below have not yet been publicly disclosed, so details regarding their severity, impact, and potential attack vectors are not available at this time. This post will be updated as soon as additional information becomes publicly available. Read More