Hello,
UPDATE to this case
Im noticing that the services fail due to consumed CPU time, and as far as I noticed with HTOP, CPUS are working at 100% (Not all of them)
× wazuh-indexer.service - Wazuh-indexer
Loaded: loaded (/lib/systemd/system/wazuh-indexer.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/wazuh-indexer.service.d
└─wazuh-indexer.conf
Active: failed (Result: signal) since Wed 2024-09-11 16:40:54 UTC; 16h ago
Docs:
https://documentation.wazuh.com Process: 4331 ExecStart=/usr/share/wazuh-indexer/bin/systemd-entrypoint -p ${PID_DIR}/wazuh-indexer.pid --quiet (code=killed, signal=ABRT)
Main PID: 4331 (code=killed, signal=ABRT)
CPU: 25min 57.121s
Sep 11 16:40:45 wazuh-pb systemd-entrypoint[4331]: dependencies [0x00007f4e43110c10,0x00007f4e43110c48] = 56
Sep 11 16:40:45 wazuh-pb systemd-entrypoint[4331]: handler table [0x00007f4e43110c48,0x00007f4e43110c60] = 24
Sep 11 16:40:45 wazuh-pb systemd-entrypoint[4331]: nul chk table [0x00007f4e43110c60,0x00007f4e43110cb8] = 88
Sep 11 16:40:46 wazuh-pb systemd-entrypoint[4331]: #
Sep 11 16:40:46 wazuh-pb systemd-entrypoint[4331]: # If you would like to submit a bug report, please visit:
Sep 11 16:40:46 wazuh-pb systemd-entrypoint[4331]: #
https://github.com/adoptium/adoptium-support/issuesSep 11 16:40:46 wazuh-pb systemd-entrypoint[4331]: #
Sep 11 16:40:54 wazuh-pb systemd[1]: wazuh-indexer.service: Main process exited, code=killed, status=6/ABRT
Sep 11 16:40:54 wazuh-pb systemd[1]: wazuh-indexer.service: Failed with result 'signal'.
Sep 11 16:40:54 wazuh-pb systemd[1]: wazuh-indexer.service: Consumed 25min 57.121s CPU time.
Any idea why this problem is occurring?
This has never happened to me on versions before 4.8