Due to a database issue last week, task generation is delayed and we need to clean up stuck workunits. The project daemons will be on and off this morning while we try to debug a problem with the BOINC transitioner.

The tasks that have already been sent out that you guys crunch do not slow down our processes. We have some problems after a lost database connection last week and an internal buffer overflow that we are now cleaning up. Hence the freshly generated tasks do not make it to the scheduler yet.

There should be tasks again once the BOINC transitioner has gone through the backlog.

thanks for the information.
What makes we wonder though is how the transitioner backlog could increase that much within the past 2 days (it's 42.21 hours right now) while now new tasks at all were sent out during this period. How come?

Indeed sorry again that some workunits that had been sent have been removed by mistake.

While our validators have been able to re-validate a majority of tasks, validation of the results for the lost VM application workunits could not be handled by standard validation process, so we have tried to give them all credit based on CPU time.

Thanks again to you all for your crunching and valuable contributions to LHC@home.