[Kroupware] kolab hangs periodically
Nicolas Huillard
nhuillard at ghs.fr
Mon Nov 17 11:38:28 CET 2003
This may be the (dead-)locking problem in imapd. Read my previous post
about that.
When imapd components start to dead-lock mutually, they all eat memory,
and stack up. This could lead to memory exhaustion (even with 2GB,
specially with a large number of users).
Stephan Buys sent me imapd 2.1.15 that I didn't install yet. This WE, I
saw a rush of 6000 mails in a few minutes (bad alerting), that blocked
lmtpd processes and consumed 200MB+ memory. The mailq flushed quickly
and everything was good after a kolab restart.
NH
d4rke1f at katamail.com wrote:
> Hi,
> I am running a kolab installation (1.0.8 or something) with a large user base (3000+ users).
> Every 5 days or so, I get a segmentation fault on Apache, and the imap services get stuck (ie no banner is received when telnetting).
> in the error log I can see something like this:
> Sun Nov 9 18:46:50 2003] [notice] child pid 15150 exit signal Segmentation fault (11)
> or I get some Apache's out of memory message.
>
> Kolab is running on a smtp server with 2Gigs of ram.
> kernel 2.4.20-20.7smp
> Can someone please help me out?
> Thanks in advance.
> _______________________________________________
> Kroupware mailing list
> Kroupware at mail.kde.org
> https://mail.kde.org/mailman/listinfo/kroupware
More information about the Kroupware
mailing list