> On Sat, Oct 07, 2000 at 01:21:22PM -0700, kmself@ix.netcom.com wrote:
> > On Sat, Oct 07, 2000 at 05:34:36PM +0200, Frederik ([EMAIL PROTECTED])
> > wrote:
> > > Subject: Cron <[EMAIL PROTECTED]> test -e /usr/sbin/anacron || run-parts
> > > --report
> > > /etc/cron.daily
> > >
> > > /etc/cron.daily/exim:
> > > Exim retry database in spool /var/spool/exim
> > > Failed to open database file retry: Invalid argument
> > > run-parts: /etc/cron.daily/exim exited with return code 1
> > >
> > > I get this cron message ever since I upgraded exim last week
> > > (unstable). Do I have to be worried? Mail gets delivered correctly, I
> > > think.
> >
> > You may need a glibc/libdb fix. This broke last week. Exim was among
> > the broken apps.
>
> How does one make that fix? I've kept everything dist-upgraded (in
> Woody) and I am still receiving the same message as the original poster.
>
------- Forwarded Message
Return-Path: [EMAIL PROTECTED]
Delivery-Date: Wed Oct 04 01:40:22 2000
Envelope-to: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=mail)
by rakefet with esmtp (Exim 3.16 #1 (Debian))
id 13gajW-0007H2-00
for <[EMAIL PROTECTED]>; Wed, 04 Oct 2000 01:40:22 +0300
Received: from mail.bezeqint.net [192.115.106.21]
by localhost with POP3 (fetchmail-5.5.0)
for [EMAIL PROTECTED] (single-drop); Wed, 04 Oct 2000 01:40:22 +0300
(IDT)
Received: from anchor-post-32.mail.demon.net by mail.bezeqint.net
(Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
with ESMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED];
Tue, 3 Oct 2000 23:04:08 +0300 (GMT)
Received: from aziraphale.demon.co.uk ([194.222.242.160])
by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1)
id 13gYKT-000Jil-0W; Tue, 03 Oct 2000 21:06:21 +0100
Received: from mark by aziraphale.demon.co.uk with local
(Exim 3.16 #1 (Debian)) id 13gXvy-0005rS-00; Tue, 03 Oct 2000 20:41:02 +0100
Date: Tue, 03 Oct 2000 20:41:02 +0100
From: Mark Baker <[EMAIL PROTECTED]>
Subject: Re: Bug#73048: exim: /etc/cron.daily/exim does not work: Failed to
open database file retry: Invalid argument
In-reply-to: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on Tue,
Oct 03, 2000 at 02:51:29PM +0300
To: Shaul Karl <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Message-id: <[EMAIL PROTECTED]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
References: <[EMAIL PROTECTED]>
On Tue, Oct 03, 2000 at 02:51:29PM +0300, Shaul Karl wrote:
> [14:41:27 /tmp]# exim_tidydb /var/spool/exim retry
> Exim retry database in spool /var/spool/exim
> Failed to open database file retry: Invalid argument
When Ben did a non-maintainer upload of exim recently he switched to using
libdb2 instead of libdb 1.85, and the files aren't compatible. Unfortunately
he didn't notice the problem, and nor did I when I subsequently uploaded an
exim package.
I'll fix this and upload a fixed package.
In the meantime, if you delete the files in /var/spool/exim/db, it will
create new ones using libdb2 which will work, but you'll have to do it again
when you upgrade to a later version where I've gone back to 1.85.
(If it was only those hints databases I'd change to libdb2 permanently and
have the postinst or something delete the existing databases, but it's
possible for users to use db files for other things, which a) I wouldn't
know about unless I parsed the config file, and b) they might not want
deleting)
------- End of Forwarded Message
> --
> Tom
> "Nothing is so firmly believed as what is least known."
> -Montaigne
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
--
Shaul Karl <[EMAIL PROTECTED]>
--
Shaul Karl <[EMAIL PROTECTED]>
