Closed dracon80 closed 5 months ago
This appears to be an OpenCTI issue, originating from a ping module within the OpenCTI SDK. I haven't seen it before, and I can't find any details about it on my initial search. What are you doing to produce these errors? Nothing, just starting the connector?
Perhaps you could try this setting for elastic/opensearch in OpenCTI: thread_pool.search.queue_size: 5000
Thank you for the quick response. Yes you were spot on, I had not set this environment variable. As soon as I did the connector started without issue. Just waiting for it to populate some data.
That's nice to hear!
If you want to run it manually on existing entities, you can run enrichment manually.
I've attempted to implement the connector but the container keeps erroring and restarting. My Environment is Wazuh 4.8.0 running 3 indexers as a cluster on virtual machines (e.g. not docker containers)
The docker container versions for opencti are;
The ENV for the connector container (with hostnames and passwords changed)
The connector can communicate with both wazuh and opensearch, but I just can't get it to work. A sample of the log file is attached, I'm just not sure if the error is caused by the opensearch instance opencti is using, or the wazuh indexer cluster. wazuh.log