Miguel Angel Cazajous

# Update > [!IMPORTANT] > As I initially thought this is not an issue with Wazuh-DB itself, there's more under the hood to analyze and the errors in wazuh-db are...

## Update Comparing 4.8.1-rc2 vs 4.9.0-b2 I see some similar errors previously mentioned above In 4.8.1-rc2, the log gap is present and also the log message where the agent 000...

Hi @VenkataPatrana, Did you configure the indexer block in your `ossec.conf` configuration file? if the indexer connector cannot communicate with the indexer, those messages are expected. Please take a look...

Take into account that the IP as well as the certificates may differ in your environment, did you check that the indexer is indeed connected? Please add `wazuh_modules.debug=2` in your...

> Error: No available server It cannot connect to the server. Try this curl command from the command line to validate your configuration `curl --cacert --cert --key -u -XGET https://:9200/_cluster/health`...

Great! thanks for the information. The reason for this > Not sure what's the issue, some agents can connect and sync with indexer but not all Cluster health is in...

Please try with Curl command in the terminal the same way you did before. I would try something like this ``` curl --cacert --cert --key -X PUT "https://:9200/*/_settings" -H 'Content-Type:...

Glad to know that @VenkataPatrana! Regards!

# DoD # Microsoft Silverlight ```console 2024/08/23 16:27:22 wazuh-modulesd:vulnerability-scanner[120231] packageScanner.hpp:145 at scanPackageTranslation(): DEBUG: Translation for package 'Microsoft Silverlight' in platform 'windows' found in Level 2 cache. ``` ```console 2024/08/23 16:27:22...

# Test passing ## WinSCP  ## Silverlight