All Apps and Add-ons

Splunk DBConnect 3.1.1 Build 34 There was an error processing your request. It has been logged (ID XXXXXXXXXXXXXXX).

Explorer

After completing the SQL Query and then setting the properties for an input, I cannot click the finish button without getting the following error:

There was an error processing your request. It has been logged (ID 7af858e1614ada9e).

If I click on it again I get a different ID. Tried going through the logs, did not see anything pointing to why it won't complete the process.

Anyone else get past this?

More info:
Using DBConnect 3.1.1 build 34
Connecting to a Microsoft SQL DB using MS-SQL Server Using MS Generic Driver. Host verified and port verified on connection.
SQL query executes successfully.

1 Solution

Explorer

We were able to get this to work through the backend and entering the same query into the backend db_inputs.conf \etc\apps\splunk_app_db_connect\local\

View solution in original post

Esteemed Legend

I was getting this when i was trying to install the Microsoft SQL Server driver:
https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view...
As described here:
https://docs.splunk.com/Documentation/DBX/latest/DeployDBX/Installdatabasedrivers

When using the v13 and v11 JAR files, I got this error. However, when I used the v8 JAR, I did not get any errors and it showed up correctly on the drivers screen.

0 Karma

Engager

Hey all is this a known error

0 Karma

Engager

Hi everyone, If someone knows, was this bug fixed? If it isnt fixed, ill have to use the work around on my enviroment.

Thanks for the work arround, @bradob .

0 Karma

Motivator

It is not fixed. Does this surprise anyone?

0 Karma

Path Finder

Hello @nick405060

If the problem is about your connections in hosts in splunk db connect you should search if there is the same stanza in other db_connections.conf. can you check if you have twice stanza.

0 Karma

Explorer

We were able to get this to work through the backend and entering the same query into the backend db_inputs.conf \etc\apps\splunk_app_db_connect\local\

View solution in original post

I manually created 
the db_inputs.conf file
but it does not run😓
what should i do?
0 Karma

Path Finder

I had the same problem and managed to bypass it by editing the configuration file.
I still do not know why it does not save the page, but editing the file directly through linux works fine.

0 Karma

Legend

@bradob, if this worked for you, please accept the same as answer to mark this question as answered.

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
0 Karma

Path Finder

I had the same issue with DBX v3.1.3 with MS SQL query setups in the GUI:

ERROR ... Error handling a request:
...
Caused by: java.lang.NullPointerException: null
at com.splunk.dbx.server.util.ResultSetMetaDataUtil.isTableHavingSameNameColumns

I updated the configurations on the back end and they work fine.

0 Karma

Explorer

This should be considered a workaround / bug that should be corrected in DBConnect

0 Karma

Legend

@bradob, you should mark your question with BUG tag. Also reach out to Splunk Support if you have Splunk Entitlement. However, I feel this issue might be just impacting you.

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
0 Karma

Explorer

Java version : 1.8.0_152-b16

0 Karma

I have exactly the same issue.
However the "Answer" / Workround below is not permitted in my environment as I do not have shell access to the server.
Please can we raise this as a bug in dbConnect - since if the SQL parses then the connection etc is valid.

0 Karma

Contributor

Hi @bradob,
You probably need to check below troubleshooting steps for dbconnect in splunk docs.
http://docs.splunk.com/Documentation/DBX/3.0.1/DeployDBX/Troubleshooting#DB_Connect_logging

Explorer

splunk_app_db_connect_server.log : 2017-12-28 08:59:00.800 -0500 [dw-55 - PUT /api/inputs/Data_Test] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: 5a9caaff16dce937
java.lang.NullPointerException: null
at com.splunk.dbx.server.util.ResultSetMetaDataUtil.isTableHavingSameNameColumns(ResultSetMetaDataUtil.java:104)
at com.splunk.dbx.server.api.service.conf.impl.InputServiceImpl.update(InputServiceImpl.java:185)
at com.splunk.dbx.server.api.service.conf.impl.InputServiceImpl.update(InputServiceImpl.java:37)
at com.splunk.dbx.server.api.resource.InputResource.updateInput(InputResource.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
at io.dropwizard.jetty.NonblockingServletHolder.handle(NonblockingServletHolder.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
at io.dropwizard.servlets.ThreadNameFilter.doFilter(ThreadNameFilter.java:34)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
at io.dropwizard.jersey.filter.AllowedMethodsFilter.handle(AllowedMethodsFilter.java:50)
at io.dropwizard.jersey.filter.AllowedMethodsFilter.doFilter(AllowedMethodsFilter.java:44)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
at com.splunk.dbx.server.api.filter.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at com.codahale.metrics.jetty9.InstrumentedHandler.handle(InstrumentedHandler.java:240)
at io.dropwizard.jetty.RoutingHandler.handle(RoutingHandler.java:51)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:396)
at io.dropwizard.jetty.BiDiGzipHandler.handle(BiDiGzipHandler.java:68)
at org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:56)
at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:169)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:524)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:186)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Unknown Source)

0 Karma

SplunkTrust
SplunkTrust

How are you authenticating? Not all MS drivers work with all authentication methods. You may need to experiment to see which driver works best.

---
If this reply helps you, an upvote would be appreciated.
0 Karma

Explorer

I have validated the authentication and run a basic query. Credentials are authenticated locally to the SQL database. Once the query got complicated is when the error is occurring. Is there a limit to how in depth the SQL query can be? A basic select * from table works. Once I started doing inner joins and calling other tables from the database, renaming columns is when it wouldn't let me complete the process. Just note that the SQL query does complete successfully before going on to the next "page" where I choose how often, and have the option to "finish"

0 Karma

SplunkTrust
SplunkTrust

Given that, I'd say your query is probably too complex. IIRC, DB Connect throws your query into a "SELECT * FROM (your query here)" statement. You can try that directly on the DB to see what results. Also, turning on debug logging in DB Connect should show more about what is happening under the covers.

One way to simplify the query is to put the complicated bits into a view and invoke the view from DB Connect.

---
If this reply helps you, an upvote would be appreciated.
0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!