Tornado: Allow disabling forwarding of local system logs to Tornado
By default, rsyslog on NetEye nodes forwards all logs it handles to the Tornado event engine. These include the system logs of the NetEye node itself, which can generate a large number of syslog events on Tornado. Until now, there was no way to turn these events off without also stopping logs received from other hosts.
A new setting now separately controls the forwarding of the node’s own logs. Rsyslog reads it from the environment variable TORNADO_RSYSLOG_FORWARD_LOCAL_LOGS, which the Tornado package sets to true by default, so the existing behavior is unchanged. When it is set to false, rsyslog stops forwarding logs that originate on the node. Logs received from other hosts are always forwarded to Tornado.
For instructions on how to change this setting, see the Rsyslog section of the Tornado collectors chapter in the NetEye User Guide.
List of updated packages
To solve the issue mentioned above, the following packages have been updated:
tornado, tornado-neteye-config, tornado-dto, tornado-configurator, tornado-rsyslog-collector-logmanager, tornado-autosetup, tornado-common, all to version 1.45.1-1
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
Social login provider icons are displayed correctly again We fixed an issue on the NetEye login page where icons of social login providers (identity providers configured in Keycloak) were rendered at the wrong size after the update to Keycloak 26.8. Read More