9 Replies Latest reply on Jul 12, 2018 8:48 AM by 72ABW SCOOT

    BladeLogic Application Server service won't start after database server moved

    72ABW SCOOT
    72ABW SCOOT Jul 11, 2018 3:20 PM
      Share:|

      Our DBA guy moved bladelogic database to new server with SQL2014.

      I had used command:

       

      Blasadmin -a set database ConnectionString {new Server name}

       

      to point the application server to new databse server and it show the connectionstring is pointing to correct database server.

       

      but somehow I can't start Bladelogic Application server , it coming back with error :

       

      " The Bladelogic Application Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs "

       

      I reboot our application server too but it won't help.

       

      Any suggestion?

       

      Thanks in advance.

      • 126 Views
      • Categories: Administration
      • Tags:
        • 1. Re: BladeLogic Application Server service won't start after database server moved
          Bill Robinson
          Bill Robinson Employee Jul 11, 2018 3:24 PM (in response to 72ABW SCOOT)

          how about looking in the appserver log to see why it's not starting ?

          • 3. Re: BladeLogic Application Server service won't start after database server moved
            72ABW SCOOT
            72ABW SCOOT Jul 12, 2018 7:09 AM (in response to Bill Robinson)

            This is what the log looks like, seem like the login issue but our DBA had not change the username and password for the new database

             

            11 Jul 2018 14:05:56,415] [Scheduled-System-Tasks-Thread-13] [ERROR] [System:System:] [Update Job Run Counts] Cannot open database "BladeLogic" requested by the login. The login failed. ClientConnectionId:57dae46f-205d-4c3d-a803-83ec1c0eac83

            java.sql.SQLException: Cannot open database "BladeLogic" requested by the login. The login failed. ClientConnectionId:57dae46f-205d-4c3d-a803-83ec1c0eac83

            at com.bladelogic.om.infra.shared.db.pool.BlSqlServerDbConnectionFactory.createConnection(BlSqlServerDbConnectionFactory.java:68)

            at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)

            at com.bladelogic.om.infra.shared.db.pool.BlPoolableConnectionFactory.makeObject(BlPoolableConnectionFactory.java:85)

            at com.bladelogic.om.infra.app.service.db.BlDbPoolableConnectionFactory.makeObject(BlDbPoolableConnectionFactory.java:51)

            at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)

            at com.bladelogic.om.infra.shared.db.pool.BlConnObjectPool$BlDbObjectPool.borrowObject(BlConnObjectPool.java:128)

            at com.bladelogic.om.infra.shared.db.pool.BlConnObjectPool.borrowObject(BlConnObjectPool.java:240)

            at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)

            at com.bladelogic.om.infra.shared.db.pool.BlDbcpConnPool.getNewConnection(BlDbcpConnPool.java:206)

            at com.bladelogic.om.infra.shared.db.pool.BlPooledDbDataSource.getConnection(BlPooledDbDataSource.java:100)

            at com.bladelogic.om.infra.app.service.db.BlAsDbDataSource.getConnection(BlAsDbDataSource.java:92)

            at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.getConnection(DefaultDatabaseServiceImpl.java:523)

            at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.executeUpdate(DefaultDatabaseServiceImpl.java:1435)

            at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.executeUpdate(DefaultDatabaseServiceImpl.java:1429)

            at com.bladelogic.om.infra.app.service.job.JobRunServiceImpl.updateJobRunCounts(JobRunServiceImpl.java:495)

            at com.bladelogic.om.infra.app.service.job.JobManagerImpl$UpdateJobRunProgressCountsTask.execute(JobManagerImpl.java:648)

            at com.bladelogic.om.infra.app.service.timer.ScheduledTaskReference.run(ScheduledTaskReference.java:95)

            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

            at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

            at java.lang.Thread.run(Thread.java:745)

            • 4. Re: BladeLogic Application Server service won't start after database server moved
              72ABW SCOOT
              72ABW SCOOT Jul 12, 2018 7:11 AM (in response to Pradeep Pattebahadur)

              I followed step 1 and 2 but didn't do step 3 and 4 since our DBA didn't change the username and password. The log showed is the login failed:

               

              11 Jul 2018 14:05:56,415] [Scheduled-System-Tasks-Thread-13] [ERROR] [System:System:] [Update Job Run Counts] Cannot open database "BladeLogic" requested by the login. The login failed. ClientConnectionId:57dae46f-205d-4c3d-a803-83ec1c0eac83

              java.sql.SQLException: Cannot open database "BladeLogic" requested by the login. The login failed. ClientConnectionId:57dae46f-205d-4c3d-a803-83ec1c0eac83

              at com.bladelogic.om.infra.shared.db.pool.BlSqlServerDbConnectionFactory.createConnection(BlSqlServerDbConnectionFactory.java:68)

              at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)

              at com.bladelogic.om.infra.shared.db.pool.BlPoolableConnectionFactory.makeObject(BlPoolableConnectionFactory.java:85)

              at com.bladelogic.om.infra.app.service.db.BlDbPoolableConnectionFactory.makeObject(BlDbPoolableConnectionFactory.java:51)

              at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)

              at com.bladelogic.om.infra.shared.db.pool.BlConnObjectPool$BlDbObjectPool.borrowObject(BlConnObjectPool.java:128)

              at com.bladelogic.om.infra.shared.db.pool.BlConnObjectPool.borrowObject(BlConnObjectPool.java:240)

              at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)

              at com.bladelogic.om.infra.shared.db.pool.BlDbcpConnPool.getNewConnection(BlDbcpConnPool.java:206)

              at com.bladelogic.om.infra.shared.db.pool.BlPooledDbDataSource.getConnection(BlPooledDbDataSource.java:100)

              at com.bladelogic.om.infra.app.service.db.BlAsDbDataSource.getConnection(BlAsDbDataSource.java:92)

              at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.getConnection(DefaultDatabaseServiceImpl.java:523)

              at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.executeUpdate(DefaultDatabaseServiceImpl.java:1435)

              at com.bladelogic.om.infra.app.service.db.DefaultDatabaseServiceImpl.executeUpdate(DefaultDatabaseServiceImpl.java:1429)

              at com.bladelogic.om.infra.app.service.job.JobRunServiceImpl.updateJobRunCounts(JobRunServiceImpl.java:495)

              at com.bladelogic.om.infra.app.service.job.JobManagerImpl$UpdateJobRunProgressCountsTask.execute(JobManagerImpl.java:648)

              at com.bladelogic.om.infra.app.service.timer.ScheduledTaskReference.run(ScheduledTaskReference.java:95)

              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

              at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

              at java.lang.Thread.run(Thread.java:745)

              • 5. Re: BladeLogic Application Server service won't start after database server moved
                Pradeep Pattebahadur
                Pradeep Pattebahadur Jul 12, 2018 7:27 AM (in response to 72ABW SCOOT)

                Could you post result of "show database all" in blasadmin prompt.

                • 6. Re: BladeLogic Application Server service won't start after database server moved
                  72ABW SCOOT
                  72ABW SCOOT Jul 12, 2018 7:40 AM (in response to Pradeep Pattebahadur)

                  hmmm database did not show here:

                   

                  To change future application servers, blasadmin must be run against the _templat

                  e deployment. Please refer to the chapter 'Configuring the Application Server' i

                  n the Administration Guide for further information.

                  blasadmin now running against deployment: default

                  Bladelogic Admin Utility; Version 8.9.00.136.

                  Copyright (c) 2008-2016 BMC Software, Inc. All rights reserved.

                  Copyright (c) 1996-2008 BladeLogic, Inc. All rights reserved.

                  Type 'help' for Bladmin help.

                  bladmin:default>show database all

                  [Database]

                  [12 Jul 2018 07:35:23,826] [main] [ERROR] com.microsoft.sqlserver.jdbc.SQLServer

                  Exception: Invalid object name 'system_property'.

                  bladmin:default>show database all

                  [Database]

                  [12 Jul 2018 07:35:56,617] [main] [ERROR] com.microsoft.sqlserver.jdbc.SQLServer

                  Exception: Invalid object name 'system_property'.

                  bladmin:default>

                   

                  but show database connectionstring show something I out in

                   

                  PS C:\> blasadmin show database connectionstring

                  To change future application servers, blasadmin must be run against the _template deployment. Please refer to the chapte

                  r 'Configuring the Application Server' in the Administration Guide for further information.

                  blasadmin now running against deployment: default

                  ConnectionString:jdbc:sqlserver://WWYK-DB-2029v:1433

                  PS C:\>

                  • 7. Re: BladeLogic Application Server service won't start after database server moved
                    Bill Robinson
                    Bill Robinson Employee Jul 12, 2018 7:49 AM (in response to 72ABW SCOOT)

                    Exception: Invalid object name 'system_property'.

                    -> are you sure you are connecting to the right db ?

                     

                    look in the NSH/br/deployments/global.properties - is the username correct ?  if you login to the database in the connection string w/ that db user do you see a table named 'system_property' in the bladelogic db ?

                    • 8. Re: BladeLogic Application Server service won't start after database server moved
                      72ABW SCOOT
                      72ABW SCOOT Jul 12, 2018 8:05 AM (in response to Bill Robinson)

                      the username is correct

                       

                      #Thu Jul 12 07:59:09 CDT 2018

                      CertStore=bladelogic.keystore

                      user=BladeLogic

                      url=jdbc\:sqlserver\://WWYK-DB-2029v\:1433

                      driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

                      • 9. Re: BladeLogic Application Server service won't start after database server moved
                        72ABW SCOOT
                        72ABW SCOOT Jul 12, 2018 8:48 AM (in response to Bill Robinson)

                        I found the global.properties backup file and copied over the ecrypted password and voila, IT WORKED.

                         

                        Thanks for your help