Philip Hazel said once upon a time:
>
>[Not copied to list as it seems rather specifically technical.]
>
>On Fri, 14 Nov 1997, Pete Ashdown wrote:
>
>> >> Output from exim_tidydb:
>> >> Exim wait-remote_smtp database in spool /var/spool/mqueue/exim
>> >> Failed to get write lock for /var/spool/mqueue/exim/db/wait-remote_smtp: Interrupted system call
>
>> Well, since I upgraded to 1.73, it happens on a daily basis. Which causes
>> outgoing mail to slow to a crawl. I eventually have to kill all the exims,
>> remove the wait-remote_smtp database and start over, only to have to do it
>> again the next day.
>
>That is worrying, though nobody else has reported anything like it.
>How often are you running exim_tidydb? You only need to do it
>infrequently. In fact, I run it only every few weeks, when I remember,
>but then this isn't a terribly high-use system.
I'm running it only to see if the database is stuck in a lock.
>One think you might consider is trying out the testing release of Exim
>which is in the Testing subdirectory of the ftp site, because in that I
>have re-written the locking code for databases to lock on an entirely
>separate file. This gets round a number of problems, though I can't see
>how it could actually relate to this one. However, the testing release
>is essentially alpha code.
This really doesn't make me feel all that much better.
>I would like very much to find the explanation for this quickly so that
>if anything needs doing to the next release I can get it done. Is there
>any way on your system of discovering which process is holding the lock
>on a file? I'm afraid I'm not enough of a Unix guru to be able to
>suggest something instantly. However, one thing you could certainly do
>is to run exiwhat to find out which exim processes are running and what
>they are doing. Maybe some process is getting into a stuck state while
>holding the lock.
Exiwhat shows several processes delivering. Nothing looks like it may be
stuck. Is there anything I can do to "unlock" the database rather than
delete it?
--
*** Exim information can be found at
http://www.exim.org/ ***
