I recognize that there was a Rosetta fileserver crash 11/30. However, both the home page and the technical news page seem to imply that the fileservers are back online, which makes me think that client/server communication should have been restored.

However, my machines all have a number of WUs stuck at the "Uploading" phase, and there are a number of "temporarily failed upload" lines under the BOINC Mgr Messages tab.

It's not clear to me from what's on the home page and tech news page whether I should expect client/server comm to be back to normal now, or if I should expect a few more days of difficulty before things get back on track.

Should I hang tight, or do I need to reset my project to clear out the stuck WUs?

(An extra sentence on the tech news page saying something like, "Clients may experience delays communicating with servers for the next few days, but backlogged WUs should eventually get delivered," or "Clients still showing WUs in 'Uploaded' state should be reset," would be greatly appreciated.)

---

I recognize that there was a Rosetta fileserver crash 11/30. However, both the home page and the technical news page seem to imply that the fileservers are back online, which makes me think that client/server communication should have been restored.

However, my machines all have a number of WUs stuck at the "Uploading" phase, and there are a number of "temporarily failed upload" lines under the BOINC Mgr Messages tab.

It's not clear to me from what's on the home page and tech news page whether I should expect client/server comm to be back to normal now, or if I should expect a few more days of difficulty before things get back on track.

Should I hang tight, or do I need to reset my project to clear out the stuck WUs?

(An extra sentence on the tech news page saying something like, "Clients may experience delays communicating with servers for the next few days, but backlogged WUs should eventually get delivered," or "Clients still showing WUs in 'Uploaded' state should be reset," would be greatly appreciated.)

I think something like that has already been added. The new fileserver is online, but not all the files have been transferred from the old one; that is likely to take a few more days. I doubt if all the servers will work normally before then.

If you reset before it allows you to upload the previous results, you'll lose those results.

Checking for lockfiles now seems worthwhile, though.

I recognize that there was a Rosetta fileserver crash 11/30. However, both the home page and the technical news page seem to imply that the fileservers are back online, which makes me think that client/server communication should have been restored.

However, my machines all have a number of WUs stuck at the "Uploading" phase, and there are a number of "temporarily failed upload" lines under the BOINC Mgr Messages tab.

It's not clear to me from what's on the home page and tech news page whether I should expect client/server comm to be back to normal now, or if I should expect a few more days of difficulty before things get back on track.

Should I hang tight, or do I need to reset my project to clear out the stuck WUs?

(An extra sentence on the tech news page saying something like, "Clients may experience delays communicating with servers for the next few days, but backlogged WUs should eventually get delivered," or "Clients still showing WUs in 'Uploaded' state should be reset," would be greatly appreciated.)

I think something like that has already been added. The new fileserver is online, but not all the files have been transferred from the old one; that is likely to take a few more days. I doubt if all the servers will work normally before then.

If you reset before it allows you to upload the previous results, you'll lose those results.

Checking for lockfiles now seems worthwhile, though.

you should be able to deal with lockfiles without losing any data. the upload issue does not seem to be resolved yet. it has been a problem since i tried uploading at 10am european time. see other thread about unable to upload.

The upload server is trying to catch up. The data should eventually get uploaded.