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!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...