-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent Logcollector from producing errors on blank lines at audit log files #3633
Comments
Update - 24/11/2022 Perform proposed checks for Wazuh manager |
Review data
Testing environment
Tested packages
Status
ConclusionAt this point, it seems to work as expected |
Testing results 🟢UnfixedInstall unfixed package
UpgradeUpgrade fixed package 🟢
Fresh installFresh install firmed package 🟢
|
I have launched the integration tests for logcollector and the changes made cause the following test failure 🔴 :
I will investigate if that change has caused a new expected behavior and update that test. If not, the bug will be reported to be fixed in this development. |
The test error is caused due to the log level change of
The following PR #3641 has been opened to update this new log level. |
Closing conclusion 👍🏼Everything seems to be working properly. |
Description
This PR aims to fix a double issue in Logcollector, whose audit log reader produces errors in these cases:
An empty line was found.
A log with a valid header but an empty message was found.
Proposed checks
Steps to reproduce
Configuration and considerations
The text was updated successfully, but these errors were encountered: