17. 11. 2026 Damiano Chini Bug Fixes, NetEye

Bug Fixes for NetEye 4.50

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, the node stopped.

NetEye now sets vm.max_map_count to 1048576, which is the value that the Elasticsearch documentation recommends. The package applies the new value immediately after the update, and the system also applies it at each boot, so a restart is not necessary.

Bug fix: race condition in Logstash configuration during update and upgrade

During neteye update and neteye upgrade, the Logstash step did not wait for nginx, which may cause an error during the procedure. Logstash now has nginx as a dependency, so no race condition can happen.

Updated packages

The following packages have been updated:

  • elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, elastic-stack-configurator, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license, filebeat, filebeat-autosetup, filebeat-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config, logstash-neteye-config-autosetup to version 9.5.6_neteye3.105.6-1

Damiano Chini

Damiano Chini

Author

Damiano Chini

Leave a Reply

Your email address will not be published. Required fields are marked *

Archive