Hi Raf, On Fri, Jun 14, 2013 at 12:24:11AM +0100, Raf Czlonka wrote: > On Wed, Jun 12, 2013 at 06:42:42PM BST, Hannes von Haugwitz wrote: > > This situation can occur if the cron job is started while the > > initialization process of the installation is still running. > > I don't think you understand. As I've written above, when choosing 'Yes' > to debconf's question whether to copy the '.new' database and replace > existing one, it's not being done - '/var/lib/aide/aide.db.new' is not > being copied to '/var/lib/aide/aide.db' [0]. > > With a new installation there's obviously no 'existing one', but that's > beside the point. > > The easiest way to test it is if you purge all the aide packages and > reinstall 'aide' and 'aide-common'.
I have tested it: # aptitude purge aide aide-common # aptitude install aide aide-common Answered 'yes' to both debconf questions and waited until the aideinit process has been finished. # ls -l /var/lib/aide/ total 42640 -rw-r--r-- 1 root root 39379 Jun 14 04:13 aide.conf.autogenerated -rw------- 1 root root 21897438 Jun 14 04:24 aide.db -rw------- 1 root root 21897438 Jun 14 04:24 aide.db.new So I'm not able to reproduce your issue that way. I'm only able to reproduce the error message from the cron job, if the cron job is executed right after the installation and before the aideinit process has been finished. That's why I have added this explanation to the error message and marked this bug pending. If this issue is still not solved, please provide more information about how to reproduce it. Best regards Hannes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
