ZX Backup Smart Scan Failing
Results 1 to 8 of 8

Thread: ZX Backup Smart Scan Failing

  1. #1
    Active Member
    Join Date
    Jun 2014
    Posts
    4

    ZX Backup Smart Scan Failing

    This is the error I get whenever I try to do a smart scan

    This is an automated notification from ZxBackup about Smart Scan.

    Operation Smart Scan failed.

    Operation Id: 0194c861-18e3-4092-a45e-580dd35ebe6a
    Operation Host: mail.nichework.com

    Operation requested by: basil@everybody.org

    ZeXtras Version: 1.8.16
    ZeXtras commit: 220a21b3d79858608ac2cb7b6f35a86de3baedc6
    Zimbra version: 8.0.7_GA_6021 20140408123908 20140408-1242 FOSS

    - exception -
    com.zextras.lib.Error.OperationBlockingError: no such folder id: 11
    at com.zextras.op.backup.ZESmartScanOperation.doOpera tion ( ZESmartScanOperation.java:260 )
    at com.zextras.op.ZEOperation.exec ( ZEOperation.java:720 )
    at com.zextras.backup.services.BackupThread.execOpera tion ( BackupThread.java:253 )
    at com.zextras.backup.services.BackupThread.run ( BackupThread.java:126 )
    at java.lang.Thread.run ( Thread.java:744 )
    Caused by: com.zimbra.cs.mailbox.MailServiceException$NoSuchI temException: no such folder id: 11
    ExceptionId:ZxBackup Thread:1402584900715:82323ec26fe26996
    Code:mail.NO_SUCH_FOLDER ArgitemId, IID, "11")
    at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH _FOLDER ( MailServiceException.java:195 )
    at com.zimbra.cs.mailbox.MailItem.noSuchItem ( MailItem.java:1640 )
    at com.zimbra.cs.mailbox.Mailbox.getItemById ( Mailbox.java:2510 )
    at com.zimbra.cs.mailbox.Mailbox.getItemById ( Mailbox.java:2469 )
    at com.zimbra.cs.mailbox.Mailbox.getFolderById ( Mailbox.java:3511 )
    at com.zimbra.cs.mailbox.Mailbox.getModifiedFolders ( Mailbox.java:3274 )
    at com.zimbra.cs.mailbox.Mailbox.getModifiedFolders ( Mailbox.java:3260 )
    at com.zextras.zal.ZEMailbox.getModifiedFolders ( ZEMailbox.java:327 )
    at com.zextras.op.backup.ZEScanOperation.fastItemsSca n ( ZEScanOperation.java:321 )
    at com.zextras.op.backup.ZEScanOperation.doAccountSca n ( ZEScanOperation.java:441 )
    at com.zextras.op.backup.ZEScanOperation.doDomainScan ( ZEScanOperation.java:153 )
    at com.zextras.op.backup.ZESmartScanOperation.doOpera tion ( ZESmartScanOperation.java:255 )
    at com.zextras.op.ZEOperation.exec ( ZEOperation.java:720 )
    at com.zextras.backup.services.BackupThread.execOpera tion ( BackupThread.java:253 )
    at com.zextras.backup.services.BackupThread.run ( BackupThread.java:126 )
    at java.lang.Thread.run ( Thread.java:744 )


    - debug info -
    -- parameters --
    deepScan = false
    dataPath = /opt/zimbra/store2/zextrasbackup
    OpStartTime = 1402584880455
    notificationeMails = basil@everybody.org
    origin = SOAP
    canBeFirstScan = false
    -- context --
    numBackuppedItems = 3
    notificationMails = basil@everybody.org
    numCheckedAccounts = 61
    numPurgedItems = 0
    lastAccountSequence = 1299
    lastAccountId = 7d968d2b-efa9-4b01-99bd-f4a15b7008bd
    failed = 1
    numBackuppedAccounts = 159
    numCheckedItems = 3
    numDeletedItems = 0
    numActiveBackuppedAccounts = 61
    numNewItems = 1
    maxTrivialIOAllowed = 1000
    numPurgedFiles = 0
    numDeletedAccounts = 0
    numPurgedAccounts = 0
    numUpItems = 0
    totItems = 31
    items4s = 3
    completed = 1
    numTotalAccounts = 119
    numContentFiles = 1
    Last progress info:
    --
    Account scanned: 60/119
    Account updated/new: 0/0
    Account skipped(disabled by COS): 0
    Item scanned: 3
    Item updated/new/unique: 0/1/1

  2. #2
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,364
    Hello Roran01,
    welcome to the forums!

    The error you report means that one of your accounts (check the lines of the mailbox.log file preceeding the error to see which one) is missing a mandatory system folder, and this causes the SmartScan to fail.

    Honestly, it's the first time that I've seen something like this happening... The cause is most likely a DB corruption, did your server experience any crash lately or any issue in general, especially during the creation of the affected mailbox? Did you manually edit Zimbra's Database or ran any unofficial script that might have done so?

    I'll discuss your case with the team in order to help you, please give us as many info as possible about what might have happened...

    Have a nice day,
    Cine
    the ZeXtras Team

  3. #3
    Active Member
    Join Date
    Jun 2014
    Posts
    4
    We did have a hacker start using our server as a spambot, and that probably doesn't help. We are working on that though. Are there any ways to fix this?

  4. #4
    CTO ZeXtras Employee d0s0n's Avatar
    Join Date
    Apr 2011
    Posts
    570
    Hi Roran01,

    I can suggest you to rename that particular mailbox, hide it in GAL and keep it in "mainteinance" status to exclude it from the Scan operation.

    Keep me posted.

    D0s0n
    ZeXtras Website # ZeXtras Wiki # ZeXtras Store

    Head of ZeXtras System Administrators

  5. #5
    Active Member
    Join Date
    Jun 2014
    Posts
    4
    Quote Originally Posted by d0s0n View Post
    Hi Roran01,

    I can suggest you to rename that particular mailbox, hide it in GAL and keep it in "mainteinance" status to exclude it from the Scan operation.

    Keep me posted.

    D0s0n
    How do I find what mailbox that is? I can't see anything in the error logs, and there was no obvious notification of "This is corrupted"

  6. #6
    CTO ZeXtras Employee d0s0n's Avatar
    Join Date
    Apr 2011
    Posts
    570
    As reported on error notification, your "broken" mailbox is:
    ...
    lastAccountId = 7d968d2b-efa9-4b01-99bd-f4a15b7008bd
    ...
    So you can find the account name by using "zmprov" command:
    Code:
    zmprov ga 7d968d2b-efa9-4b01-99bd-f4a15b7008bd
    D0s0n
    ZeXtras Website # ZeXtras Wiki # ZeXtras Store

    Head of ZeXtras System Administrators

  7. #7
    Active Member
    Join Date
    Jun 2014
    Posts
    4
    There seems to be a bug that, when Zextras comes across a closed account, it errors out, as it was in this case. After deleting the problematic account, the scan works.

  8. #8
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,364
    Hello Roran01!

    The status of the account is completely unrelated to this issue...
    D0s_0n suggested to set it to "Maintenance" so that the affected account would be skipped by any *scan operation while investigating in order not to impair the backup system, but any other account status is treated exactly the same way as "open".

    Unfortunately now that the account has been deleted we can't help that much in finding the cause of the missing system folder... I hate to sound pessimistic, but I strongly suggest to keep an eye on your server's performances and logs - the deleted system folder might have been caused by an unfortunate event but if this is not the case this might happen again...

    Have a nice day,
    Cine
    the ZeXtras Team

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •