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 Kibana sysconfig migration We resolved a bug that occurred during the migration of Kibana to a multi-instance setup. The issue prevented the proper copying of custom configurations from /neteye/shared/kibana/conf/sysconfig/kibana-user-customization. As a result, these customizations were missing from the Kibana instances Read More
Fix monitoring object creation during deployment We fixed a bug that caused a monitoring object to be lost if it was created while a Diretor deployment was in progress. List of updated packages To solve the issues mentioned above, the Read More
Fix for Tornado Webhook collector We have fixed an issue where large incoming requests to the Webhook Collector could cause the system to become unresponsive over time. List of updated packages To solve the aforementioned issues, the following packages have Read More
Fixes for Elastic Stack Improved wait for cluster status during updates / upgrades When restarting the Elasticsearch cluster during the NetEye update / upgrade procedure, is it possible let the restart procedure going even if the cluster has a "yellow" Read More
Fix for Previously, database updates would fail if the GLPI DRBD resource was active on a node other than the primary, due to an inability to locate the necessary database configuration within the DRBD-managed volume. This fix ensures that GLPI Read More