All Apps and Add-ons

Error while adding new Oracle connection in DB connect app

mariamathewtel
Explorer

Hi,

I am facing an error while trying to establish a new Oracle connection in Splunk DB connect app. Added identities without any error. Below are the details. 

Error - There was an error processing your request. It has been logged (ID .....).

Have configured java- /java/jdk1.8.0_251-amd64/
Installed Drivers - Oracle 12.1

Splunk Version -  8.0.4.1
DB Connect Version - 3.3.1  & Build:5

dbx_settings.conf  =>
[java]
javaHome = /usr/java/jdk1.8.0_251-amd64/

identities.conf =>
[Oracle_iden]
disabled = 0
password = U2FsdGVkX1+cAT2Scp6riQGah0uCf5sGgSaFYe4qZ2U=
use_win_auth = 0
username = admin

inputs.conf =>
[http://db-connect-http-input]
disabled = 0
token = DF5BE1B9-0C3A-47F7-8B69-5815C91222B4

ui-metrics-collector.conf =>
[collector]
app_id = e3743b4e-9f25-4ccb-ac66-122fa9e48149
mode = on

db_connections.conf =>
[Oracle_Conn]
connection_type = oracle
database = test
disabled = 0
host = <hostname>
identity = Oracle_iden
jdbcUseSSL = false
localTimezoneConversionEnabled = false
port = 1521
readonly = false
timezone = Australia/Sydney

 

Can someone please help me to fix this issue. 

 

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust
What errors do you see in splunkd.log or splunk_app_db_connect*.log?
---
If this reply helps you, Karma would be appreciated.
0 Karma

mariamathewtel
Explorer

Hi @richgalloway ,

The errors in splunkd.log are :-

08-20-2020 02:13:28.815 +0800 ERROR TcpInputProc - Error encountered for connection from src=192.168.91.110:54671. Read Timeout Timed out after 600 seconds.
08-20-2020 02:13:30.614 +0800 ERROR TcpInputProc - Error encountered for connection from src=192.168.91.116:57329. Read Timeout Timed out after 600 seconds.
08-20-2020 15:31:47.454 +0800 ERROR TcpInputProc - Error encountered for connection from src=172.28.214.43:34054. Read Timeout Timed out after 600 seconds.
08-20-2020 15:31:47.813 +0800 ERROR TcpInputProc - Error encountered for connection from src=172.28.214.41:23511. Read Timeout Timed out after 600 seconds.
08-20-2020 15:31:47.882 +0800 ERROR TcpInputProc - Error encountered for connection from src=172.28.214.63:49707. Read Timeout Timed out after 600 seconds.
08-20-2020 15:31:48.263 +0800 ERROR TcpInputProc - Error encountered for connection from src=172.28.214.60:23087. Read Timeout Timed out after 600 seconds.
08-20-2020 15:31:49.236 +0800 ERROR TcpInputProc - Error encountered for connection from src=172.28.216.44:32187. Read Timeout Timed out after 600 seconds.
08-20-2020 18:35:05.684 +0800 ERROR ApplicationUpdater - Error checking for update, URL=https://apps.splunk.com/api/apps:resolve/checkforupgrade: Connect Timeout
08-20-2020 18:41:50.340 +0800 ERROR ApplicationUpdater - Error checking for update, URL=https://apps.splunk.com/api/apps:resolve/checkforupgrade: Connect Timeout

Errors in splunk_app_db_connect_dbx.log :-


2020-08-20T18:38:24+0800 [ERROR] [__init__.py], line 201: [HTTP 500] Error in 'litsearch' command: Your Splunk license expired or you have exceeded your license limit too many times. Renew your Splunk license by visiting www.splunk.com/store or calling 866.GET.SPLUNK.
2020-08-20T20:56:29+0800 [ERROR] [__init__.py], line 201: [HTTP 500] Error in 'litsearch' command: Your Splunk license expired or you have exceeded your license limit too many times. Renew your Splunk license by visiting www.splunk.com/store or calling 866.GET.SPLUNK.

Errors in splunk_app_db_connect_server.log :-

2020-08-20 19:13:29.021 +0800 [dw-56 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: fd3a7a3099a4a86d
2020-08-20 19:15:52.201 +0800 [dw-57 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: ce3de8cb966e2598
2020-08-20 20:36:59.795 +0800 [dw-58 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: 660c7169fe8b1252
2020-08-20 21:18:03.338 +0800 [dw-56 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: 2f988c7cd297e9e7
2020-08-20 21:18:27.249 +0800 [dw-60 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: fcb9fa36bb0dffd5
2020-08-20 21:18:31.971 +0800 [dw-56 - POST /api/connections/status] ERROR io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: 343a9b7f02b77722

0 Karma

richgalloway
SplunkTrust
SplunkTrust
The first step is to fix the license problem. Either install an unexpired license or a Reset license to correct the limit violation.
The other errors could be related to the license problem or could be a network problem.
---
If this reply helps you, Karma would be appreciated.
0 Karma

mariamathewtel
Explorer

hi @richgalloway ,

Thanks for the reply.
But i did the same setup in another server with same expired license and it was successful. So why is this happens to one server only? 

 

Tags (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust
Apparently, there is something different between the two servers. Perhaps it's a network problem. Once you isolate the difference then the solution should be clear.
---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Cultivate Your Career Growth with Fresh Splunk Training

Growth doesn’t just happen—it’s nurtured. Like tending a garden, developing your Splunk skills takes the right ...