Clone the Wazuh repository

Oct 13, 2025 by miodeya.com 3 views

Understanding the Issue

During the tests at #28281, it was found that in the development branch 4.12.0 the manager fails to gracefully restart and prints the following error messages. This issue requires a thorough Root Cause Analysis (RCA) to propose a fix.

Error Message Analysis

The error message is as follows:

root@ubuntu-focal:/var/ossec# ./bin/wazuh-control restart && tail -f logs/ossec.log 
2025/03/12 03:56:42 wazuh-modulesd[7106] debug_op.c:116 at _log_function(): DEBUG: Logging module auto-initialized
2025/03/12 03:56:42 wazuh-modulesd[7106] main.c:80 at main(): DEBUG: Wazuh home directory: /var/ossec
2025/03/12 03:56:42 wazuh-modulesd[7106] wmodules-osquery-monitor.c:78 at wm_osquery_monitor_read(): DEBUG: Logpath read: /var/log/osquery/osqueryd.results.log
2025/03/12 03:56:42 wazuh-modulesd[7106] wmodules-osquery-monitor.c:84 at wm_osquery_monitor_read(): DEBUG: configPath read: /etc/osquery/osquery.conf
2025/03/12 03:56:42 wazuh-modulesd:router[7106] wm_router.c:98 at wm_router_read(): INFO: Loaded router module.
2025/03/12 03:56:42 wazuh-modulesd:content_manager[7106] wm_content_manager.c:87 at wm_content_manager_read(): INFO: Loaded content_manager module.
wazuh-clusterd not running...
Killing wazuh-modulesd...
./bin/wazuh-control: 491: kill: No such process

Reproducing the Issue

To reproduce the issue, follow these steps:

Clone the Wazuh repository: Clone the Wazuh repository from the development branch 4.12.0.
Build and install Wazuh: Build and install Wazuh on a test environment.
Restart the manager: Restart the manager using the wazuh-control restart command.
Verify the error message: Verify that the error message is printed in the ossec.log file.

Root Cause Analysis (RCA)

To perform the RCA, follow these steps:

Analyze the error message: Analyze the error message to identify the root cause of the issue.
Check the process list: Check the process list to verify that the wazuh-modulesd process is running.
Verify the configuration: Verify the configuration files to ensure that they are correct.
Check the logs: Check the logs to identify any errors or warnings that may be related to the issue.

Fixing the Issue

To fix the issue, follow these steps:

Update the Wazuh repository: Update the Wazuh repository to the latest version.
Rebuild and reinstall Wazuh: Rebuild and reinstall Wazuh on the test environment.
Verify the issue is fixed: Verify that the issue is fixed by restarting the manager and checking the error message.

Conclusion

In conclusion, the error message from Wazuh-control during manager restart is a critical issue that requires a thorough RCA to propose a fix. By following the steps outlined in this article, you can reproduce the issue, perform the RCA, and fix the issue.

Recommendations

To prevent similar issues in the future, we recommend:

Regularly updating the Wazuh repository: Regularly update the Wazuh repository to the latest version.
Verifying the configuration files: Verify the configuration files to ensure that they are correct.
Checking the logs: Check the logs to identify any errors or warnings that may be related to the issue.

Additional Resources

For additional resources, please refer to the Wazuh documentation and the Wazuh community forum.

Wazuh Documentation

Wazuh Documentation

Wazuh Community Forum

Wazuh Community Forum

Wazuh GitHub Repository

Wazuh GitHub Repository
Wazuh-Control Error Message During Manager Restart: Q&A ===========================================================

Frequently Asked Questions (FAQs)

This article provides answers to frequently asked questions related to the Wazuh-control error message during manager restart.

Q: What is the Wazuh-control error message during manager restart?

A: The Wazuh-control error message during manager restart is a critical issue that occurs when the Wazuh manager fails to restart gracefully and prints an error message.

Q: What is the cause of the Wazuh-control error message during manager restart?

A: The cause of the Wazuh-control error message during manager restart is not yet identified, but it is believed to be related to a bug in the Wazuh development branch 4.12.0.

Q: How can I reproduce the Wazuh-control error message during manager restart?

A: To reproduce the Wazuh-control error message during manager restart, follow these steps:

Clone the Wazuh repository from the development branch 4.12.0.
Build and install Wazuh on a test environment.
Restart the manager using the wazuh-control restart command.
Verify that the error message is printed in the ossec.log file.

Q: What are the symptoms of the Wazuh-control error message during manager restart?

A: The symptoms of the Wazuh-control error message during manager restart include:

The manager fails to restart gracefully.
The error message is printed in the ossec.log file.
The wazuh-modulesd process is not running.

Q: How can I fix the Wazuh-control error message during manager restart?

A: To fix the Wazuh-control error message during manager restart, follow these steps:

Update the Wazuh repository to the latest version.
Rebuild and reinstall Wazuh on the test environment.
Verify that the issue is fixed by restarting the manager and checking the error message.

Q: What are the best practices to prevent similar issues in the future?

A: To prevent similar issues in the future, follow these best practices:

Regularly update the Wazuh repository to the latest version.
Verify the configuration files to ensure that they are correct.
Check the logs to identify any errors or warnings that may be related to the issue.

Q: Where can I find additional resources related to the Wazuh-control error message during manager restart?

A: For additional resources, please refer to the Wazuh documentation and the Wazuh community forum.