<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DB Connect configuration: Unable to save database inputs and slow search query in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170283#M186337</link>
    <description>&lt;P&gt;I assume there is a way to restart jbridge without restarting Splunk (as the UI seems to manage it somehow), but I've never found a way to do it from the command line. There's nothing in the documentation that I could find on the subject or on the "answers" site. Perhaps someone from Splunk Support could weigh in on this...&lt;/P&gt;</description>
    <pubDate>Wed, 06 Aug 2014 01:41:56 GMT</pubDate>
    <dc:creator>pmdba</dc:creator>
    <dc:date>2014-08-06T01:41:56Z</dc:date>
    <item>
      <title>DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170280#M186334</link>
      <description>&lt;P&gt;Trying to get our freshly working DB Connect configured.&lt;/P&gt;

&lt;P&gt;I am finding a problem in that I cannot save some new database inputs; the web GUI comes back with &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Encountered the following error while trying to save: Splunkd daemon is not responding: ('Error connecting to /servicesNS/admin/search/dbx/dbmon: The read operation timed out',)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and the input does not get into app/dbx/local/inputs.conf.&lt;/P&gt;

&lt;P&gt;I'm starting to notice a correlation between how slow the query I'm putting in is and above error occurring: if it's a slow query (say 30-60s because we are working against a large table), then I get the error.&lt;/P&gt;

&lt;P&gt;Has anyone else seen this? Is there some kind of validation of the query that I can turn off so that I can add this input? Am I going to have to add the input into inputs.conf directly?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Aug 2014 21:20:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170280#M186334</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2014-08-04T21:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170281#M186335</link>
      <description>&lt;P&gt;My personal experience is that in order to get all of the parameters I need set correctly I almost always have to edit inputs.conf. The UI is getting better, but there are a couple of things it doesn't do. That said, if the query is timing out in the UI, it will probably still time out after you put it in inputs.conf. &lt;/P&gt;

&lt;P&gt;You might consider whether there is any way to tune the query or the database to reduce the response time. You might also consider if if this is a "tail" type of input and the table has a lot of rows, not selecting historical data into Splunk; in such a case it might only be the initial query that takes so long. Once the historical data is indexed in Splunk performance might improve on its own.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2014 03:56:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170281#M186335</guid>
      <dc:creator>pmdba</dc:creator>
      <dc:date>2014-08-05T03:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170282#M186336</link>
      <description>&lt;P&gt;the query is running fine (I can see it in dbx.log), but I just get the timeouts when I try to save the query (or changes) in the GUI. &lt;/P&gt;

&lt;P&gt;Is there a way to just restart jbridge so it picks up my manually entered changes? restarting splunkd for every change to inputs.conf is expensive....&lt;/P&gt;

&lt;P&gt;Optimization on the query is already done; it's an ugly one, not likely to get quicker.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2014 12:09:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170282#M186336</guid>
      <dc:creator>wegscd</dc:creator>
      <dc:date>2014-08-05T12:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170283#M186337</link>
      <description>&lt;P&gt;I assume there is a way to restart jbridge without restarting Splunk (as the UI seems to manage it somehow), but I've never found a way to do it from the command line. There's nothing in the documentation that I could find on the subject or on the "answers" site. Perhaps someone from Splunk Support could weigh in on this...&lt;/P&gt;</description>
      <pubDate>Wed, 06 Aug 2014 01:41:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170283#M186337</guid>
      <dc:creator>pmdba</dc:creator>
      <dc:date>2014-08-06T01:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170284#M186338</link>
      <description>&lt;P&gt;I run into this constantly, and have found no reliable solution other than editing inputs.conf and restarting splunkd, which as you say, is not much of a solution. When I'm at a point where I simply can't afford the outage, sometimes I will keep banging away at the UI and the query will eventually save, but this issue needs attention for dbx to be taken seriously. &lt;/P&gt;</description>
      <pubDate>Wed, 06 Aug 2014 13:19:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170284#M186338</guid>
      <dc:creator>jonathan_octane</dc:creator>
      <dc:date>2014-08-06T13:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170285#M186339</link>
      <description>&lt;P&gt;FYI - you can reload the jbridge server by updating the JVM Command Line Options under the "Splunk DB Connect Configuration" dialog (&lt;A href="http://your.splunk:8000/en-US/manager/dbx/apps/local/dbx/setup?action=edit"&gt;http://your.splunk:8000/en-US/manager/dbx/apps/local/dbx/setup?action=edit&lt;/A&gt;). I typically just change the heap size between two equivalent sets of units (eg "-Xmx2048m" and "-Xmx2G") and save to restart the java bridge.&lt;/P&gt;

&lt;P&gt;You can also reload the java bridge by hitting the debug/refresh endpoint as follows:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://your.splunk:8000/en-US/debug/refresh?entity=admin/dbx-dblookups&amp;amp;entity=admin/dbx-dboutput"&gt;http://your.splunk:8000/en-US/debug/refresh?entity=admin/dbx-dblookups&amp;amp;entity=admin/dbx-dboutput&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Verify that this worked by looking at the Java Bridge Status UI's uptime info.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Aug 2014 03:50:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170285#M186339</guid>
      <dc:creator>gcoles</dc:creator>
      <dc:date>2014-08-15T03:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170286#M186340</link>
      <description>&lt;P&gt;This may help form the Splunk directory:&lt;/P&gt;

&lt;P&gt;splunk cmd python $splunk_home/etc/apps/dbx/bin/reload.py databases&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2015 22:09:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170286#M186340</guid>
      <dc:creator>brundl3fly</dc:creator>
      <dc:date>2015-01-07T22:09:54Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect configuration: Unable to save database inputs and slow search query</title>
      <link>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170287#M186341</link>
      <description>&lt;P&gt;This made everything much quicker and less prone to timeouts, thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2016 21:35:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/DB-Connect-configuration-Unable-to-save-database-inputs-and-slow/m-p/170287#M186341</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2016-11-15T21:35:12Z</dc:date>
    </item>
  </channel>
</rss>

