On Wed, Nov 15, 2006 at 09:09:10PM +0100, Bill Allombert wrote:
> On Mon, Oct 02, 2006 at 04:19:17PM +0200, Marc Haber wrote:
> > On Wed, Sep 27, 2006 at 10:56:09AM +0200, Bill Allombert wrote:
> > > I never experienced the bug with gzip_dbout=no for some months now, so
> > > I am confident this fi
On Mon, Oct 02, 2006 at 04:19:17PM +0200, Marc Haber wrote:
> On Wed, Sep 27, 2006 at 10:56:09AM +0200, Bill Allombert wrote:
> > I never experienced the bug with gzip_dbout=no for some months now, so
> > I am confident this fixed it.
>
> Very well, thanks. Can you set dzip_dbout again to verify t
Hi,
On Wed, Oct 04, 2006 at 12:28:37PM +0200, Richard van den Berg wrote:
> What I did to try and work around the issue is close aide.db as soon as
> possible (before the reporting is done). So basically, when a
> report (with or without differences found) is printed you will know
> gzclose() has
The only reason I can think of that would result in a corrupt gzipped
aide.db (and not in a corrupt/incomplete plaintext aide.db) is when aide
exists before gzclose() is called. Plaintext aide.db is flushed after
every line, for gzip this is skipped because it degrades the compression
a lot. I look
On Wed, Sep 27, 2006 at 10:56:09AM +0200, Bill Allombert wrote:
> I never experienced the bug with gzip_dbout=no for some months now, so
> I am confident this fixed it.
Very well, thanks. Can you set dzip_dbout again to verify that
hypothesis?
> I would suggest gzip_dbout=no be set as the default
On Thu, Jul 20, 2006 at 11:50:31PM +0200, Marc Haber wrote:
> On Thu, Jul 20, 2006 at 07:31:54PM +0200, Bill Allombert wrote:
> > On Tue, Jul 18, 2006 at 04:21:27PM +0200, Marc Haber wrote:
> > > May I remind? I suspect that we have a bug in the gzip code which I'd
> > > love to report upstream.
>
On Thu, Jul 20, 2006 at 07:31:54PM +0200, Bill Allombert wrote:
> On Tue, Jul 18, 2006 at 04:21:27PM +0200, Marc Haber wrote:
> > May I remind? I suspect that we have a bug in the gzip code which I'd
> > love to report upstream.
>
> Well, I did that and the bug has not show up yet, but since it wa
On Tue, Jul 18, 2006 at 04:21:27PM +0200, Marc Haber wrote:
> On Fri, Jun 23, 2006 at 11:54:19PM +0200, Marc Haber wrote:
> > On Fri, Jun 23, 2006 at 10:19:56PM +0200, Bill Allombert wrote:
> > > On Fri, Jun 23, 2006 at 11:23:14AM +0200, Marc Haber wrote:
> > > > Are you using gzipped db, or did yo
On Fri, Jun 23, 2006 at 11:54:19PM +0200, Marc Haber wrote:
> On Fri, Jun 23, 2006 at 10:19:56PM +0200, Bill Allombert wrote:
> > On Fri, Jun 23, 2006 at 11:23:14AM +0200, Marc Haber wrote:
> > > Are you using gzipped db, or did you gzip the files before encrypting
> > > them in the message?
> >
>
On Fri, Jun 23, 2006 at 10:19:56PM +0200, Bill Allombert wrote:
> On Fri, Jun 23, 2006 at 11:23:14AM +0200, Marc Haber wrote:
> > Are you using gzipped db, or did you gzip the files before encrypting
> > them in the message?
>
> I am using the standard Debian config which say
> gzip_dbout=yes
>
>
On Fri, Jun 23, 2006 at 11:23:14AM +0200, Marc Haber wrote:
> On Fri, Jun 23, 2006 at 07:34:02AM +0200, Marc Haber wrote:
> > On Thu, Jun 22, 2006 at 05:58:29PM +0200, Marc Haber wrote:
> > > Can you send me - in private - a corrupted and the correct database
> > > generated after the corrupted one
On Fri, Jun 23, 2006 at 07:34:02AM +0200, Marc Haber wrote:
> On Thu, Jun 22, 2006 at 05:58:29PM +0200, Marc Haber wrote:
> > Can you send me - in private - a corrupted and the correct database
> > generated after the corrupted one?
>
> I have received the files in private, encrypted e-mail and wi
On Thu, Jun 22, 2006 at 05:58:29PM +0200, Marc Haber wrote:
> Can you send me - in private - a corrupted and the correct database
> generated after the corrupted one?
I have received the files in private, encrypted e-mail and will take a
look at the later today.
Greetings
Marc
--
--
On Thu, Jun 22, 2006 at 05:30:25PM +0200, Bill Allombert wrote:
> Both actually:
> I run aide --check several time and I always get that the db is
> corrupted miss files.
Yes, so your aide.db is corrupted.
> Then I do aide --update and I get a working db.
Do you get a gazillion of "new file" re
On Thu, Jun 22, 2006 at 04:57:43PM +0200, Marc Haber wrote:
> On Thu, Jun 22, 2006 at 04:52:20PM +0200, Bill Allombert wrote:
> > Yes, I do
> > aide --update
> > mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
> > aide --check
> > If that reports a lot of missing files, I restart the process and
On Thu, Jun 22, 2006 at 04:52:20PM +0200, Bill Allombert wrote:
> Yes, I do
> aide --update
> mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
> aide --check
> If that reports a lot of missing files, I restart the process and it
> works.
Do you start again with aide --update, or with aide --chec
On Thu, Jun 22, 2006 at 03:53:38PM +0200, Marc Haber wrote:
> On Fri, Jun 16, 2006 at 04:06:31PM +0200, [EMAIL PROTECTED] wrote:
> > Experimentally, the corruption happens randomly when writing the
> > database. When I get a corrupted db, regenerating the database with the
> > same underlying files
On Fri, Jun 16, 2006 at 04:06:31PM +0200, [EMAIL PROTECTED] wrote:
> Experimentally, the corruption happens randomly when writing the
> database. When I get a corrupted db, regenerating the database with the
> same underlying filesystem lead to a non-corrupted db.
> OTOH, trying to read a corrupted
On Thu, Jun 01, 2006 at 05:22:47PM +0200, [EMAIL PROTECTED] wrote:
> On Tue, Apr 12, 2005 at 01:39:05PM +, Guillaume Tamboise wrote:
> > Package: aide
> > Version: 0.10-6.1
> > Followup-For: Bug #245423
> >
> >
> > I am facing the same issue with /sbin and with a certain number of files
> > i
On Thu, Jun 01, 2006 at 05:22:47PM +0200, [EMAIL PROTECTED] wrote:
> This problem make aide rather useless for me.
Do you have the possibility of trying a later aide version than the
one in sarge?
Greetings
Marc
--
-
Ma
On Tue, Apr 12, 2005 at 01:39:05PM +, Guillaume Tamboise wrote:
> Package: aide
> Version: 0.10-6.1
> Followup-For: Bug #245423
>
>
> I am facing the same issue with /sbin and with a certain number of files
> in /dev. I have been using aide for woody for a long time and never face
> this issu
forwarded #245423
https://sourceforge.net/tracker/index.php?func=detail&aid=1448359&group_id=86976&atid=581579
thanks
On Wed, Mar 08, 2006 at 02:02:30PM -0700, Will Aoki wrote:
> On Thu, Feb 23, 2006 at 10:32:59AM +0100, Marc Haber wrote:
> > On Tue, Jan 17, 2006 at 04:31:24PM -0700, Will Aoki wr
On Thu, Feb 23, 2006 at 10:32:59AM +0100, Marc Haber wrote:
> On Tue, Jan 17, 2006 at 04:31:24PM -0700, Will Aoki wrote:
> > This problem occurs on my various systems with great regularity. I can
> > trigger it reliably by making largeish changes to the filesystem which
> > modify existing files (s
On Tue, Jan 17, 2006 at 04:31:24PM -0700, Will Aoki wrote:
> This problem occurs on my various systems with great regularity. I can
> trigger it reliably by making largeish changes to the filesystem which
> modify existing files (such as by installing the recent perl security
> updates) and running
This problem occurs on my various systems with great regularity. I can
trigger it reliably by making largeish changes to the filesystem which
modify existing files (such as by installing the recent perl security
updates) and running an 'aide -u' to update the database.
If it would help, I should b
tags #245423 unreproducible
thanks
On Tue, Apr 12, 2005 at 01:39:05PM +, Guillaume Tamboise wrote:
> I am facing the same issue with /sbin and with a certain number of files
> in /dev. I have been using aide for woody for a long time and never face
> this issue. The issue came on board quickly
Package: aide
Version: 0.10-6.1
Followup-For: Bug #245423
I am facing the same issue with /sbin and with a certain number of files
in /dev. I have been using aide for woody for a long time and never face
this issue. The issue came on board quickly after I moved to Sarge.
-- System Information:
27 matches
Mail list logo
