4 Replies Latest reply on Dec 13, 2013 9:26 AM by Moses Arockiadass

    postmigration.exe failed with Keystore error

      We are upgrading our appserver from 8.2 to 8.3, this steps failed "Migrating compliance rules, discovery signatures, and smart group conditions"

       

       

      13 Dec 2013 14:04:16,917] [main] [ERROR] [::] [] problems reading or parsing keystore file:D:\Program Files\BMC Software\BladeLogic\NSH\br\deployments\_postmig\bladelogic.keystore

      [13 Dec 2013 14:04:16,933] [main] [ERROR] [::] [] Error installing to Start: name=bladelogic.service.management.ServerSocketFactory state=Create

      com.bladelogic.om.infra.app.service.ServiceInitializationException: java.io.IOException

        at com.bladelogic.om.infra.app.service.client.ServerSocketFactory.start(ServerSocketFactory.java:74)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

        at java.lang.reflect.Method.invoke(Unknown Source)

        at org.jboss.joinpoint.plugins.reflect.ReflectMethodJoinPoint.dispatch(ReflectMethodJoinPoint.java:72)

        at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:92)

        at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:452)

        at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:147)

        at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)

        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)

        at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:291)

        at com.bladelogic.om.infra.app.service.bootstrap.ServiceBeanXMLDeployer.deployBean(ServiceBeanXMLDeployer.java:38)

        at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:261)

        at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:117)

        at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:91)

        at com.bladelogic.om.infra.app.service.bootstrap.ServiceBootstrap.deploy(ServiceBootstrap.java:252)

        at com.bladelogic.om.infra.app.service.bootstrap.ServiceBootstrap.deployService(ServiceBootstrap.java:199)

        at com.bladelogic.om.infra.app.service.bootstrap.ServiceBootstrap.bootstrap(ServiceBootstrap.java:153)

        at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:91)

        at com.bladelogic.om.infra.app.service.bootstrap.ServiceBootstrap.startup(ServiceBootstrap.java:66)

        at com.bladelogic.om.infra.mfw.fw.BlManager.startWithType(BlManager.java:610)

        at com.bladelogic.om.infra.mfw.fw.BlManager.startWithType(BlManager.java:745)

        at com.bladelogic.om.infra.app.service.migration.PostMigration.doPostMigration(PostMigration.java:54)

        at com.bladelogic.om.infra.app.service.migration.PostMigration.main(PostMigration.java:40)

      Caused by: java.io.IOException

        at com.bladelogic.om.infra.app.service.client.ServerSocketFactory.createSocketFactory(ServerSocketFactory.java:169)

        at com.bladelogic.om.infra.app.service.client.ServerSocketFactory.start(ServerSocketFactory.java:70)

        ... 30 more

      Caused by: com.bladelogic.om.infra.mfw.util.BlException: java.io.IOException: Keystore was tampered with, or password was incorrect

        at com.bladelogic.security.cert.AppServerKeyStore.<init>(AppServerKeyStore.java:144)

        at com.bladelogic.security.cert.AppServerKeyStore.getInstance(AppServerKeyStore.java:224)

        at com.bladelogic.security.cert.AppServerKeyStore.getInstance(AppServerKeyStore.java:216)

        at com.bladelogic.om.infra.app.service.client.ServerSocketFactory.getAppServerKeyStore(ServerSocketFactory.java:183)

        at com.bladelogic.om.infra.app.service.client.ServerSocketFactory.createSocketFactory(ServerSocketFactory.java:158)

        ... 31 more

      Caused by: java.io.IOException: Keystore was tampered with, or password was incorrect

        at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source)

        at sun.security.provider.JavaKeyStore$JKS.engineLoad(Unknown Source)

        at java.security.KeyStore.load(Unknown Source)

        at com.bladelogic.security.cert.AppServerKeyStore.<init>(AppServerKeyStore.java:117)

        ... 35 more

      Caused by: java.security.UnrecoverableKeyException: Password verification failed

        ... 39 more

      [13 Dec 2013 14:04:16,980] [main] [INFO] [::] [] Starting Model Graph Service...

      [13 Dec 2013 14:04:19,304] [main] [INFO] [::] [] Model Graph Service started.

      [13 Dec 2013 14:04:19,320] [main] [INFO] [::] [] Starting Port Provider...

        • 1. Re: postmigration.exe failed with Keystore error
          Bill Robinson

          1  - delete the NSH/br/deployments/_postmig directory

          2 - ensure that the keystore password is correct in the _template instance.

          eg in nsh run:

          keypass=$(blenc -d BLencrypt:$(blasadmin -s _template show app certpass | grep CertPass | cut -f2 -d:) | tail -1)

           

          /D/Program\ Files/BMC\ Software/BladeLogic/NSH/jre/bin/keytool.exe -list -keystore "D:\Program Files\BMC Software\BladeLogic\NSH\br\deployments\_template\bladelogic.keystore" -storepass "${keypass}"

           

          that should produce some output like:

           

           

          if not you have some mismatch between the keystore file in the _template and the passwd used which means you need to either reset the certpassword in _template or generate a new keystore, put that in all instances and reset the passwd.

          1 of 1 people found this helpful
          • 2. Re: postmigration.exe failed with Keystore error

            Thanks Bill. What is the significance of this postmigration step? Also we have regenerated the keystore and started the appservercoz the appserver is started and running fine. I shall run the steps given here.

             

            Is this failure will create any issue?

             

            Thanks again.

            • 3. Re: postmigration.exe failed with Keystore error
              Bill Robinson

              for the 8.2 to 8.3 upgrade it will fix a possible issue related to cleanup of smart groups.

              • 4. Re: postmigration.exe failed with Keystore error

                Thanks Bill.

                 

                I have taken these points from documentation:

                https://docs.bmc.com/docs/display/public/bsa83/Migrating+compliance+rules%2C+discovery+signatures%2C+and+smart+group+conditions

                In the following upgrade scenarios you must run the postmigration file to migrate various types of rules that were defined in the earlier version of BMC Server Automation:

                • If you are upgrading from a pre-8.0 version of BMC Server Automation, after you complete the basic migration of database data using the BMC BladeLogic Data Migration Manager, you must run the postmigration file. This file migrates the pre-8.x compliance rules and discovery signatures stored in the core BMC Server Automation database and converts them to the new rule format introduced in BMC Server Automation version 8.0.


                     we are upgrading from 8.2.01.328 to 8.3.0.115 - is this still applicable for us. Please let us know

                 

                • If smart group conditions were defined in any earlier version of BMC Server Automation and you are upgrading to version 8.3.01 or 8.3.02, you must run the postmigration file to migrate and update smart group conditions. This step eliminates future problems in database cleanup processes after you delete smart groups.

                  

                     we are upgrading from 8.2.01.328 to 8.3.0.115 - is this still applicable for us. Please let us know

                 

                Regards