All Apps and Add-ons

java.lang.RuntimeException: java.security.GeneralSecurityException: org.bouncycastle.crypto.InvalidCipherTextException: pad block corrupted

sathwikr076
Communicator

Hi,

We have added new search head to the cluster and when we try to do some db query we are getting the above error. We tested using individual search heads and it was running fine in other two search heads. The problem here is we are using DB connect 3 in cluster environment, which is not recommended by splunk. Please let us know if anyone have any idea about this.

Thanks,
Sathwik.

0 Karma
1 Solution

sathwikr076
Communicator

identity.dat file is not updated properly on to the Sh3 that we added in the cluster and that was causing that problem. It was continuously contacting the database and after few failed attempts causing the account to be locked and making the database not available to other search heads as well. So when we made identity.dat file same as other search heads, the issue got resolved.

Thanks.

View solution in original post

0 Karma

sathwikr076
Communicator

identity.dat file is not updated properly on to the Sh3 that we added in the cluster and that was causing that problem. It was continuously contacting the database and after few failed attempts causing the account to be locked and making the database not available to other search heads as well. So when we made identity.dat file same as other search heads, the issue got resolved.

Thanks.

0 Karma
Get Updates on the Splunk Community!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

March Community Office Hours Security Series Uncovered!

Hello Splunk Community! In March, Splunk Community Office Hours spotlighted our fabulous Splunk Threat ...

Stay Connected: Your Guide to April Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars in April. This post ...