Why is KV Store certificate renewal not working?

[conwaw]

Hi,

Does anyone know where may I find official documentation which will help me to resolve this problem?

I have renewed a certificate using this tutorial, but for some reason, MongoDB is still not starting.

https://splunkonbigdata.com/2019/07/03/failed-to-start-kv-store-process-see-mongod-log-and-splunkd-l...

mongodb.log is showing this error...

2020-04-11T10:27:08.899Z W CONTROL [main] net.ssl.sslCipherConfig is deprecated. It will be removed in a future release.
2020-04-11T10:27:08.902Z F NETWORK [main] The provided SSL certificate is expired or not yet valid.
2020-04-11T10:27:08.902Z F - [main] Fatal Assertion 28652 at src/mongo/util/net/ssl_manager.cpp 1145
2020-04-11T10:27:08.902Z F - [main] 
***aborting after fassert() failure

Can anyone here help?

Cheers
Konrad

[kell_cena]

Worked on 9.2.1 , the add-on was not running.

[robertlynch2020]

worked for me - but - surely this is something that should not happen- there are no warnings in Splunk it just bang - Splunk is down in production

[helge]

On Windows, you may get the following error message in mongod.log:

Fatal Assertion 50755 at src\mongo\util\net\ssl_manager_windows.cpp 1609

To fix the error that causes mongod to terminate, you need the following in addition to deleting server.pem:

1. Open Windows certificate management MMC for the local computer
2. Navigate to Personal > Certificates
3. Delete any entries named SplunkServerDefaultCert

[pavankumarh]

This worked after lot of research. Thank You.. 

Just for others.. Dont run certmgr.msc on server. Instead run certlm.msc to see the "SplunkServerDefaultCert" entries. 

I was doing this wrong. 

[Gregski11]

appreciate you, thank you so much 

[vinod94 · Accepted solution]

Hi dyude @conwaw ,

Try this,

1. Stop the Splunk service.

2. Rename the server.pem($SPLUNK_HOME/etc/auth) to server.pemck or move the pem file.

3. Start the Splunk service.

It will generate a new server.pem

Let me know if this helps. 🙂

[mahegstrom]

Just upgraded to 9.2.2 on our heavy forwarder and had the same KV store errors. Our mongod.log displayed the same ssl errors. These steps worked perfectly! 

[eholz1]

This has not worked for me, any ideas? here is my SSLconfig line in server.conf

[sslConfig]

sslPassword = $7$IVRDJa9zz5Rmt3ZehltRkIK2vnYpOPiMSSAZMNAUqdQ7hQAGf2GNXg

No other lines in the file. I am open to suggestions, and get this as well:

WARNING: Server Certificate Hostname Validation is disabled., see server.conf, etc

Thanks,

EWHolzx

[tfrederick74656]

Still working in 2024, thanks so much!!

[jmrubio]

Three years later and this worked! Thanks!!

[Ola]

Thank you so much . It works for me!!!

[linhmai_bne]

This solution is the one I have been looking for. Thank you.

[juhatamminen]

Hi,

I also have to do the same for server_pkcs1.pem file.

[fabiofox]

it's working! thank you for this 🙏

[Gregski11]

awesome, thank you, that did it

[freddy_Guo]

That worked beautifully for us. Thank you.

[rmendoza]

This did the trick, thank you!

[SirDrake7]

Thank you for this fix big time.

[Eduardo_Perez]

Thanks, it worked for me.

[PavelP]

Hello @conwaw ,

did you find a solution for your problem?

If still not, try this command on the same host and post here a (redacted) output:

openssl s_client -connect localhost:8191