"Error while communicating with Splitd" errors

[aej]

Hi,

We are using this in our application and we have set this up as a containerized sidecar following your documentation here: https://developer.harness.io/docs/feature-management-experimentation/sdks-and-infrastructure/optional-infra/split-daemon-splitd/#containerized-sidecar

Unfortunately we are getting a large number of these error logs: "Error while communicating with Splitd". This only happens on some connection attempts - the Split client is definitely working and we have lots of feature flags evaluating correctly. But the existence of this log (~1000 instances in the last week for us) makes us worried that something is not working at the integration level here.

I'd be curious to know if you have any thoughts

Thanks

[EmilianoSanchez]

Hi @aej ,

Sorry for the delay.

That error suggests that SplitDaemon cannot be reached on some connection attempts (maybe while it's starting up?). Could you share a bit more context around those error logs?
For example, are there other error or debug logs around the same time (e.g. [error] Error establishing socket connection: :enoent)? If possible, could you also provide SplitDeamon logs with similar timestamps to check for any correlation?

Thank you