After six weeks of continuous operation, the validator exposed a bug in the unzip library which it uses to uncompress results, and crashed. I noticed this within a short time, and restarted the validator, but it crashed again on the same bug and this time a number of hours went by before I could look more carefully.
The authors of the zip library have been notified about the bug, and the validator has been restarted. After a number of hours offline, the validator had a backlog of about 14000 workunits to validate, which took some time to grind through. Right now the validator backlog is normal -- a handful of workunits. I really don't understand the P233 remarks: normally, workunits never wait more than about ten seconnds before validation.
Cheers,
Bruce

Validator offline??
)
This is because a week or so ago I changed one of the scheduler parameters so that unsent results only get 'forced' out to a host machine if they are more than a week old. Previously this happened if they were more than about two days old. The primary reason I made this change is that it will result in fewer large data file downloads by volunteers. To say it another way, it will tend to localize data files more, so that a given volunteer with a given data file will get more work for that file before having to download a new data file. I think this is a better choice for the project, although it may lead to somewhat longer average times to validation.
Cheers,
Bruce