Hi
I have a problem with wazuh-manager. When the vulnerability-detector module remains enabled, a few seconds after starting wazuh-manager, the modulesd process is killed. Ossec-control status returns as follows:
/var/ossec/bin/ossec-control status wazuh-clusterd not running... wazuh-modulesd: Process 2432672 not used by Wazuh, removing... wazuh-modulesd not running... ossec-monitord is running... ossec-logcollector is running... ossec-remoted is running... ossec-syscheckd is running... ossec-analysisd is running... ossec-maild not running... ossec-execd is running... wazuh-db is running... ossec-authd is running... ossec-agentlessd not running... ossec-integratord not running... ossec-dbd not running... ossec-csyslogd not running...
The wazuh-manager itself is one instance, it is not in a cluster. There are about 1600 agents connected to it. wazuha version 3.13.3. What can this error be caused by? When the vulnerability detector is disabled, everything works fine. Unfortunately, I do not see any errors in the ossec.log. In api.log:
WazuhAPI 2022-05-30 09:18:19 foo: [::ffff:127.0.0.1] GET /agents/?offset=0&limit=1&q=id!%3D000 - 200 - error: '1017'. WazuhAPI 2022-05-30 09:18:19 foo: [::ffff:127.0.0.1] GET /cluster/status? - 200 - error: '1017'. WazuhAPI 2022-05-30 09:18:34 foo: [::ffff:127.0.0.1] GET /manager/info? - 200 - error: '1017'. WazuhAPI 2022-05-30 09:18:36 foo: [::ffff:127.0.0.1] GET /manager/info? - 200 - error: '1017'. WazuhAPI 2022-05-30 09:18:37 foo: [::ffff:127.0.0.1] GET /summary/agents? - 200 - error: '1017'
