Results 1 to 4 of 4

Thread: User mailbox crashed

  1. #1
    Chareos is offline New Member
    Join Date
    Aug 2010
    Posts
    4
    Rep Power
    5

    Default User mailbox crashed

    Hi,

    yesterday, my zimbra service mailboxdctl crashed throughout the day without reason.

    This morning, a user say to me, he don't receive any mail since 2 days. He use Outlook to connect her mailbox with IMAP. When i'm trying to connect to his mailbox in webmail, i can't , and my service shutdown. When i'm trying to configure account in the administrative web interface, i have an error like :

    zaaccountviewcontroller.prototype._setview
    And my service shutdown again.

    I have try to see the account info with the command line:

    zmprov getMailboxInfo "mail_adresse_account"
    I received the following error

    [] INFO: I/O exception (org.apache.commons.httpclient.NoHttpResponseExcep tion) caught when processing request: The server zimbra.monserveur.com failed to respond
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: zimbra.monserveur.com) (cause: java.net.ConnectException Connection refused)
    And my service shutdown again.

    How can I repare this mailbox?

    thanks a lot

    (please excuse my bad english)

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,581
    Rep Power
    57

    Default

    Quote Originally Posted by Chareos View Post
    yesterday, my zimbra service mailboxdctl crashed throughout the day without reason.
    There's usually somethingin the log files, did you look at them? What exactly do you mean by "crashed"?

    You should always post details of which ZCS version and release you're using (and update your forum profile with the information, post the output of the following:

    Code:
    zmcontrol -v
    Are all the Zimbra services running? Have you restarted ZCS?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Chareos is offline New Member
    Join Date
    Aug 2010
    Posts
    4
    Rep Power
    5

    Default

    Sorry I've forgotten to post my Zimbra version....
    Version 6.0.1_GA_1816.SuSEES10.FOSS 11
    All the Zimbra services running, but when I access to this user's mailbox, the mailboxdctl service crash down

  4. #4
    Chareos is offline New Member
    Join Date
    Aug 2010
    Posts
    4
    Rep Power
    5

    Default

    for information, i seeing than i have one disk from my RAID 5 is damaged, i'll replace this one tomorrow.
    I found these error messages in my mysql_error.log

    130702 10:28:36 InnoDB: Page checksum 2291541643, prior-to-4.0.14-form checksum 3463440453
    InnoDB: stored checksum 3918700677, prior-to-4.0.14-form stored checksum 2987591815
    InnoDB: Page lsn 4 692297742, low 4 bytes of lsn at page end 692297742
    InnoDB: Page number (if stored to page already) 209,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 360
    InnoDB: Page may be an index page where index id is 0 959
    InnoDB: (index PRIMARY of table mboxgroup26/mail_item)
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 209.
    InnoDB: You may have to recover from a backup.
    InnoDB: It is also possible that your operating
    InnoDB: system has corrupted its own file cache
    InnoDB: and rebooting your computer removes the
    InnoDB: error.
    InnoDB: If the corrupt page is an index page
    InnoDB: you can also try to fix the corruption
    InnoDB: by dumping, dropping, and reimporting
    InnoDB: the corrupt table. You can use CHECK
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: See also InnoDB: http://dev.mysql.com...g-recovery.html
    130702 10:28:36 InnoDB: Page checksum 2291541643, prior-to-4.0.14-form checksum 3463440453
    InnoDB: stored checksum 3918700677, prior-to-4.0.14-form stored checksum 2987591815
    InnoDB: Page lsn 4 692297742, low 4 bytes of lsn at page end 692297742
    InnoDB: Page number (if stored to page already) 209,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 360
    InnoDB: Page may be an index page where index id is 0 959
    InnoDB: (index PRIMARY of table mboxgroup26/mail_item)
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 209.
    InnoDB: You may have to recover from a backup.
    InnoDB: It is also possible that your operating
    InnoDB: system has corrupted its own file cache
    InnoDB: and rebooting your computer removes the
    InnoDB: error.
    InnoDB: If the corrupt page is an index page
    InnoDB: you can also try to fix the corruption
    InnoDB: by dumping, dropping, and reimporting
    InnoDB: the corrupt table. You can use CHECK
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: by dumping, dropping, and reimporting
    InnoDB: the corrupt table. You can use CHECK
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: See also InnoDB: http://dev.mysql.com...g-recovery.html
    130702 10:28:36 InnoDB: Page checksum 2291541643, prior-to-4.0.14-form checksum 3463440453
    InnoDB: stored checksum 3918700677, prior-to-4.0.14-form stored checksum 2987591815
    InnoDB: Page lsn 4 692297742, low 4 bytes of lsn at page end 692297742
    InnoDB: Page number (if stored to page already) 209,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 360
    InnoDB: Page may be an index page where index id is 0 959
    InnoDB: (index PRIMARY of table mboxgroup26/mail_item)
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 209.
    InnoDB: You may have to recover from a backup.
    InnoDB: It is also possible that your operating
    InnoDB: system has corrupted its own file cache
    InnoDB: and rebooting your computer removes the
    InnoDB: error.
    InnoDB: If the corrupt page is an index page
    InnoDB: you can also try to fix the corruption
    InnoDB: See also InnoDB: http://dev.mysql.com...g-recovery.html
    InnoDB: about forcing recovery.
    InnoDB: Ending processing because of a corrupt database page.
    my DB seem defective.

    I'll waiting than my new disk arrived for repair my RAID system and see if my DB will be repaired
    Chareos

    Version 6.0.1_GA_1816.SuSEES10.FOSS 11

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. User mailbox
    By ramlang in forum Administrators
    Replies: 3
    Last Post: 02-05-2013, 02:02 PM
  2. User mailbox
    By ramlang in forum Installation
    Replies: 1
    Last Post: 02-04-2013, 04:00 AM
  3. Replies: 1
    Last Post: 07-01-2012, 07:46 AM
  4. Replies: 0
    Last Post: 07-21-2011, 06:44 AM
  5. user mailbox migrate
    By amitbiswas in forum Migration
    Replies: 0
    Last Post: 04-12-2009, 05:02 PM

Posting Permissions

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