Home > Failed To > Failed To Get Write Lock For /var/spool/exim/db/retry.lockfile

Failed To Get Write Lock For /var/spool/exim/db/retry.lockfile

user = Debian-exim group = Debian-exim log_output = true return_fail_output = true return_path_add = false message_prefix = message_suffix = This could be where the second 'cannot get lock' message gets generated. Details of the error are\n\ reported below. No, create an account now. You may have to do special things in order to get a dump of a setuid process such as Exim - seek advice from Debian experts. have a peek here

So far, there's no reason to care or touch the lockfile (except for whatever Exim does with it of course). 3. I'm grasping at straws here. /var is ext3 >> 2006-04-20 21:06:35 1FWeOO-000396-DP Spool file is locked (another >> process is handling this message) > > At least *some* locking is working. Copy sent to Exim4 Maintainers . No. https://bugs.debian.org/360696

I had forgotten that it was only at 4.12 that I modified -bV to output more details about what the binary contained. It really is very straightforward: sigalrm_seen = FALSE; alarm(EXIMDB_LOCK_TIMEOUT); rc = fcntl(dbblock->lockfd, F_SETLKW, &lock_data); alarm(0); if (sigalrm_seen) errno = ETIMEDOUT; if (rc < 0) { log_write(0, LOG_MAIN, "Failed to get %s Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers.

Am I right in thinking it looks at Exim's spool files itself? Quote: The given log had this: 2006-04-04 09:13:48 1FQfhL-00035E-Ay Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out 2006-04-04 09:14:48 1FQfhL-00035E-Ay Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out which The fix below should resolve these errors 2013-12-22 03:16:00 Failed to get write lock for /var/spool/exim/db/ratelimit.lockfile: timed out
2013-12-22 03:16:00 H=[190.235.210.104]:13468 temporarily rejected connection in "connect" ACL: ratelimit database not you'll just lose some ratelimits and caching that would have expired soon anyways) rm -fv /var/spool/exim/db/* #2 cPanelNick, Jan 22, 2008 sneader Well-Known Member Joined: Aug 21, 2003 Messages: 1,132

Message #10 received at [email protected] (full text, mbox, reply): From: Marc Haber To: Michel Meyers , [email protected], [email protected] Cc: Marc Haber Subject: Re: Bug#360696: exim4-daemon-heavy: Failed to get write Full text and rfc822 format available. Rodrigo Prieto: Hi, thanks for the explanation , it was really useful for me. https://www.servernoobs.com/exim-error-ratelimit-database-not-available/ While the stuck process is there, the mainlog keeps mentioning messages like these: 2006-04-04 09:13:33 1FQfgD-0002kv-EZ Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out 2006-04-04 09:13:48 1FQfhL-00035E-Ay Failed to get

Graeme This message was posted to the following mailing lists:Exim-usersMailing List Info | Nearby Messages[exim] Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed outRe: [exim] Failed to get write lock for I don't know much about mailscanner. This should just exit without updating the retry database. (And I can't believe it's looping in the log-writing function, though anything is possible...) > 2006-04-25 21:30:58 1FYTFD-0002aU-BC <= [email protected] U=Debian-exim > Sorry!

I presume that you have /var/spool/exim on a local disc? https://lists.exim.org/lurker/message/20150321.092810.f0031f8c.en.html thanks, cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by ould you also answer Phil's questions, i.e. If it is in a loop, that should indicate where the loop is.

I guess you mean libdb4.2 (package rev 4.2.52-23.1 is installed)? navigate here Therefore, if there is a lot of updating going on, so much so that there is lock contention, it must mean that there are a lot of temporary delivery failures happening. The stuck message doesn't seem to appear in the log at all any more, unless I try to remove it through eximon in which case I get: 2006-04-20 21:06:35 1FWeOO-000396-DP Spool But of course I was using release 4.61, not 4.60.

Message #49 received at [email protected] (full text, mbox, reply): From: Andreas Metzler To: Michel Meyers , [email protected] Subject: Re: Bug#360696: exim4-daemon-heavy: Failed to get write lock for retry.lockfile / exim Hmm. If there is any significant interest, I willsetup a mailing list for interested users.RegardsIan---------------------------------------------------------------------Ian Forbes ZSDhttp://www.zsd.co.zaOffice: +27 21 683-1388 Fax: +27 21 674-1106Snail Mail: P.O. Check This Out I use amavisd-new and spamassassin (spamc) with the configuration I described in my previous mail.

Information stored: Bug#360696; Package exim4-daemon-heavy. Ah! Please try again later.

Full text and rfc822 format available.

Cc: exim-users [at] exim Subject: Re: [Exim] /var/spool/exim/db/retry.lockfile problems On Tue, 11 Mar 2003, Smith, A.D. Pascal Schonewille: I have tried it, when i use service ondemand start it works good. Full text and rfc822 format available. Acknowledgement sent to Andreas Metzler : Extra info received and forwarded to list.

I use greylistd, >> amavis-new and spamassassin on my end and the server hosts multiple >> domains (lookups done through static alias files for those). > > Is TLS in use? I tried to simulate this problem by patching the code to pretend it had failed to get a lock when trying to update the retry database while tidying up after a I am currently queuing mail, any help would be very greatly appreciated, Alex ads13 at leicester Mar11,2003,4:32AM Post #2 of 8 (1769 views) Permalink RE: /var/spool/exim/db/retry.lockfile problems [In reply to] # exim -bP this contact form Full text and rfc822 format available.

Copy sent to Exim4 Maintainers . Are you using MailScanner, No, I am not using MailScanner. Full text and rfc822 format available. Message #54 received at [email protected] (full text, mbox, reply): From: Michel Meyers To: Andreas Metzler Cc: Michel Meyers , [email protected] Subject: Re: Bug#360696: exim4-daemon-heavy: Failed to get write lock

Full text and rfc822 format available. I also found other reports scattered over the web with seemingly similar symptoms but I can't recall the references to those right now. If so, then indeed it may have something to do with this. -- Philip Hazel University of Cambridge Computing Service Get the Exim 4 book: http://www.uit.co.uk/exim-book -- ## List details at There were some changes in that area, butnothing that seems related.

I'm trying to do t... Which is why it needs to know (and care) about the spool file format.