Bug discovered on NetEye module logmanagement and SIEM
A bug has been discovered on NetEye modules logmanagement and SIEM. If affected, rsyslog directories on system might be created with wrong permissions causing Logstash to be unable to load log lines of some hosts inside Elasticsearch. Users might also receive an error message trying to check signatures for some hosts inside Logmanager Log Check. All NetEye systems with neteye-logmanagement or netey-siem modules installed might be affected .
To check your system run following command:
find /neteye/shared/rsyslog/data/ -not -perm 770 -type d -exec ls -lad {} \; | grep "dr-------T."
If the provided command returns some results your system is affected. Please apply the following workaround to fix it until an official bug-fix is provided:
Run command: crontab –e
Add following line: 30 00 * * * /usr/bin/find /neteye/shared/rsyslog/data/ -not -perm 770 -a -not -perm 750 -type d -exec /usr/bin/chmod 770 {} \; > /dev/null
Save the file
Previous steps must be executed on every NetEye node.
If
you need further information, or experience some problem applying the fix, feel
free to contact our support team using one of the following options:
Fix support for Alyvix Nodes with older versions We solved an issue that could cause Test Cases to be not shown in the Alyvix UI if the Alyvix Nodes supported only API version 3 (i.e. Alyvix Service version <= 2.5). Read More
Fix for Broken Links in the Icinga Web 2 Business Process Module We have resolved an issue that caused broken links within the Business Process module. In certain cases, links pointing to monitoring objects were generated incorrectly, resulting in users Read More
Passive Checks Stuck in Pending During Director Deployments A race condition during Director deployments caused some passive checks to remain in a pending state instead of updating properly. This behavior has now been corrected. With the fix in place, passive Read More
Passive Checks Stuck in Pending During Director Deployments A race condition during Director deployments caused some passive checks to remain in a pending state instead of updating properly. This behavior has now been corrected. With the fix in place, passive Read More
A safer way to run privileged Windows checks with SystemRunner If you’ve been monitoring Windows for a while, you’ve probably seen this pattern: some checks must run as LocalSystem (S-1-5-18), and the “quick fix” is to run the Icinga Agent Read More