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!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

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 ...