Autor: W B Hacker
Datum:
To: exim-users
Betreff: Re: [exim] Failed to get write lock
for/var/spool/exim/db/wait-remote_smtp.lockfile: timed out
Cengiz Yazgan wrote:
> I am getting this error message
>
> Failed to get write lock for /var/spool/exim/db/wait-remote_smtp.lockfile:
> timed out
>
> What does it mean
>
> root@yaren [/var/log]# exim -bV
> Exim version 4.52 #1 built 28-Jul-2005 08:17:04
> Copyright (c) University of Cambridge 2005
> Berkeley DB: Sleepycat Software: Berkeley DB 4.1.25: (August 21, 2003)
> Support for: iconv() PAM Perl OpenSSL Content_Scanning Old_Demime
> Lookups: lsearch wildlsearch nwildlsearch iplsearch dbm dbmnz
> Authenticators: cram_md5 plaintext spa
> Routers: accept dnslookup ipliteral manualroute queryprogram redirect
> Transports: appendfile autoreply pipe smtp
> Configuration file is /etc/exim.conf
>
>
>
> Best regards
>
>
>
>
> Cengiz YAZGAN
When, (startup, per-connection, per-message, per queue run?)
where (what log?),
and how often (per child spawn / connection / queue-run?)
...are you getting that message?
Does /var/spool/exim/db and below 'belong' to the UID:GID that
Exim is using: at the time of attempt? Always? (ever?)
Do the perms permit Exim UID:GID to write there?
Is another user or process or another Exim 'child' holding open
the same file?
Bill
