On Wed, Jun 15, 2005 at 11:36:38PM +0200, Sylvain LE GALL wrote: > I have encounter a problem with exim since 2 weeks or so. I am using the > sarge version. > > >From time to time, there is an exim4 process that eats 100% of the CPU > for hours (it doesn't stop until i kill it with a "kill -9" signal). The > mainlog keep telling me that another process is handling a lockfile. > > Here is what i think is relevant concerning the bug : > > All the error begin here (first occurence of the word "lock"). > > 2005-06-15 15:31:32 1DiXzP-0003Z4-Rr <= > [EMAIL PROTECTED] > H=localhost.gallu.homelinux.org (localhost) [127.0.0.1] P=esmtp S=4722 > [EMAIL PROTECTED] > 2005-06-15 15:31:32 1DiXzP-0003Z4-Rr => gildor <[EMAIL PROTECTED]> > R=ldap_user T=maildrop_ldap_user > 2005-06-15 15:31:32 1DiXzP-0003Z4-Rr Completed > 2005-06-15 15:32:44 Start queue run: pid=13737 > 2005-06-15 15:32:44 1DiXmf-0003YT-LQ Spool file is locked (another > process is handling this message) > 2005-06-15 15:32:44 End queue run: pid=13737 > 2005-06-15 15:42:49 1DiXmf-0003YT-LQ TLS error on connection to > smtp-vip.easynet.fr [212.180.1.59] (gnutls_handshake): A record packet > with illegal version was received. > [...] > > And then for every message : > 2005-06-15 15:47:54 1DiYEI-0003Zb-FJ Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:55 1DiYEJ-0003Zb-3o Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:55 1DiYEJ-0003Zb-LM Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:56 1DiYEK-0003Zb-6k Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:56 1DiYEK-0003Zb-OO Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:57 1DiYEL-0003Zb-9o Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:47:57 1DiYEL-0003Zb-RS Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:48:55 1DiYEI-0003Zb-FJ Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > 2005-06-15 15:48:55 1DiYEI-0003Zb-FJ => gildor <[EMAIL PROTECTED]> > R=ldap_user T=maildrop_ldap_user > 2005-06-15 15:48:55 1DiYEI-0003Zb-FJ Completed > 2005-06-15 15:48:55 1DiYEJ-0003Zb-3o Failed to get write lock for > /var/spool/exim4/db/retry.lockfile: timed out > [...] > 2005-06-15 16:02:44 Start queue run: pid=13807 > 2005-06-15 16:02:44 1DiYTF-0003ad-89 Spool file is locked (another > process is handling this message) > 2005-06-15 16:02:44 1DiYTE-0003ad-Ja Spool file is locked (another > process is handling this message) > 2005-06-15 16:02:44 1DiXmf-0003YT-LQ Spool file is locked (another > process is handling this message)
Can you try moving the retry database away, and probably see with -d what the delivery attempt tries to do. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
