Zafer Balkan

Hi @ShreyasZare, That's an amazing solution. I admire the way you solved the issue. The plugin works as expected with the changes. Anything regarding the code itself? Any review comments...

At this point, I should note that TLS implementation is not fully complete as it would also require allowing certificate configuration out of OS certificate store and providing mutual TLS...

Hi all. It's the PR author here. First of all, the https://github.com/wazuh/wazuh-agent/issues/179 and https://github.com/wazuh/wazuh-agent/pull/180 are in the https://github.com/wazuh/wazuh-agent repository, which is for Wazuh. 5.x. Wazuh 5.x roadmap is not publicly...

It looks like the patch worked good on test cases but it is not actually solving the problem.

Maybe something like this would help: ```cpp rocksdb::DB* db; rocksdb::Options options; options.create_if_missing = true; rocksdb::Status status = rocksdb::DB::Open(options, EVENTS_QUEUE_PATH, &db); if (!status.ok()) { logError(WM_VULNSCAN_LOGTAG, "Failed to open RocksDB database: %s....

Ho @sebasfalcone, Thanks. I hope everything is good on Wazuh team. I wish I have used different keywords while searching. This is duplicate in this case. I already tried many...

I would like to point out that this fix is needed ASAP as it is the 4.8.x that broke the functionality. So making the users wait more until a recent...

FYI, I managed to solve my issue: 1. Stopped the Wazuh manager on all nodes 2. Removed the queue folder (`/var/ossec/queue/vd/event`) 3. Start the Wazuh manager on all nodes Still...

Dear @sebasfalcone, A side not is that Wazuh's behavior is not consistent for default paths. Sometimes [it silently breaks down and runs in a broken state](https://github.com/wazuh/wazuh/pull/22515). That's why I hesitated...

Hi, Thank you for the link. It is a good workaround to a really needed feature. As you said, the current ones are not suppressed. It basically drops new ones....