On Thu, 2 Jan 2003, Philipp Gaschuetz wrote:
> As stated before, I was now running exim 4.10 without any problems. a retry db
> had been created automatically which currently has 2 entries.
> I downloaded, extracted and compiled 4.12 again. make install, and started
> exim, sent a message and: hurray, it worked!
> However, removing the retry db file, and restarting exim would end up with the
> same "failed to open DB" error again....
> when I copied the retry db created by 4.10 back into the db diretory
> everything worked again...
That is all rather weird!
> to me, it seems as if there is a problem in 4.12 creating new db files...
No problem in my testing, but of course that depends on your DB
library...
> WITH NO retry DB FILE
> =======================
> bash-2.05b# exim -d+all-memory -M 18UCXW-0001ad-00
> 22:27:07 6206 Exim version 4.12 uid=0 gid=0 pid=6206 D=fffeffff
> Probably Berkeley DB version 1.8x (native mode)
Oooh!! DB 1.8x is very, very old, and has been unsupported for quite a
long time now. I do still have a copy (over 6 years old), so I will
(when I get round to looking at this more deeply) compile a version of
Exim that uses it, and see if I can reproduce the problem.
> 22:27:07 6206 Delivery address list:
> 22:27:07 6206 someone@???
> 22:27:07 6206 locking /var/spool/exim/db/retry.lockfile
> 22:27:07 6206 locked /var/spool/exim/db/retry.lockfile
> 22:27:07 6206 /var/spool/exim/db/retry appears not to exist: trying to create
> 22:27:07 6206 ensuring /var/spool/exim/db/retry.lockfile is owned by exim
> 22:27:07 6206 ensuring /var/spool/exim/db/retry is owned by exim
> 22:27:07 6206 opened hints database /var/spool/exim/db/retry: flags=0
Hmm. That suggests it has created the db file, and successfully opened it.
But, later on...
> 22:27:07 6206 locking /var/spool/exim/db/retry.lockfile
> 22:27:07 6206 locked /var/spool/exim/db/retry.lockfile
> 22:27:07 6206 LOG: MAIN
> 22:27:07 6206 failed to open DB file /var/spool/exim/db/retry:
> Inappropriate file type or format
> 22:27:07 6206 retry database not available for updating
... for some reason it can't re-open it.
If I can reproduce this, I should be able to fix it. But if I can't
reproduce it, I'm afraid there's nothing I can do. I will look at it
sometime in the next week or two since you have a workaround. (Another
possibility is to upgrade to a later DB library, of course.)
Regards,
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
