Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-06-19 Thread Joachim Wieland
Hi, (breaking thread on purpose because the mail I quote is quite old already) On Tue, May 02, 2006 at 10:02:27AM +0100, Philip Hazel wrote: I would argue that there is a bug in BDB in that it shouldn't loop, whatever data file you throw at it. Just for the records: I have just encountered

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-05-02 Thread Philip Hazel
On Fri, 28 Apr 2006, Michel Meyers wrote: So there you have it: deleting one silly little file fixed my months old issue (if only I had tried that before!). If only I'd thought to suggest it before! We have had crashes in the past, but not, I think, CPU loops. There are two possible causes:

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-05-01 Thread Michel Meyers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Hazel wrote: On Fri, 28 Apr 2006, Michel Meyers wrote: I installed the package that Andreas supplied: http://downhill.aus.cc/debian/misc/exim4-daemon-heavy_4.61-1.0.0.debug_i386.deb (md5: 1adecd15e58afe4f06d35b41bbda8871) The binary

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-05-01 Thread Greg Folkert
On Fri, 2006-04-28 at 18:24 +0200, Michel Meyers wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Hazel wrote: On Fri, 28 Apr 2006, Michel Meyers wrote: If that backtrace is to be trusted, Exim's function dbfn_open() has called the function __db_pg_free_read_4002() from the

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-28 Thread Philip Hazel
On Thu, 27 Apr 2006, Michel Meyers wrote: Then I tried gcore: gcore -o /var/core 30611 That dumped a file which I gzipped. I don't know whether my previous mail went through (might've been rejected with the big file), so just to be sure I uploaded it to Rapidshare (I don't have any fast

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-28 Thread Philip Hazel
On Fri, 28 Apr 2006, Michel Meyers wrote: I installed the package that Andreas supplied: http://downhill.aus.cc/debian/misc/exim4-daemon-heavy_4.61-1.0.0.debug_i386.deb (md5: 1adecd15e58afe4f06d35b41bbda8871) The binary should be in there as well. (you can extract it with ar if you don't

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-27 Thread Michel Meyers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Byng-Maddick wrote: On Wed, Apr 26, 2006 at 02:03:39PM +0200, Michel Meyers wrote: Matthew Byng-Maddick wrote: On Wed, Apr 26, 2006 at 09:39:15AM +0100, Philip Hazel wrote: Ah! I don't know much about mailscanner. Am I right in thinking it

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-27 Thread Michel Meyers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Metzler wrote: On 2006-04-26 Michel Meyers [EMAIL PROTECTED] wrote: Philip Hazel wrote: On Tue, 25 Apr 2006, Michel Meyers wrote: If there's anything I could run to debug it, please let me know (as I can reproduce the problem pretty

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-26 Thread Michel Meyers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Hazel wrote: On Tue, 25 Apr 2006, Michel Meyers wrote: If there's anything I could run to debug it, please let me know (as I can reproduce the problem pretty easily here). Perhaps compiling Exim with -g and taking a core dump of a stuck

Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout

2006-04-26 Thread Andreas Metzler
On 2006-04-26 Michel Meyers [EMAIL PROTECTED] wrote: Philip Hazel wrote: On Tue, 25 Apr 2006, Michel Meyers wrote: If there's anything I could run to debug it, please let me know (as I can reproduce the problem pretty easily here). Perhaps compiling Exim with -g and taking a core dump of a