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.

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.

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?

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.

And only being able to get 2 new Tasks at a time it's going to take a long time for all of these duds to be cleared out.
My maximum Tasks per day & the number of errors i'm returning are rapidly approaching each other.


At this rate no one will be able to get more than a couple of Tasks (when some that can be processed without error are eventually released) because they will have used up all of their Maximum Tasks per day credit.
It'll take 8 hours to return a valid result (with luck) & then bump up the limit to a couple of Tasks, Another 8 hours to return some more Valid results, and bump up the limit by a few more Tasks.
It's leading to an extremely ugly mess.

---

Grant
Darwin NT

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.

---

Grant
Darwin NT

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.

So errors are in:
- _abinitio_1_abinitio_
- 6mers

Practicaly, all wus!!

---

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?

Everything running great last night. Got up to see 3 remaining running tasks and the entire rest of my cache with the Computation errors we've all now seen.
So much for rushing through fresh tasks. Slower and more sure may be the better policy.

Took WCG off NNT. 217 tasks came down...
That should certainly provide some breathing space

---

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

What causes it to switch to local settings?

It seems the RAM problem is not yet solved. I just updated Rosetta now and got the same complaint about needing 6 GB of RAM and only having 3 GB.

It's not a problem, it's just some tasks needing more RAM.

It is a problem when a Work Unit says it it will need 6+GB of RAM, when it really only needs 300MB (or less), as that results in almost a third of the projects computing resources becoming unavailable.

It's true all the ones that came through to my larger machines all say under 700MB RAM. Maybe they can occasionally need a lot more so they're playing safe and not crashing small machines with them?

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

I used to run Rosetta by itself. Now I run SiDock too (both at 100%) and don't have to worry about switching anything.
Of course, Rosetta then gets less total CPU time, but it appears that they don't need it/can't use it anyway.

You can always set SiDock to 0 priority, then it will only get that if Rosetta is broken.
By the way it's not percent. I can set priorities to add up to any number.

I must agree with Brian, pretty disappointing that I have yet to see a project admin come in even acknowledging there is an issue. I'll give it to the end of the week. If it doesn't appear anyone is working on the problem I'll most likely drop Rosetta and look for a different project to donate processing to.

Why do you expect them to spend time talking to us instead of working on the programming and science? If things go wrong, they'll notice when they don't get the tasks sent back completed, then they'll fix it, they need it fixed so they can get the science done. all you need to do is check in here to see if any other volunteers are experiencing the same problem. If we all are, then it's not your end at fault.

Seeing as it seems to be whining season for the excessively-entitled it might be worth making myself as popular as usual by stating the obvious that I can't be the only one aware of.

1) Looking at my main PC, I've downloaded 54 tasks today across 10 separate downloads. Even my weirdly-running laptop managed 6 more. And my Android 4 more.
For all the comments about it (none) it seems like I'm the only one.
Of course, I'm not.

2) There are people here from all over the world, and a similar range of nationalities and creeds at UW from what I've observed, so some people may not be aware that UW is in the USA, which is a largely Christian country.
Traditionally their institutions and work-places close for the Easter holidays which have been taking place over the last4 days, from "Good Friday" to "Easter Monday" even if some of the people working there don't personally celebrate.

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.

And as thanks, I see the usual levels of appreciation here, to wit, "if you don't supply what I need 24hrs a day, even during the holiday season, and provide chapter and verse on progress to tell us what we already know, loyalty will be shown by reducing contribution levels or leaving altogether"

Maybe you should have the occasional day off from your disgusting levels or personal entitlement too.
Though tbf, there's never any shortage of that.

Yeah, save it. I heard last time too. And the time before that. And the time before that etc

Well put.

Me, I have obsessive-compulsive tendencies

Then keep them to yourself.

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

Woah, dude, you can tell that even though my system was turned off?

Did you find the horse porn folder too? That was from...uh, my kid brother.

Apparently that's illegal. When I was a teenager, everyone had seen the Pamela Anderson with a horse video. Seems we're getting prudish nowadays.

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

What causes it to switch to local settings?

My bet is, accidentally pressing the button to see what it does, not noticing anything immediate, then shrugging, followed by not remembering some years later whether you pressed the button or not for that host (puts hand up)

---

It seems the RAM problem is not yet solved. I just updated Rosetta now and got the same complaint about needing 6 GB of RAM and only having 3 GB.

It's not a problem, it's just some tasks needing more RAM.

It is a problem when a Work Unit says it it will need 6+GB of RAM, when it really only needs 300MB (or less), as that results in almost a third of the projects computing resources becoming unavailable.

It's true all the ones that came through to my larger machines all say under 700MB RAM. Maybe they can occasionally need a lot more so they're playing safe and not crashing small machines with them?

What I noticed earlier today was, I had 3 good tasks running and 11 came down.
As they began to run for 10 or 15 seconds before erroring out, 3 more than the existing 3 would run at a time with the others saying "Waiting for memory"
As each crashed out, one of the waiting-for-memory tasks would start running until crashing out. And so on until they all had.
So that's 6 tasks running at a time from 28Gb of memory allocated to Boinc. SIX!

The vast majority of people won't stand a chance at that rate.
I'd need 75Gb of free RAM allocated to Boinc to run on all 16 cores.
Never going to happen.

Up to yesterday I seemed to be running 16 tasks comfortably within 28Gb. No idea what's going on now. Bizarre.

---

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

What causes it to switch to local settings?

My bet is, accidentally pressing the button to see what it does, not noticing anything immediate, then shrugging, followed by not remembering some years later whether you pressed the button or not for that host (puts hand up)

Where is this button? I've never seen it. I assumed that it changed mine to local because I changed a local setting - eg the buffer size.

It seems the RAM problem is not yet solved. I just updated Rosetta now and got the same complaint about needing 6 GB of RAM and only having 3 GB.

It's not a problem, it's just some tasks needing more RAM.

It is a problem when a Work Unit says it it will need 6+GB of RAM, when it really only needs 300MB (or less), as that results in almost a third of the projects computing resources becoming unavailable.

It's true all the ones that came through to my larger machines all say under 700MB RAM. Maybe they can occasionally need a lot more so they're playing safe and not crashing small machines with them?

What I noticed earlier today was, I had 3 good tasks running and 11 came down.
As they began to run for 10 or 15 seconds before erroring out, 3 more than the existing 3 would run at a time with the others saying "Waiting for memory"
As each crashed out, one of the waiting-for-memory tasks would start running until crashing out. And so on until they all had.
So that's 6 tasks running at a time from 28Gb of memory allocated to Boinc. SIX!

The vast majority of people won't stand a chance at that rate.
I'd need 75Gb of free RAM allocated to Boinc to run on all 16 cores.
Never going to happen.

Up to yesterday I seemed to be running 16 tasks comfortably within 28Gb. No idea what's going on now. Bizarre.

If the program needs the RAM, there's nothing they can do about it, unless they go back in time and find the real programmers who could write a game that ran in 48KB. Chances are some of the tasks will have less of a RAM need, and you'll get a decent mix. Or you get some from another project at once.

And why have you only got 48GB? I have 64 out of an allowed 128.

Maybe it has something to do with the recent SSL post they posted on the Forum News.
Maybe every client instance has to manually reset the URL like months ago.
I don't really know, but you are right, the project is in risk of losing a lot of WUs if they don't attest to this issue.
Keep the faith in this project!

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

What causes it to switch to local settings?

My bet is, accidentally pressing the button to see what it does, not noticing anything immediate, then shrugging, followed by not remembering some years later whether you pressed the button or not for that host (puts hand up)

Where is this button? I've never seen it. I assumed that it changed mine to local because I changed a local setting - eg the buffer size.

It's at the very top of Computing Preferences - above all the tabs.
I know what you mean - it's so obvious I go blind to it

---

It seems the RAM problem is not yet solved. I just updated Rosetta now and got the same complaint about needing 6 GB of RAM and only having 3 GB.

It's not a problem, it's just some tasks needing more RAM.

It is a problem when a Work Unit says it it will need 6+GB of RAM, when it really only needs 300MB (or less), as that results in almost a third of the projects computing resources becoming unavailable.

It's true all the ones that came through to my larger machines all say under 700MB RAM. Maybe they can occasionally need a lot more so they're playing safe and not crashing small machines with them?

What I noticed earlier today was, I had 3 good tasks running and 11 came down.
As they began to run for 10 or 15 seconds before erroring out, 3 more than the existing 3 would run at a time with the others saying "Waiting for memory"
As each crashed out, one of the waiting-for-memory tasks would start running until crashing out. And so on until they all had.
So that's 6 tasks running at a time from 28Gb of memory allocated to Boinc. SIX!

The vast majority of people won't stand a chance at that rate.
I'd need 75Gb of free RAM allocated to Boinc to run on all 16 cores.
Never going to happen.

Up to yesterday I seemed to be running 16 tasks comfortably within 28Gb. No idea what's going on now. Bizarre.

If the program needs the RAM, there's nothing they can do about it, unless they go back in time and find the real programmers who could write a game that ran in 48KB. Chances are some of the tasks will have less of a RAM need, and you'll get a decent mix. Or you get some from another project at once.
And why have you only got 48GB? I have 64 out of an allowed 128.

I allocate 28Gb from 32Gb total
They don't need the RAM. If they run, they generally use 300Mb, not 5 or 6Gb each. It's more than a bit crackers

Anyway, new news. I grabbed another few tasks while WCG is mainly running and they all seems new and running normally without crashing.
I think the hint dropped pretty heavily when every task got sent back un-run.
Things are happening whether they say so here or not

---