Yesterday we discovered that when result files are lost, say due to a restore from a backup (restores involve both the DB and the ULDL directories) the validator ends up in a endless loop


log in

Advanced search

Message boards : News : Yesterday we discovered that when result files are lost, say due to a restore from a backup (restores involve both the DB and the ULDL directories) the validator ends up in a endless loop

Author Message
SETI News
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Dec 09
Posts: 383
Credit: 0
RAC: 0
Message 956499 - Posted: 8 Sep 2004, 0:00:00 UTC

Yesterday we discovered that when result files are lost, say due
to a restore from a backup (restores involve both the DB and the ULDL
directories) the validator ends up in a endless loop. The entire result
set for an affected workunit gets ignored and after a while the validator
ends up enumerating only affected workunits and is thus in a loop. We
turned off the validator when we discovered this. Today we have coded
a fix and are testing it in the alpha project. While the validator is off
credits are not given but they should show up once we turn the validator
back on.


The snap server continues to run well.

Message boards : News : Yesterday we discovered that when result files are lost, say due to a restore from a backup (restores involve both the DB and the ULDL directories) the validator ends up in a endless loop

Copyright © 2014 University of California