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
wazuh-apid blindly killing pid (found in wazuh-apid.pid) after a sudden reboot #22608
wazuh-apid blindly killing pid (found in wazuh-apid.pid) after a sudden reboot #22608
Comments
UpdateModified the method in charge of cleaning up methods to validate that the process belonged to the Wazuh daemon before killing it. In case the process was from other service, it just removes the file from the folder to avoid it happening again. |
UpdateAdded the |
UpdateMade some modifications in the wazuh-qa, wazuh-packages and wazuh-documentation repositories to update the name of the API script and re-launched the failed checks to generate the packages with the changes. |
UpdateResolved conflicts in the linux upgrade check files. |
UpdateGenerated packages and ran the upgrade tests for each one of the linux distros required. |
UpdateApplied suggested changes to some files in the Jenkins repository. |
wazuh-manager v4.7.2 (rpm) Amazon Linux 2
I'm having an issue with wazuh v4.7.2, after a sudden reboot, when wazuh-manager restarts it's killing processes not owned by wazuh blindly
In this case it's a process owned by systemd (da-controller-procmgr.service which has pid 8634; I verified this from a different log file), which makes this all the more confusing.
it looks like https://github.com/wazuh/wazuh/blob/master/api/scripts/wazuh-apid.py#L355 is to blame as it's just reading the pids from previously started wazuh processes and blindly trying to kill them.
Any recommendations on how to work around this?
My suggestion would be for https://github.com/wazuh/wazuh/blob/master/framework/wazuh/core/utils.py#L43 (
clean_pid_files
) to try a bit harder to make sure the daemon name matches the process name before attempting to kill it.The text was updated successfully, but these errors were encountered: