Error wazuh-db: CRITICAL: At pthread_mutex_lock(): Invalid argument

[Isaac]

Hello Wazuh Team

Working with new rules and adding a CDB list in the ossec.conf file of all the workers, after restarting the wazuh-manager service i got in some workers errors in the wazuh-manager service.

And the "systemctl status wazuh-manager" output is:

wazuh-dbd: CRITICAL: At pthread_mutex_lock(): Invalid argument

I have appliaed the following actions:

- Restart wazuh-manager

- kill the "wazuh-db -t" that appears twice in ps -fea

- stop the wazuh-manager service

After all actions, the problem continue.

wazuh version: 4.10.1

Regards.

Isaac

[Bony V John]

Hi,

Please allow me some time, I'm working on this and will get back to you with an update as soon as possible.

[Bony V John]

Hi,

When the Wazuh Manager service fails to start, the first step is to check the Wazuh Manager ossec.log file, as it usually provides details about the root cause of the issue.

Run the following command on your Wazuh Manager CLI to filter errors or warnings from the log:

cat /var/ossec/logs/ossec.log | grep -iE "error|warn"

Check if there are any error messages and share them with us for further analysis.

Next, check the Wazuh Manager service status:

/var/ossec/bin/wazuh-control status

Also, re-validate your ossec.conf configuration file to ensure the settings were added correctly. You can refer to the Wazuh documentation for more details on configuration syntax.

If you have created a CDB list, make sure it has been added correctly. You can verify this using the Wazuh documentation on CDB list configuration.

To confirm whether the issue is related to the CDB list, temporarily remove the <list> configuration you added inside the <ruleset> tag in your ossec.conf file, and then restart the Wazuh Manager:
systemctl restart wazuh-manager

After restarting, check if the issue is resolved.
If it is, please share the CDB file you created so we can review it.
Also, share your ossec.conf file so we can validate the configuration.

[Isaac]

Hello Bony

I have checked the ossec.conf configuration file and the problem was with a new CDB list. I remove the line and restart wazuh-manager service and it started ok.

Thank you.