It might help if you actually read other threads in the forum as well. NOBODY can upload/download or communicate in any way with the project servers for more than a day now...

.. And I suggest to inform users at least on main page about such issues ..
it would definitely reduce number of such posts

I have finished several tasks and there are no errors, but it couldn't upload, and the time left shown in 'status' just delayed for many times, besides, I found that the 'TeraFLOPS estimate' in the frontpage is 7.068, and it's far below several days before, I remember three days before, that was over 100, so I guess there maybe some errors with the server and I'm calling for help.
Thanks!

Oh well. It's Sunday so I expect we will have to wait another day for the comms to be sorted out.

Why not abort these tasks as has been reported as the fix on the front page and all over these forums?

Yes but Remote Desktop is $80

Wed 18 Jul 19:56:15 2012 | | max memory usage when idle: 3686.40MB
Wed 18 Jul 19:56:15 2012 | | max disk usage: 0.00GB

...I will be ABORTING...

Thus assuring that you receive zero credit for the effort.

As of now there are only 18,000 WU's left. My Boinc manager is already giving the message: "Message
From Server: No Work Sent."

We will probably run out of WU's in a few hours and shut-down for the rest of the weekend.

pfft, just more lack of communication and action by R@H team.
total work units queued goose egg 0.
in the news section any info? no - why should there be this is not news.
news here on the boards? no - same reason, this is not news.

RALPH has separate executables for minirosetta (current version of Rosetta@Home) and minirosetta_beta (next version of Rosetta@Home). At the moment, the two applications are identical, despite their different version numbers.

minirosetta => 3.18
minirosetta_beta => 3.17

During the update process, the two versions will diverge. The idea behind this is to always have a running version of the software currently deployed on Rosetta@Home available for test.

Why isn't ralph being used to catch these errors? All workunits I've received from ralph recently have been using app version 3.14.

The offending jobs have been removed.

Rosetta is a large and diverse project. Unlike more focused efforts such as SETI@Home, the breadth of compute tasks being performed on Rosetta@Home is incredible. While offering enormous flexibility, this greatly complicates testing and validation. Unfortunately, some bad jobs slipped in this time. In many cases, Rosetta@Home users such as myself find out about failing jobs when you do, and we're just as frustrated when such jobs are distributed.

Thank you for your continued support.

Well, never a dull moment...

Does anyone know what the issue is here or is this (just) another "it's weekend and no sysadmin is around" kind of typical R@H thing again? :-(

Ralf

It's slow but it isn't a problem.

The validator is probably working through a backlog of results after their downtime, hence the pending status of tasks.

Everything normal here as of now,
Uploads, downloads, validation, no pending`s,
Though from what you are saying here something else is not.

Either the validator is malfunctioning and this is not registering on the Server Status page, or else it is badly behind. I have over 120 work units waiting to validate -- some are several days old.