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
When starting the wazuh-manager with the EPS limitation block but without the <maximum> tag, multiple warnings come up, flooding the log and proving annoying.
2022/10/18 09:42:09 wazuh-maild: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:09 wazuh-maild: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:09 wazuh-analysisd: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:10 wazuh-remoted: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:10 wazuh-monitord: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:10 wazuh-testrule: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:14 wazuh-analysisd: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:15 wazuh-remoted: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
2022/10/18 09:42:17 wazuh-monitord: WARNING: EPS limit disabled. The maximum value is missing in the configuration block.
It is requested to improve this behavior, so that only a single log message is displayed.
Steps to reproduce
Add the following configuration block to the <global> section of ossec.conf (missing <maximum>)
Description
When starting the
wazuh-manager
with the EPS limitation block but without the<maximum>
tag, multiple warnings come up, flooding the log and proving annoying.It is requested to improve this behavior, so that only a single log message is displayed.
Steps to reproduce
<global>
section ofossec.conf
(missing<maximum>
)wazuh-manager
and check logsThe text was updated successfully, but these errors were encountered: