Closed AlexRuiz7 closed 6 months ago
We tried to reproduce the issue in 4.8.0 - beta5 AIO in the following environments:
We have not been able to replicate the error, on any of the operating systems discussed, with an AIO installation using both local vagrant and the qa test environment in jenkins, everything worked correctly. In the main issue we were using an aws environment, stopping it and reactivating it the next day, we changed the issue to on hold until tomorrow to test that case.
In all the cases mentioned above, everything has worked as it should, the error has not been reproduced.
LGTM
LGTM
Description
It has been reported that the
wazuh-indexer
fails to start as the whole/var/log/wazuh-indexer/
folder disappears due to unknown reasons.We have been trying to replicate the problem without success. Using a Vagrant AIO deployment, the log folder exists, is persistent between restarts and the service starts as expected.
We have tested this behavior in RHEL7 and Ubuntu 22.04 operating systems.
Check https://github.com/wazuh/wazuh-indexer/issues/201
We would like to be sure that this issue is not reproducible and has been a particular case. We would like to create a new environment with a fresh v4.8.0-beta5 installation and check if this error happens again.
Configuration and considerations
Fresh and untouched Wazuh v4.8.0-beta5 installation.