We found Java Bridge server seems not to be running
Please advise!
jbridge.log
2014-06-18 09:41:51,931 INFO Checking for obsolete java libraries in /opt/splunk/etc/apps/dbx/bin/lib
2014-06-18 09:41:51,934 INFO Started JavaBridgeServer PID=5094
splunkd.log
06-18-2014 09:53:10.627 +0800 WARN HttpListener - Socket error from 127.0.0.1 while idling: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher
dbx.log
2014-06-18 09:44:52.439 main:INFO:SplunkContext - Splunk Context initialized: SplunkContext{env=SplunkEnvi
ronment{SPLUNK_HOME=/opt/splunk,SPLUNK_DB=/opt/splunk/var/lib/splunk}}
2014-06-18 09:44:58.145 main:INFO:Splunkd - Initialized Splunkd REST service service=127.0.0.1:8089 sessio
nKey=Rf^lkc54OI0hWjhqMhVbLtreEjjeW7F4Cp^8PQDBAPiO8P55LtqCHmLKlHi3F1aQXJLeI0qcEzysf3LUu_MeSfV^Tx2ptI_gLmWq8
t2s
This might be relevant to the second error you reference.
https://answers.splunk.com/answers/296893/how-can-i-force-a-specific-ecdhe-cipher-to-communi.html