Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Big problem after "out of disk space"

  1. #11
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Wow.
    I do not know how this thread got past us!!!
    I'm checking with the devs to see if they've made any headway repoing.
    trapanator,
    I want to personally extend my apologies for not noticing this sooner. It's amazing that all of the mods, and employees missed this, and I'm sorry.

    Have you made any head way?

    -john

  2. #12
    Join Date
    Oct 2006
    Posts
    78
    Rep Power
    9

    Default

    Quote Originally Posted by jholder View Post
    Wow.
    I do not know how this thread got past us!!!
    I'm checking with the devs to see if they've made any headway repoing.
    trapanator,
    I want to personally extend my apologies for not noticing this sooner. It's amazing that all of the mods, and employees missed this, and I'm sorry.

    Have you made any head way?

    -john
    I partially resolved this bug with this manner (without reinstalling Zimbra):

    sudo mv /[pathtozimbra/postfix/postmap /(identicalpath)/postmap.old
    sudo ln -sf /bin/true /(identicalpath)/postmap

    no 100% cpu anymore.

    I know, it's a stupid fix, but I cannot wait one month or two (or never) for this bug resolved...

  3. #13
    Join Date
    Apr 2007
    Location
    Germany
    Posts
    10
    Rep Power
    8

    Default

    We had the same issue as described here today as well. A stack trace showed that the file "/etc/__db.aliases.db" already existed and /etc/aliases.db did not.
    Oh well I just erased /etc/__db.aliases.db and everything seems to work fine now.

  4. #14
    Join Date
    Nov 2007
    Posts
    1
    Rep Power
    7

    Default

    Hey daceilo, your solution "is" the solution. Thank you very much.
    In fact, has been filed as a bug (relative to postfix).

    My scenario was the same as trepanator.

    Now working ok!.
    Thanks again.

  5. #15
    Join Date
    Jul 2009
    Posts
    15
    Rep Power
    6

    Default Problem still persists!

    Hello all, there is more than 2 years since last post, but here we go.

    I don't know if my problem is directly related to this bug, but on ZCS 6.0.6 we experienced the exact same symptoms, although we didn't check to see if it's related to the Berkeley DB problem.

    But the problem gone alway when we moved away the temporary *.db files, so we believe it's a similar problem.

    Particularly, after the problem started, we noticed some kind of loop of messages being sent from admin@mydomain to zimbra@mydomain, back and forth, in an endless loop, until we clared the temp files.

    Could you please check and advice?

    [zimbra@mail ~]$ zmcontrol -v

    Release 6.0.6_GA_2324.RHEL5_64_20100406133038 RHEL5_64 NETWORK edition.

    For now we still didn't open a support case, but we can do that if necessary.

  6. #16
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by celsowebber View Post
    Hello all, there is more than 2 years since last post, but here we go.

    I don't know if my problem is directly related to this bug, but on ZCS 6.0.6 we experienced the exact same symptoms, although we didn't check to see if it's related to the Berkeley DB problem.
    Have you had a disk full situation? I guess you can check if it's this bug by doing the repro steps in connect 8 from that bug report.

    Quote Originally Posted by celsowebber View Post
    the problem gone alway when we moved away the temporary *.db files, so we believe it's a similar problem.

    Particularly, after the problem started, we noticed some kind of loop of messages being sent from admin@mydomain to zimbra@mydomain, back and forth, in an endless loop, until we clared the temp files.

    Could you please check and advice?

    [zimbra@mail ~]$ zmcontrol -v

    Release 6.0.6_GA_2324.RHEL5_64_20100406133038 RHEL5_64 NETWORK edition.

    For now we still didn't open a support case, but we can do that if necessary.
    If you can reproduce this with the steps from the bug report then open a support case and mention that report. If you think it's a bdb problem then on a support case for that.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Similar Threads

  1. Amavis RAM Disk Setup - OK Now To Reimplement?
    By LMStone in forum Administrators
    Replies: 7
    Last Post: 10-12-2011, 08:26 PM
  2. Daily mail report always reports "No messages found"
    By McPringle in forum Installation
    Replies: 42
    Last Post: 06-13-2011, 08:57 AM
  3. Wiki and big problem
    By tdi in forum Administrators
    Replies: 1
    Last Post: 10-23-2006, 08:43 AM
  4. I found a big problem.
    By sshgz in forum Administrators
    Replies: 9
    Last Post: 08-10-2006, 06:14 PM
  5. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 10:11 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
  •