Abnormal termination of deduplication service detected on MA. Please call in a support ticket

Last post 11-03-2010, 11:17 AM by Bill Baumann. 11 replies.
Sort Posts: Previous Next
  • Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 07-20-2010, 6:54 AM

    Any ideas how to fix this problem as my AUX copy job is now pending?

    Thanks in anticipation

     

    SIDBEngine.log:

    2224 ab0 07/20 11:14:02 ### SIDBEngine [C:\Program Files\CommVault\Galaxy\Base\SIDB2.exe] started for Engine Id = 28, Copy id = 180, SIDB path = D:\DeDup\Aux_DBA, Instance = Instance001, client name = commvaultaux, User = , New DB = 0, Signature type = 4, Age = 157680000, Redundancy Factor [1]
    2224 ab0 07/20 11:14:02 ### Setting max threads to 20
    2224 ab0 07/20 11:14:02 ### Setting DB admin thread wakeup time to 600 Sec(s)
    2224 ab0 07/20 11:14:02 ### Idle timeout set to 0 Sec(s)
    2224 ab0 07/20 11:14:02 ### Minimum time elapsed since last connect time [10]
    2224 ab0 07/20 11:14:02 ### Idle Session timeout set to 0 Sec(s)
    2224 ab0 07/20 11:14:02 ### Max connections beyond which pruning requests will be rejected [5]
    2224 ab0 07/20 11:14:02 ### Geting Low-DiskSpace Threshold From CS for engine-id 28
    2224 ab0 07/20 11:14:02 ### SidbStorInfo received...LowDisk Space  = 0
    2224 ab0 07/20 11:14:02 ### Setting Low-DiskSpace Threshold 200MB as default
    2224 ab0 07/20 11:14:02 ### Low disk space threshold set to 200 MB
    2224 ab0 07/20 11:14:02 ### Successfully initialized the thread pool.
    2224 ab0 07/20 11:14:02 ### Initialized the CVD and SIDB sync mutex
    2224 ab0 07/20 11:14:02 ### N-Instancing Level set to [2]
    2224 ab0 07/20 11:14:02 ### Use transaction for commit records [true]
    2224 ab0 07/20 11:14:02 ### Going to fetch SIDB information from the commserve for engine id [28]
    2224 ab0 07/20 11:14:02 ### Fetched SIDB information from the commserve successfully.
    2224 ab0 07/20 11:14:02 ### Detected unclean shutdown of previous instance of sidb. State [1], Last modified [1279543453], Owner [4992]
    2224 ab0 07/20 11:14:02 ### Cannot start the DBProcessor object. return code = 53027

  • Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 07-20-2010, 9:45 AM
    Hello Gateshead,

    It would be best to log a call with support and allow them to have a closer look at this issue – the log snippet above is not enough detail to deduce what the issue may be.

    MattR
  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 07-20-2010, 10:33 AM

    Hi Gateshead,

    Is service pack 4 installed here?

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 07-21-2010, 3:19 AM

    SP4 with May post pack is installed

     

    Thanks

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 07-21-2010, 9:13 AM
    Thanks, Gatehead

    Please do open a call with support so that they may troubleshoot the issue further with you
  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 1:58 AM

    Hi!

     

    We're having the exact same problem now. Did you find a work-around/solution? I can't seal the previous deduplication store either.

     

    //Oscar

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 2:01 AM

    Here is the extract from our logs:

     

    10486 1   11/03 06:58:47 ### ::respond() - Responding to Challenge10486 1   11/03 06:58:47 ### ::UserLogin() - Application Login for SIDBEngine10486 1   11/03 06:58:47 ### ----------------------------SIDB Engine Started--------------------------------10486 1   11/03 06:58:47 ### SIDBEngine [/opt/hds/Base/sidb2] started for Engine Id = 24, Copy id = 80, SIDB path = /dedup02-sisdb1/full1mret1mdb-nostage, Instance = Instance001, client name = cv-dedup02.hiddendomain.se, User = , New DB = 0, Signature type = 4, Age = 2764800, Redundancy Factor [1]10486 1   11/03 06:58:47 ### Surprisingly selectRunning is already present g_mapCvSessionServerToSelectRunning10486 1   11/03 06:58:47 ### Setting max threads to 2010486 1   11/03 06:58:47 ### Setting DB admin thread wakeup time to 600 Sec(s)10486 1   11/03 06:58:47 ### Idle timeout set to 0 Sec(s)10486 1   11/03 06:58:47 ### Minimum time elapsed since last connect time [10]10486 1   11/03 06:58:47 ### Idle Session timeout set to 0 Sec(s)10486 1   11/03 06:58:47 ### Max connections beyond which pruning requests will be rejected [5]10486 1   11/03 06:58:47 ### Geting Low-DiskSpace Threshold From CS for engine-id 2410486 1   11/03 06:58:47 ### SidbStorInfo received...LowDisk Space  = 010486 1   11/03 06:58:47 ### Setting Low-DiskSpace Threshold 200MB as default10486 1   11/03 06:58:47 ### Low disk space threshold set to 200 MB10486 1   11/03 06:58:47 ### Successfully initialized the thread pool.10486 1   11/03 06:58:47 ### Initialized the CVD and SIDB sync mutex10486 1   11/03 06:58:47 ### N-Instancing Level set to [2]10486 1   11/03 06:58:47 ### Use transaction for commit records [true]10486 1   11/03 06:58:47 ### Going to fetch SIDB information from the commserve for engine id [24]10486 1   11/03 06:58:47 ### Fetched SIDB information from the commserve successfully.10486 1   11/03 06:58:47 ### Detected unclean shutdown of previous instance of sidb. State [1], Last modified [1288697159], Owner [17609]10486 1   11/03 06:58:47 ### Cannot start the DBProcessor object. return code = 53027

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 10:17 AM

    SDX,

    this error indicates the media agent hosting the DDB was shutdown while the SIDB2 process was running. Please check to event logs of the media agent to see if it was shutdown recently. I would also check to see if Windows Auto Updates is turned on and set to reboot. 

    let me know what you find.

    AaronA

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 10:35 AM

    Yep, agree. But the difference here is that normally you just select "Seal deduplication store" on that copy, and everything returns to normal, but in this case, the software just refused to create a new store. It complained that there were active volumes used by the dedup store. After opening a support ticket, the support representative found a reservation made by a job that was no longer running. This was only visible when looking directly in the database. The solution was to delete this row in the database. After that, the store could be sealed, and backups worked as normal again.

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 10:45 AM

    SDX,

    Thanks for the reponse. There is a tool in the base directory called CommServerdisasterRecoveryGui that has an option to kill all active jobs. if you run into this issue again try this out to see if the job and reservation can be terminated.

     

    AaronA

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 11:10 AM

    Here is a screenshot:

     

  • Re: Abnormal termination of deduplication service detected on MA. Please call in a support ticket
    Posted: 11-03-2010, 11:17 AM

    AaronA:

    SDX,

    Thanks for the reponse. There is a tool in the base directory called CommServerdisasterRecoveryGui that has an option to kill all active jobs. if you run into this issue again try this out to see if the job and reservation can be terminated.

     

    AaronA

     

    Just a side note here, do not run that if you have jobs running as they will be killed, do it when you have nothing else going on in the GUI job wise.

    Both of these issues point to a MA\store that was shut down or rebooted for some reason while SIDB was running. MA's cannot be rebooted or shut down if they are running the DDB unless it is done in a specific fashion or the store will have problems.

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy