Thank you all for your understanding and patience.

I have 7 tasks stuck in upload.
Is there any chance before Monday of getting them uploaded to you?
That's a lot of time sitting on my machine and no way to shut down the upload without killing the tasks.

>>> I have 7 tasks stuck in upload.

Stuck? My tasks are uploading without issue, I've just sent a couple within the last five minutes. Is there another issue?
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

>>> I have 7 tasks stuck in upload.

Stuck? My tasks are uploading without issue, I've just sent a couple within the last five minutes. Is there another issue?

I hope this filesystem problem gets repaired soon as I'm starting to see other troubling problems. To wit: Supposedly task 230186_Hs_T142754-TRIML1-wu96_1677560784479 was sent to one of my hosts on 28-Feb-2023 19:35:31 UTC. Looking through the client log, that task is not found in any form. At that time in the log there was an indication that a scheduler request timed out. I was never sent the WU but evidently the server thought it was. Consequently, 5 days later the task was listed as an error against my host as Timed out -- no response. I'm seeing a rising number of these against all my hosts. All my hosts return WUs within the 5 day return period. Several were flagged against my 128 thread EPYC server that cannot get even one day of work before hitting the "limit of tasks in progress" message. All systems are up 24/7/365 (mostly, except brief reboots for security fixes)

it is not a major problem as only about 86 of 15300 WUs were flagged as being timed out. I don't see them when the filesystem isn't acting up. hopefully, after the move, we won't see them anymore

I noticed that one way to get lost work units like these to be immediately marked as invalid to force the work unit to be sent out to another computer is to detach the computer that was assigned the lost work units from the project and then reattach the same computer to the project. The detachment and reattachment should be done after all of the work units on that machine have been uploaded and then reported by setting the project to "No new tasks" mode. This will cause the scheduler to mark the lost work units as abandoned.

Meanwhile the work generator will be active just a few hours a day, so very few workunits will be available.
Thank you all for your understanding and patience.

Hi, new user here (not new to boinc). I'm getting failed attempts when I try to attach this project to existing machines. "Failed to add project, please try again later". Is this expected in any way?

The University have bought a new one and they planned the moving procedure. The HPC cluster should be moved this Monday (March, 6th), the other resources will follow.
I will reasonably shut down the server when needed, I will tell you when as soon as I know the date. Meanwhile the work generator will be active just a few hours a day, so very few workunits will be available.

Thanks for confirming what was happening with the word generator. I have to agree everything seems to be running a lot nicer currently on the old server :-)
Out of curiosity when the move to new server happens what will happen with work that is currently being processed?