All Apps and Add-ons

[DB Connect] java.sql.SQLRecoverableException: IO Error: Connection reset by peer, Authentication lapse 140354 ms.

sylim_splunk
Splunk Employee
Splunk Employee

I've recently migrated to a new server with Splunk 7.2.1 + DB Connect 3.1.1 which intermittently shows an issue as below;
Some dashboard running many panels of dbxquery getting these errors;

2 errors occurred while the search was executing. Therefore, search results might be incomplete. Hide errors.
[subsearch]: java.sql.SQLRecoverableException: IO Error: Connection reset by peer, Authentication lapse 88400 ms.
java.sql.SQLRecoverableException: IO Error: Connection reset by peer, Authentication lapse 140354 ms.

I had never had this kind of error before the migration to this new server.
It's not happening always but very frequently. Please help.

sylim_splunk
Splunk Employee
Splunk Employee

Based on the symptoms of "happening intermittently". It appears to be a known issue around "/dev/random" and "/dev/urandom".
Tried as suggested below and worked around it. ;

https://docs.oracle.com/cd/E13209_01/wlcp/wlss30/configwlss/jvmrand.html

1. Open the $JAVA_HOME/jre/lib/security/java.security file in a text editor.
2. Change the line:
  securerandom.source=file:/dev/random
  to read:
  securerandom.source=file:/dev/urandom
3. Save your change and exit the text editor.
Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...