Hi community,
I am trying to connect to the DB connect app and i am constantly redirected to
http://$HOST/en-US/app/splunk_app_db_connect/ftr
What is the FTR and how can I get rid of this error or force a redirection to a DB app that will work.
I tried deleting the app folder in the ($SPLUNK_HOME/etc/apps) directory and reinstalling but still getting the same error. Any assistance here will be greatly appreciated.
Hi guys,
I had the same issue with Splunk 9.3.0 and DB Connect 3.8.x. To solve this just has to clear the cashe of the browser.
Regards,
Hi @Strangertinz ,
I tried the same steps done by you, going back and forth versions and had the same issues as mentioned. I think it's a bug in the splunk db connect app.
Thanks,
Pravin
Hi @_pravin
you can correct the issue by going to latest version of db_connect assuming you are running 9.2.x splunk.
I am still dealing with the issue of the latest version not seeing data send from my db_connect. Has this ever happened to you and how did you resolve it? I cant find any error log to point to the main issue
Thanks @isoutamo , that's pretty much what I am looking.
I don't know if that a version issue/bug but only difference I can find between the working install and non working install is the linux kernel that I am use.
kernel version | DB connect version - Not Working | DB connect version - working |
3.10.0 | 3.17.0 / 3.18.0 | 3.16.0 |
5.14.0 | - | 3.17.0 / 3.18.0 /3.16.0 |
Sometimes, I also have the issue where the app gets launched but doesn't the configuration page remains empty or doesn't move forward past a point.
Is this a common issue with Splunk DB Connect as well ?
Regards,
Pravin
I am using Splunk 9.2.2
Sorry that I forgot to mention the version of Splunk in the earlier version.
I still have the same issue. I tried with version 3.17.0 / 3.18.0 had the same issue. I am using Splunk 9.2.2 and DB connect 3.16.0 worked fine, is this a version issue ?
Disregard, issue resolved
It was just a versioning issue. Had to install the latest db connect app and that solved my issue.
However I am facing the issue again as I tried to go back to an older version with a splunk db connect and facing the same issue while on splunk 9.3.1