Big problem after "out of disk space"

[jholder]

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

[trapanator]

Originally Posted by jholder

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...

[hannes]

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.

[jfgarcia]

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.