Wonderful, thank you Paul, and not just for this, but for all the great
work you are doing on DBMail.
Matt
Paul J Stevens wrote:
I ran into it myself recently, and concluded that there's a bug in the
pool code which doesn't cleanup when a fork fails.
basically what happens is that after forking, a child process tries to
register in the scoreboard. This will fail if there are too many
children. However, upon failure to register the child exists (which is
ok), but this child is not 'wait'-ed upon (which is not good). This lead
to zombies. I've fixed in svn-trunk (though I haven't validated the
fix). It this works out, the fix applies easily to 2.0 since the pool
code is the same for 2.0 and 2.1. And if it does, I'll release 2.0.11.
Matthew T. O'Connor wrote:
Could you expound on that? I have seen the same problem, DBMail 2.0.9,
Fedora Core 2, PostgreSQL database backend. One thing I think I noticed
is that the problem happened more frequently when I set IMAPs NCHILDREN
to a small number like 5, that caused a lot of problems, I bumped it
back to 30 and the problem happens less often.
In my experience this is the biggest problem with DBMail, this is also
the main reason I looking forward to 2.2 since I'll be able to use
xinetd to manage connections. Any chance of that feature being
backported to the 2.0.x branch?
You mean non-forking in 2.0? It's not difficult, but I'm not going to do
it. My time is too precious, and I rather spent it at getting 2.2. ready.
Matt
Paul J Stevens wrote:
This is a known issue that is not 2.0.10 specific.
[EMAIL PROTECTED] wrote:
Dev-monsters,
Not reproducible on demand so I really can't call/submit it as a bug but
it's serious enough to post to the dev list in case others are having
this problem.
Approximately 2 days after upgrading from 2.0.9/8 (forgot which one) to
2.0.10, my mail server for whatever reason had over 3 thousand
dbmail-imapd proccesses (the dbmail.conf specified 20 max) causing the
system to run out of memory, swap. Systems is Centos 4.2 with Mysql
4.1.18.
This was 2 days ago and haven't seen the IMAPD issue come up yet.
However, today, 48 hours later, dbmail-pop3d has 4 zombies.
I'm the only user of IMAP access on the server though several boxes have
30K+ messages.
Don't want to sound the life-boat alarm but just a warning bell to watch
this if others experience similar issues after upgrade.
Xing
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
