Fixing process_list.erb performance #94
Merged
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
|
Hello team, We found the root of the error. The wazuh-manager service was not restarted by its provider (redhat) in CentOS 7. By changing the provider to systemd we have made the service restart and have a correct operation, similar to Debian. Regards, Alfonso Ruiz-Bravo |
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.
Hello team,
This PR solves issue #91
When we execute a manifest to install a Wazuh manager the following list of processes is loaded:
https://github.com/wazuh/wazuh-puppet/blob/master/templates/process_list.erb
On the server.pp
https://github.com/wazuh/wazuh-puppet/blob/master/manifests/server.pp#L117
We can see how the template is added according to the enabled daemons, in this case, authd and integratord.
But if we check ossec-control status:
And the corresponding processes do not start (In the tests done on Debian it did work).
If we perform a restart for example by means of the command
/var/ossec/bin/ossec.control restart, the demons do start after launching the manifest, solving the problem.And the agents will be able to register without any problems.
Regards,
Alfonso Ruiz-Bravo