Hi Willy,
weekend is nearing, so you've got enough time to fix this (I hope).
Since 2 days BOINCstats didn't update, there has been some incremental update since, but no real one. What has happened?

In the "Last 30 days (based on the daily update numbers)" at the bottom of every page just the date changed. The latest numbers there are still the same as tuesday, but the date shown is today. :confused:

According to the status in the menu bar, there were daily updates the last two days, but they don't show up in the stats. :/

Edit: Site has been very slow since yesterday, too.

I'm actually in Geneva for the BOINC workshop. I'll get home Friday night, and I have to work on Saturday.

So I'l try to have a quick look now. It appears to be a caching problem.

Usually caching problems can be solved by choosing another language, but this one persists, even in chinese

There's a difference between the stats for the projects in combined and the projects themself now. In combined the last two days have appeared, in my case as "+ 4,860.99 since then", and in two steps in best 5 days (I coincidently resetted them before this), there it's 2007-09-05 2,654 and 2007-09-06 2,181, which sums up nearly to 4860.
In the project stats it's still the old amount, without anything added.

But enjoy the workshop in Geneva, tell us something about it later on, and care about the stats once you're back and family has had you beck for a sufficient time

Problem is found.

It actually all started yesterday. The webserver was showing a lot of idle MySQL processes which were slowing down the server. To solve this a timeout for idle queries was set.

BUT, the update uses the webserver database for an up-to-date list of projects, and during the update of a large table this connection is idle, and you guessed it, it gets terminated. This then causes the upload of updated tables to the webserver.

Why was I thinking caching: because one of the incremental updates crashed the database server was locked for updates. This cause the cache directory to 'overflow' causing yet another problem today.

I fixed the stats replication, but due to the limitations I have here it did not replicate the history tables. This means historical data is two days off on the webserver, but the data is ok on the databaseserver and will replicate to the webserver after the next daily update.