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.

[celsowebber]

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.

[phoenix]

Originally Posted by celsowebber

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.

Originally Posted by celsowebber

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.