No wonder that last batch of new work went so quickly.

This is why i reduce my cpu time in this project...

Of course, Rosetta then gets less total CPU time, but it appears that they don't need it/can't use it anyway.

<message>
process exited with code 1 (0x1, -255)</message>
ERROR: ERROR: FragmentIO: could not open file 00001.500.6mers
ERROR:: Exit from: src/core/fragment/FragmentIO.cc line: 233
BOINC:: Error reading and gzipping output datafile: default.out

Returning to my anecdote about a remote PC I have being unable to download any Rosetta tasks, so running its backup project, WCG, 24/7, my local laptop is also doing weird things. It refuses to run a particular Rosetta task, so it's running those it has room for - a combination of WCG and later Rosetta tasks, but only 3 on 4 cores. Now I know it's definitely happening, I've set NNT and suspended all running tasks except for the one problem Rosetta task. It still refuses to run, even as the only task. No tasks are running in my experiment!

So, maintaining NNT, I've found some combination of WCG and Rosetta tasks that'll run together on all 4 cores. I'll work my way through my small cache until all are completed bar the problem task and see if it runs then. If not, I'll finally abort it and just grab fresh tasks.

Bit of a weird one. Even attempting to micromanage tasks doesn't entirely work. No wonder that graph is running so much lower than it was, if I'm any example

Finally got to the end of this.
Last night I had 3 WCG tasks running (2 of which were Africa Rainfall project that use slightly more RAM, but in fact were only using 300Mb each) and my one weird Rosetta nip* task reporting "waiting for memory" on my 4-core laptop.
Looking at my Event log, it was only when the last ARP was wrapping up that sufficient RAM was available for the Rosetta task to begin running. The last ARP task completed 3 minutes later and now the Rosetta task is the only task running.
Looking at the task's properties, it's only using between 271Mb & 292Mb RAM, while earlier complaining that it needed something like 6.6Gb RAM to begin.
I'm going to wait for completion before dragging any more tasks down. Hopefully there are some new tasks available to download at that time.

The task in question is this one

With 30 minutes to go, I've allowed new tasks and 11have come down. Stage one successful.
3 of the new tasks attempt to start. Stage two successful.
2 of the new tasks are waiting for memory... Oh

I'm going out for a while. When I return the older task will have completed and I'll see if the new tasks all run ok.
The journey continues...

And the answer is... no.
Still two new Rosetta tasks running and two more new ones waiting for memory...

It seems we're a way from having a solution or correction

Maybe you should have the occasional day off from your disgusting levels or personal entitlement too.

We had an interruption in power here last night (it happens), and when I got up this AM I found one of my hosts was completely dead. So, I restarted it and when I got into BOINC, I am finding that every task that I download aborts for "Computational Error" within about 20 seconds.

While this was going on, I tried to add SiDock as another project, with the intent to diversify as some have suggested (currently running Rosetta only). That produced an error that said that I could not join because I am required to agree to the terms of service. Which I did. I tried it a couple more times to confirm it.

Now I'm wondering if the power failure messed up something in BOINC, or if the problems are coincidental and not related to me.

Any suggestions?

couldn't start app: Input file rosetta_4.20_x86_64-pc-linux-gnu missing or invalid: file missing

You’re missing some prerequisite system libraries (glibc-⁠2.27)

We had an interruption in power here last night (it happens), and when I got up this AM I found one of my hosts was completely dead. So, I restarted it and when I got into BOINC, I am finding that every task that I download aborts for "Computational Error" within about 20 seconds.

While this was going on, I tried to add SiDock as another project, with the intent to diversify as some have suggested (currently running Rosetta only). That produced an error that said that I could not join because I am required to agree to the terms of service. Which I did. I tried it a couple more times to confirm it.

Now I'm wondering if the power failure messed up something in BOINC, or if the problems are coincidental and not related to me.

Any suggestions?

At the moment every Rosetta task I get is bombing Computation Error within 25 seconds of starting.

But, of course, during this holiday period people here expect to demand the creation and issue of sufficient work to serve at least a third of a million tasks per day to the world at large, with no respite.
And the amazing thing is, a fair few do seem to have come down. Maybe my caches aren't quite completely full, but near enough.

The last dozen I received also failed within 25 seconds. All of them had log files mentioning a missing file with 6mers in its name.

It looks like the project staff contains some students who still need lessons on how to read the task log files and correct any errors they find.

Ignore the …_abinitio_1_abinitio_… tasks; lots of people are reporting problems with those.

Ignore the …_abinitio_1_abinitio_… tasks; lots of people are reporting problems with those.

Of the ones i have had, i have 6 running, and 475 - so far - that errored out in seconds.

But, of course, during this holiday period people here expect to demand the creation and issue of sufficient work to serve at least a third of a million tasks per day to the world at large, with no respite.
And the amazing thing is, a fair few do seem to have come down. Maybe my caches aren't quite completely full, but near enough.

Maybe we are all just waiting for the resurrection of this project? Isn't that what Easter is all about?

Unless you have set it to use local settings, it will use whatever you have set in your account's Computing preferences section.