You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
If the Wazuh cluster is enabled, after saving local_rules.xml and using the button to restart the cluster the Wazuh managers fail to restart.
Steps to reproduce
Enable the Wazuh cluster configuration.
Edit any rule file (such as local_rules.xml) using the Wazuh Kibana plugin.
Save and click restart the manager using the wui.
Check the API logs to verify that no petition to restart the manager was made (although the wui shows no error message).
Screenshots
Additional context
If Wazuh cluster is enabled the Wazuh Kibana plugin fails to restart the manager when asked, for example, after editing local_rules.xml. From the API logs /var/ossec/logs/api.log it can be seen that there is not an actual petition to restart the manager:
Description
If the Wazuh cluster is enabled, after saving
local_rules.xml
and using the button to restart the cluster the Wazuh managers fail to restart.Steps to reproduce
local_rules.xml
) using the Wazuh Kibana plugin.Screenshots
![image](https://user-images.githubusercontent.com/61882981/99665925-91720200-2a6a-11eb-8c70-36489b747466.png)
Additional context
If Wazuh cluster is enabled the Wazuh Kibana plugin fails to restart the manager when asked, for example, after editing
local_rules.xml
. From the API logs/var/ossec/logs/api.log
it can be seen that there is not an actual petition to restart the manager:When the Wazuh cluster is disabled the petition to restart the manager is actually made as can be seen in this logs:
The text was updated successfully, but these errors were encountered: