All Apps and Add-ons
Highlighted

Splunk DB Connect 2: After moving from standalone search heads to a search head cluster, getting errors "BadStatusLine" and "Connection Refused"

Path Finder

We are having issues since we moved from Standalone Search Heads to Clustered Search Heads. Often when we run searches, we get one of the following errors:

BadStatusLine
Connection refused

This runs fine on a standalone machine with the same libraries that we have previously used before moving to the search head cluster. I deployed the app per the documentation (via the Search Head Cluster) and I am positive passwords and such are fine.

Anyone run into this problem and found a fix?

Splunk: 6.4.1
DbConnect 2.2.0

Highlighted

Re: Splunk DB Connect 2: After moving from standalone search heads to a search head cluster, getting errors "BadStatusLine" and "Connection Refused"

Path Finder

This seems to be resolved with the latest version of Splunk and DBConnect

Highlighted

Re: Splunk DB Connect 2: After moving from standalone search heads to a search head cluster, getting errors "BadStatusLine" and "Connection Refused"

Path Finder

Thanks for reporting back on this!
I was having the same issue.

0 Karma