Fix failed to disable wazuh-manager.service #5761
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rauldpm
requested changes
Sep 23, 2024
|
This PR should go to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
After conducting several tests on the issue: #5742, it was concluded that when uninstalling with the
--purgeoption, it is not necessary to runsystemctl disable wazuh-managerafterward. This was causing the error message mentioned in the issue, as after the uninstallation, it would attempt to disable the service, and since it couldn't find it, it displayed that message.Testing performed
The job flow was executed again with the applied changes, and the error was not encountered again.
Log:
jobflow.log
Packages used: 4.9.0