Intermittent Data Ingestion Failures in DB Inputs with Status Code "500" (Internal Server Error) in Splunk Db connect App.

Available Languages

Updated:September 29, 2026
Document ID:SPLK047671

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise Splunk Cloud Splunk Apps and Add-on

Description

On the Splunk DB Connect App’s UI, queries in the input tab yield the expected results; however, data ingestion during scheduled cron runs has been inconsistent.

The number of processed inputs fluctuates - on some days, only a few inputs are ingested successfully, while on other days, all inputs complete without issues.


Investigation

Upon reviewing internal logs using the following SPL query:

index=_internal "*db*" sourcetype="*metrics*"

Error Logs:

2024-09-29 05:40:36.189 +0000 INFO c.s.dbx.server.task.listeners.JobMetricsListener - action=collect_job_metrics connection=CONNECTIONNAME jdbc_url=jdbc:postgresql://CONNECTIONNAME.zsservices.local:5432/platform_analytics_wh?ssl=verify status=FAILED input_name=InputName batch_size=1000 error_threshold=N/A is_jmx_monitoring=false start_time=2024-09-29_05:40:00 end_time=2024-09-29_05:40:36 duration=35376 read_count=0 write_count=0 error_count=02024-09-29T05:40:36+0000 [WARNING] [dbx_db_input.py], line 68 : Run Db Input name=InputName failed, status=500 content=b'{"code":500,"message":"There was an error processing your request. It has been logged (ID 900c184950af9703)."}'

All failed inputs display the same error message. 

From the above logs, it appears that, on certain days, a high data volume from the database causes timeouts, resulting in an internal server error with status code 500.


Resolution

To address the issue, follow these steps:

1. Navigate to $SPLUNK_HOME/etc/apps/splunk_app_db_connect/config/dbxquery_server.yml.

2. Set both socketTimeout and stdinTimeout to 600.

3. Restart the Splunk service.

4. In the Splunk UI, go to Apps > Splunk DB Connect App > Data Lab > Inputs. 
Edit the reported input, increase the query timeout time, and save the input.


The relevant KB here for this issue.

Explanation of the error here

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles