NATS: Fix multi-tenancy configuration corruption in cluster environments
When executing commands such as neteye install --restrict-services-to nats-server, neteye tenant config apply, or neteye satellite config create from a cluster node while nats-server was active on a different node, the shared /neteye/shared/nats-server/conf/multi-tenancy.conf configuration file could get corrupted. Unreplaced template placeholders (such as @@ACCOUNTS@@, @@TORNADO_IMPORTS@@, and @@TELEGRAF_IMPORTS@@) were written to the file, causing a parse error and preventing nats-server from starting.
The configuration generation has been fixed to ensure placeholders are properly expanded and the configuration remains valid across all cluster nodes.
List of updated packages
To solve the issue mentioned above, the following package has been updated:
nats-server to version 2.10.21_neteye1.36.1-1
Luca Tecchio
Software Developer - IT System & Service Management Solutions at Würth IT Italy
Author
Luca Tecchio
Software Developer - IT System & Service Management Solutions at Würth IT Italy
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
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
Important: ClickHouse security update Type/Severity NetEye Product Security has rated this update as having a CRITICAL security impact. Topic An update for the clickhouse-server package is now available for NetEye 4. Security Fix for NetEye 4.50: 26.3.62.3-1 Security Fixes CVE-2026-116366CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H This vulnerability Read More
Disclaimer: Three of the security issues referenced below do not yet have public CVE identifiers, so they are referenced by their GHSA ID. This post will be updated as soon as CVEs become available. Important: Icinga Web 2 security update Read More
Disclaimer: Some of the CVEs referenced below have not yet been publicly disclosed, 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
