Despite the upload server status showing 'running.' This is happening on a couple of computers.

I have the same problem. BOINC Manager says the completed work unit is uploading, but it isn't.

This is on a Raspberry Pi, which takes several days to complete a work unit; the deadline is today, so I would like the work unit submitted soon to get credit for work completed.

All of my work has uploaded yesterday I think I something like 33 results waiting

My clients are still unable to upload files and show messages like:

This

This issue hit my hosts again...
Is it still the filesystem to blame?

Yes, now it's working. I will try to check the "unable to upload" problem as soon as possible. Unfortunately it's Saturday:)

I still can´t up- or download any wu´s or results.

I have moved to Denis since they now have lots of work. Last time i looked they had about 62,000 WUs unsent

The project has an endemic problem with uploading results. I'm going to stop crunching for them.
____________

A proud member of the OFA (Old Farts Association)

Upload problem is back.

>>> The project has an endemic problem with uploading results. I'm going to stop crunching for them.

Why? It's been off most of the day, but my uploads have all cleared within the last couple of hours. BOINC handles this kind of thing fine.
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Not totally, I have 173 errors of which half are jobs cancelled by server and the other half are labeled Timed out -- No response. These are jobs that couldn't be uploaded in time due to either client back-off or due to files on the server that remain locked and cannot be opened when client tries the upload process again. The later can only be fixed by a server admin.

Cancelled by the server might go into the "errors" box, but really, it is not a client error, there is a limit on the number of boxes to put the figure. The server has been instructed to cancel remaining tasks already sent for a particular job, or class of jobs, if the criteria it is given are met. There are several, probably many, possible reasons for this. It might have been instructed to cancel jobs because an error has been found with them, alternatively, if the server has already received sufficient replies from other crunchers which are valid it cancels outstanding jobs to prevent crunchers wasting their time. You can get this message from all projects, I have received several of these messages from Rosetta this week for example.
Timed out is simply what it says, no reply has been successfully received for a job it has sent you before the given deadline. The deadline is used by the server to ensure that a task does, indeed, get processed. It allows it to resend the job to another cruncher so that the result can be assimilated.
Both of these "errors" can, and will be seen at all projects. A common cause is a client downloading excessive quantities of work units for the project.
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I understand fully what you are saying and you are correct. The server cancelled WUs are not a problem as they were the work that was in my queue and not started when quorum was established for the WU. The other work however was work that was stuck in upload and missed the deadline not because there was too much work queued (this project limits the amount of work queued to twice the number of threads) but because the client was in an extended backoff. If I micro managed the client, I would have noticed the extended backoff and forced an update which would have met the deadline. I just wish they would fix that filesystem issue once and for all.

Fair enough. I've never had that problem.
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.