Wazuh did not load properly. Check the server output for more information.

[Jaime-Moranchel]

Hi, so I just logged in this morning and I found a white page with the title message marked in red. I checked the logs and It just appeared this:

2024/05/13 01:01:13 wazuh-db: WARNING: After vacuum, the database '257' has become just as fragmented or worse
2024/05/13 07:18:26 wazuh-maild: ERROR: date or location not NULL
2024/05/13 07:43:14 wazuh-db: WARNING: After vacuum, the database '232' has become just as fragmented or worse

So I checked the db directory and I think that there's a corrupted file: -????????? ? ? ? ? ? 372.db-journal But if I do an ls -lh | grep '?', it gives me other corrupted file:

root@wazuh-mgr:/var/ossec/queue/db# ls -lh | grep '?'
ls: cannot access '219.db-journal': No such file or directory
-????????? ? ?     ?        ?            ? 219.db-journal

[Jaime-Moranchel]

I checked the wazuh control and it output me this:

root@wazuh-mgr:/# /var/ossec/bin/wazuh-control status
wazuh-clusterd not running...
wazuh-modulesd is running...
wazuh-monitord is running...
wazuh-logcollector is running...
wazuh-remoted is running...
wazuh-syscheckd is running...
wazuh-analysisd is running...
wazuh-maild is running...
wazuh-execd is running...
wazuh-db is running...
wazuh-authd is running...
wazuh-agentlessd not running...
wazuh-integratord not running...
wazuh-dbd not running...
wazuh-csyslogd not running...
wazuh-apid is running...
root@wazuh-mgr:/#

It could be that the problem is related to the wazuh-dbd? I have it installed in a docker in single-node

[Jaime-Moranchel]

Nvm, I just had to renew the certificates in wazuh_indexer_ssl_certs