We deployed SAM 1.1 a couple of weeks ago on a customer site and it had an issue starting up due to be unable to read the keystore. We discovered the problem because we were seeing the symptoms in RHBZ 875876. and it looked like it was fixed SAM 1.2 so we waited for the release to see if it was. It appears we're still having issues. thumbslug-0.0.28-1.el6_3.noarch debug: Feb 25 16:53:05 [main] WARN org.candlepin.thumbslug.Main - Shutting down... Feb 25 16:53:05 [main] INFO org.candlepin.thumbslug.ssl.SslContextFactory - reading keystore Feb 25 16:53:06 [main] ERROR org.candlepin.thumbslug.Main - Unable to load the ssl keystore. Check that ssl.keystore and ssl.keystore.password are set correctly. org.candlepin.thumbslug.ssl.SslKeystoreException: Failed to initialize the server-side SSLContext. at org.candlepin.thumbslug.ssl.SslContextFactory.getServerContext(SslContextFactory.java:92) at org.candlepin.thumbslug.Main.configureSSL(Main.java:73) at org.candlepin.thumbslug.Main.main(Main.java:158) Caused by: java.io.IOException: failed to decrypt safe contents entry: javax.crypto.BadPaddingException: Given final block not properly padded at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:1304) at java.security.KeyStore.load(KeyStore.java:1214) at org.candlepin.thumbslug.ssl.SslContextFactory.getServerContext(SslContextFactory.java:71) ... 2 more Caused by: javax.crypto.BadPaddingException: Given final block not properly padded at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676) at com.sun.crypto.provider.PKCS12PBECipherCore.implDoFinal(PKCS12PBECipherCore.java:355) at com.sun.crypto.provider.PKCS12PBECipherCore$PBEWithSHA1AndRC2_40.engineDoFinal(PKCS12PBECipherCore.java:462) at javax.crypto.Cipher.doFinal(Cipher.java:2087) at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:1295) ... 4 more RHBZ 859128 looks very similar to the problem but doing: cp /etc/candlepin/certs/candlepin-ca.crt /etc/thumbslug/client-ca.pem Makes no difference, I still get: # service thumbslug status thumbslug dead but pid file exists
*** Bug 915408 has been marked as a duplicate of this bug. ***
Please attach the output of katello-debug as a private attachment.
(In reply to comment #2) > Please attach the output of katello-debug as a private attachment. I don't have the option to upload a private attachment
A clean install of SAM 1.2 seems to work OK. Seems there's a problem in the upgrade process.
This is fixed in katello and will be available in next SAM release.
SNAP0 contains these bug fixes. Moving to ON_QA.
VERIFIED : # rpm -qa | grep katello katello-selinux-1.4.4-2.el6sat.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-certs-tools-1.4.2-2.el6sat.noarch katello-common-1.4.3-5.el6sam_splice.noarch katello-configure-1.4.4-2.el6sat.noarch katello-cli-common-1.4.3-4.el6sat.noarch katello-glue-elasticsearch-1.4.3-5.el6sam_splice.noarch katello-headpin-all-1.4.3-5.el6sam_splice.noarch katello-cli-1.4.3-4.el6sat.noarch katello-glue-candlepin-1.4.3-5.el6sam_splice.noarch signo-katello-0.0.10-2.el6sat.noarch katello-headpin-1.4.3-5.el6sam_splice.noarch # service thumbslug status thumbslug (pid 18088) is running... # tail -f /var/log/thumbslug/error.log at sun.security.ssl.Handshaker.processLoop(Handshaker.java:609) at sun.security.ssl.Handshaker$1.run(Handshaker.java:549) at sun.security.ssl.Handshaker$1.run(Handshaker.java:547) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:968) at org.jboss.netty.handler.ssl.SslHandler$2.run(SslHandler.java:1023) at org.jboss.netty.handler.ssl.ImmediateExecutor.execute(ImmediateExecutor.java:37) at org.jboss.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:1020) at org.jboss.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:910) ... 11 more
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1390.html