4 Replies Latest reply on Oct 25, 2017 9:10 AM by Roland Pocek

    BMC Discovery Upgrade to v11.2 from v11.1 patch 5

      Share This:

      Hi,

      i just upgraded our BMC Discovery from v11.1.0.5 to v11.2 but reasoning service is getting stuck to start and application is not able to come up.

      i'm getting below error. could someone help please:

       

        • 1. Re: BMC Discovery Upgrade to v11.2 from v11.1 patch 5
          Andrew Waters

          For some reason the system could not create, or more likely delete, a node in the datastore.

           

          You are going to have to talk to customer support there is no way you can go through enough detail on a forum.

          2 of 2 people found this helpful
          • 3. Re: BMC Discovery Upgrade to v11.2 from v11.1 patch 5

            thanks both,

             

            we found indexing issue post doing db_verify. we did re-indexing but it did not help. it still getting stuck at reasoning service.

             

            db_verify: p0002_rInference_pidx: BDB0090 DB_VERIFY_BAD: Database verification failed

             

            latest logs :

             

            [tideway@GDCADDMAP001
            log]$ tail tw_svc_model.log

            140390635882240:
            2017-10-14 16:54:34,313: model.datastore.ds_store: USEFUL: Reindex progress:
            435394401 / 436417766 (99%). About 1 minute remaining.

            140390635882240:
            2017-10-14 16:55:54,318: model.datastore.ds_store: USEFUL: Reindex progress: 435703701 / 436417766 (99%).

            140390635882240:
            2017-10-14 16:56:44,321: model.datastore.ds_store: USEFUL: Reindex progress: 435979701 / 436417766 (99%).

            IOR:010000002a00000049444c3a746964657761792e636f6d2f4d6f64656c434f5242412f41756469742f4d61696e3a312e300000000100000000000000a7000000010102000b00000031302e312e37362e32380000bc6100000d000000546964657761792f41756469740000000300000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100025454413b000000010000000d0000004744434144444d4150303031000000001f0000002f746d702f6f6d6e692d746964657761792f74775f7376635f6d6f64656c00

            140390635882240:
            2017-10-14 16:58:04,612: model.main: INFO: Model service ready.

            140390635882240:
            2017-10-14 16:58:05,219: model.search.servants: INFO: Search 1 ([model]):

                   SEARCH PatternModule

                   WHERE active AND content HAS SUBWORD 'host_type' AND content MATCHES "\\bhost_type\\b"

                   SHOW name,

                        creationTime(#UploadItem:UploadContents:Upload:KnowledgeUpload),

                        UploadItem:UploadContents:Upload:KnowledgeUpload.name,

                        origin

                   PROCESS WITH unique(1)

               Starting SQL Provider
            service:                       
            [  OK  ]

               Starting CMDB Sync (Exporter)
            service:               
            [  OK  ]

               Starting CMDB Sync (Transformer)
            service:            
            [  OK  ]

                Starting Reasoning
            service:                          
            [FAILED]

            Sat
            Oct 14 16:58:49 2017 : tw_svc_reasoning started.

            Traceback
            (most recent call last):

            File "./main.py", line 187, in <module>

            File "./main.py", line 159, in main

            File "./upgrade.py", line 1124, in upgradeModel

            File "./upgrade.py", line 111, in convertNodeKind

            File "./localtransaction.py", line 170, in commit

            • omniORB.CORBA.TRANSACTION_ROLLEDBACK:
              CORBA.TRANSACTION_ROLLEDBACK(0x0, CORBA.COMPLETED_NO)

            Sat
            Oct 14 16:59:44 2017 : Watchdog : Service failed after
            54.9 seconds (signal 0; exit 1). Restarting (1 restart so far).

             

            • 4. Re: BMC Discovery Upgrade to v11.2 from v11.1 patch 5
              Roland Pocek

              we have same issue, support ticket opened