Bug Fixes for NetEye 4.37
We fixed a bug in nginx that was causing NetEye upgrades from version 4.36 to version 4.37 to fail with an error. We updated the following packages:
Read MoreWe fixed a bug in nginx that was causing NetEye upgrades from version 4.36 to version 4.37 to fail with an error. We updated the following packages:
Read MoreCore Neteye install, update, upgrade procedures individual service logs weren’t saved in the correct format We resolved a small issue where logs from parallel install or configurator playbooks were wrongly manipulated resulting in a different format from what they were supposed to be saved. SIEM – Log Management Elastic Stack missing systemd configuration files We…
Read MoreWe fixed a procmail misconfiguration that was occurring after the upgrade. We updated the following packages:
Read MoreWe resolved an issue in the neteye update and neteye upgrade commands where the process would halt if the Elasticsearch cluster took longer than 30 seconds to respond to API requests. We updated the following packages:
Read MoreWe resolved a bug in the nginx configuration for our clickhouse integration. This fix guarantees that queries will no longer be directed to the voting-only node in cluster environments, preventing potential errors. We updated the following packages:
Read MoreWe fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade. This enhancement guarantees proper pcs resource management throughout this phase. We updated the following packages:
Read MoreWe fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade, to ensure a correct handling of the resources during this phase. We updated the following packages:
Read MoreA bug in the NetEye Alyvix integration has been resolved. This bug was associated with certain secure attributes that were absent from the cookie responsible for storing the Alyvix JWT token. We updated the following packages:
Read MoreWe fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read MoreWe fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read MoreWe fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read MoreWe fixed a bug that caused the tenant drop down, in the NetEye Alyvix integration, to not display the full list of tenants in case of users who are not administrator of NetEye but have Full Module Access on the Alyvix module. We updated the following packages:
Read MoreWe fixed a bug that caused the tenant drop down, in the NetEye Alyvix integration, to not display the full list of tenants in case of users who are not administrator of NetEye but have Full Module Access on the Alyvix module. We updated the following packages:
Read MoreWe fixed a bug that caused the neteye install command to not wait for resources to restart after the procedure completed. We updated the following packages:
Read MoreWe released an update for GLPI that fixes several vulnerabilities. We updated the following packages:
Read More