Another stupid idea: did you tweak the checks that update daemon (and/or rid script) does at it's start to ensure that only one copy of the daemon is running at any single moment? If you somehow get multiple copies of the update deamon running, there might be a chance of them corrupting the database..... But probably this is bullshit, since berkeley db has a database type for concurrent access and it was the one that I used for update daemon, I think. I just do not remember the details anymore. -i On Sat, Jan 15, 2011 at 12:15 AM, Ivan Kurmanov <duraley@gmail.com> wrote:
Guys, when did you have corruption errors for the first time? Was there an upgrade or something exactly before that?
-ivan
On Fri, Jan 14, 2011 at 11:45 PM, Thomas Krichel <krichel@openlib.org> wrote:
Thomas Krichel writes
Christian Zimmermann writes
Yes this is what I am doing. But knowing a minority complain, this is not reassuring.
I am spending yet more time trying to took into this.
I tried an elaborate method today,
#!/bin/bash db4.6_dump /home/aras/acis/RI/data/ACIS/records > ~/acis_records.dump db4.6_load -f acis_records.dump -h /home/aras/acis/RI/data ~/acis/RI/data/ACIS/records db4.6_load -r lsn -h /home/aras/acis/RI/data ~/acis/RI/data/ACIS/records
and the ame for RePEc/records, but now found it still has helped, we still have corruption.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run