-
Notifications
You must be signed in to change notification settings - Fork 133
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
ossec.conf <email_to> is not correctly populated. #138
Comments
Hello @pavlinpetkov , Thanks for reporting this. We will fix it as soon as possible and will let you know when the patch is merged. Please, stay tuned to this ticket. Cheers |
@manuasir , here's my patch if it helps. I was not able to submit a pull request.
|
Hope you're doing well! We have added the corresponding changes and ran some tests to detect the correct functionality. Good News! all the tests got passed successfully. Applied Changes and Required StepsIf we look over /var/ossec/etc/ossec.conf, our example looks like:
Note that we have to assign the value wazuh-puppet/manifests/params_manager.pp Line 15 in bd5e793
Note that this list of emails was generated by filling up the variable $ossec_emailto wazuh-puppet/manifests/params_manager.pp Line 16 in 236dea5
Also by adding the changes you proposed in the template file wazuh-puppet/templates/wazuh_manager.conf.erb Lines 6 to 10 in 236dea5
You can also specify the value for the variable wazuh-puppet/manifests/params_manager.pp Line 19 in bd5e793
Faced Issue, How to resolve & Success TestingMaybe your network only support IPv4 and not IPv6, so in case of not specifying the value of the variable
Error Message
Error Complete Log
Once I changed Success Log:
Screenshot of a received notification:Kind regards, Rshad |
$ossec_emailto parameter of class wazuh::manager requires a list. However the values of the list are not correctly populated by the wazuh_manager.conf.erb template.
Instead of creating an <email_to> entry with each element of the list it creates one <email_to> entry with the full list.
The text was updated successfully, but these errors were encountered: