Wazuh agent's error

449 views
Skip to first unread message

istecenter staj

unread,
Aug 25, 2022, 2:07:24 PM8/25/22
to Wazuh mailing list
Hi,
We use Wazuh for our project. When we look ossec.log we see errors like: "ERROR(6716): Could not open handle for 'c:\users\e\ntuser.dat.log1'. Error code: 32"
Could you explain what does this mean, why is this appear and how can we solve this?

Carlos Dams

unread,
Aug 25, 2022, 4:00:44 PM8/25/22
to Wazuh mailing list
Hi istecenter,

The "Error code: 32" indicates that Wazuh process cannot access the file because it is being used by another process. Source: https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-
Most likely it appears because you are using File Integrity Monitoring and that file belongs to a path you want to monitor, let me know if this is the case.

In case my assumption is correct, you can eliminate that error from the log by ignoring that file, you can test by adding <ignore>C:\users\e\ntuser.*</ignore> in your Windows config file (open C:\Program Files (x86)\ossec-agent\win32ui.exe and then click on View > View Config) under <syscheck>
I recommend you to check the following article that will help you understand FIM: https://documentation.wazuh.com/current/learning-wazuh/detect-fs-changes.html

I hope you find this information useful, please let me know if this address the issue
Reply all
Reply to author
Forward
0 new messages