Problem with Wazuh API manager

[Facu Basgall]

Every now and then I get this error in Wazuh, I can't find a log to refer to and the wazuh-manager service is active

I usually fix it by restarting the wazuh-manager service.

Is there something I can check to avoid this kind of problems? or something I should monitor and run with a script so it auto fixes itself without restarting the service?

I'm using version 4.14.1 with an all-in-one architecture.

[Carlos Ezequiel Bordon]

Hi, can you check the manager logs to verify what's generating the error?

cat /var/ossec/logs/ossec.log | grep -i -E "error|warn|cri"

[Facu Basgall]

Attached is a file according to the command sent

[Carlos Ezequiel Bordon]

Can you tell us what type of Wazuh deployment you have? (All-in-One or Distributed)

Also, can you tell us what resources the Wazuh manager host has?:

lsof -n | wc -l 

free -h 

top

[Facu Basgall]

It is an AIO architecture

Attachment command results