All Database Related Splunk indexes stopped working post update to 7.1.1

New Member

We recently updated splunk to latest version of 7.1.1 post that update, the splunk database connections are all not working. We receive the below warnings in the Jbrige.log

ERROR Java process returned error code 1! Error: Initializing Splunk context... Environment: SplunkEnvironment{SPLUNK_HOME=D:\Program Files\Splunk,SPLUNK_DB=D:\Program Files\Splunk\var\lib\splunk} Configuring Log4j... Exception in thread "main" com.splunk.config.SplunkConfigurationException: IO Error while reading configuration from Splunkd: Received fatal alert: protocol_version at at at com.splunk.config.cache.CachedConfigurationAdapter.readConfig( at com.splunk.config.cache.CachedConfigurationAdapter.readStanza( at com.splunk.env.SplunkContext.getConfigStanza( at com.splunk.env.SplunkContext.initialize( at com.splunk.bridge.JavaBridgeServer.main( Caused by: Received fatal alert: protocol_version at Source) at Source) at Source) at Source) at Source) at Source) at Source) at Source) at Source) at Source) at at at ... 6 more

Splunkd.log shows the below message:

07-06-2018 12:36:17.089 +0100 WARN SSLCommon - Received fatal SSL3 alert. ssl_state='SSLv3 read client hello C', alert_description='protocol version'.
07-06-2018 12:36:17.089 +0100 WARN HttpListener - Socket error from while idling: error:1408A10B:SSL routines:ssl3_get_client_hello:wrong version number

We are using JRE6 and splunk DBConnect version 1. the JBridge Server status in the splunk shows as loading..

Please can someone help.

Tags (2)
0 Karma
.conf21 Now Fully Virtual!
Register for FREE Today!

We've made .conf21 totally virtual and totally FREE! Our completely online experience will run from 10/19 through 10/20 with some additional events, too!