Why is Splunk UBA generating "ECONNREFUSED" error?

[dlyubchenko]

While troubleshooting an error with Splunk UBA that stated the Offline Models have not executed for 72 hours, and that the HR data retrieval time was timed out after 6000 ms, the "Learn More" button referenced the following error message below:

{"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect","address":"34.213.241.61","port":80,"message":"connect ECONNREFUSED 34.213.241.61:80","details":"Error from /uba/help/\nconnect ECONNREFUSED 34.213.241.61:80"}

From what I can tell the 34.213.241.61 address belongs to a Splunk DNS resolver, but I cannot find anywhere in the Splunk UBA configuration where this is referenced or why UBA is reaching out to this resolver. I am also not sure how this is associated to both of the errors I am having, and would like some advice as to where to go next with this as it feels like a red herring.

Thank you!

[dlyubchenko · Accepted solution]

I ended up resolving this myself by doing the following:

sudo su - caspida
/opt/caspida/bin/Caspida stop-all
/opt/caspida/bin/Caspida start-all

I realize this was a work-around but it seemed that I had some stalled services, or resource over-utilization.