This time of year I have world community grid on standby because rosetta tends to be down and no one is available to fix it.

---

This time of year I have world community grid on standby because rosetta tends to be down and no one is available to fix it.

Yes, I am inclined to throw a little more on OPN anyway since you never know where the new mutations will lead.

The project’s primary goal is to search for potential treatments for COVID-19, so studying proteins from SARS-CoV2 (the virus that causes COVID-19) is the highest priority.

Additionally, scientists want to fight not only the current emergency, but also prepare for the ones that will likely follow. Future pandemics could stem from a progressive accumulation of mutations, which can eventually lead to a new virus variant. This is what happened when the virus SARS-CoV1 mutated to become SARS-CoV2. So, the research team is including proteins from the SARS-CoV1 and other viruses to be studied as part of OpenPandemics –COVID-19, which will help them assess how difficult would it be to find or design molecules capable of overcoming the inevitable mutations.

https://www.worldcommunitygrid.org/research/opn1/overview.do


I would be happy to consider more Rosetta too if I knew which way they are going. But they don't tell us that.

---

11 million queued jobs

What matters are "Tasks ready to send" on the Server Status Page and that is near 0.

As i mentioned in my original post.

...all i get is No Tasks sent when requesting new work to replace returned work (Ready to send is zero).

---

Grant
Darwin NT

Are you saying that no one can remote into and reboot the servers? If so, that is not good.
There is a _lot_ of computing and good will lost if there are millions of jobs available and no one can download them.

In the past, some holidays have been out of all and any contact.
That may not be the case this time, but it's a possibility.
Point being, it'll be fixed when it's fixed and complaining repeatedly in the forums has rarely ever solved it

I see why the feedbacks are felt like complaints, but what it is meant as is an heads up that people want to do work and that idle CPUs are being wasted. People think that this is to important not to be mentioned because people care, and they get a bit bummed out when the reply can be interpreted as "what ever..." I guess no one is expecting people to leave their families to fix this, but it is a disappointment that there is no one who can spend ten minutes in a remote session to reboot the servers, just in case that helps.

To build a strong and lasting community there must be an "us". There must be some feeling of "we are all in on this together". Right now that feeling is diminishing, and that is not good.

I do hope there will be made some effort to both stopping this current bug to reappear, and for a solution where low effort incident resolving can be done.

Are you saying that no one can remote into and reboot the servers? If so, that is not good.
There is a _lot_ of computing and good will lost if there are millions of jobs available and no one can download them.

In the past, some holidays have been out of all and any contact.
That may not be the case this time, but it's a possibility.
Point being, it'll be fixed when it's fixed and complaining repeatedly in the forums has rarely ever solved it

I see why the feedbacks are felt like complaints, but what it is meant as is an heads up that people want to do work and that idle CPUs are being wasted. People think that this is too important not to be mentioned because people care, and they get a bit bummed out when the reply can be interpreted as "what ever..." I guess no one is expecting people to leave their families to fix this, but it is a disappointment that there is no one who can spend ten minutes in a remote session to reboot the servers, just in case that helps.

To build a strong and lasting community there must be an "us". There must be some feeling of "we are all in on this together". Right now that feeling is diminishing, and that is not good.

I do hope there will be made some effort to both stopping this current bug to reappear, and for a solution where low effort incident resolving can be done.

This kind of comment never goes down well with me...

- "Idle CPUs" is 100% always a user failure - or "bug" as you mistifyingly want to call it
- If "people think this is too important not to be mentioned" then they'll have missed it already having been mentioned a dozen times
- "ten minutes" - yeah, ok...
- "community", "us" - <puke>

---

Are you saying that no one can remote into and reboot the servers? If so, that is not good.
There is a _lot_ of computing and good will lost if there are millions of jobs available and no one can download them.

In the past, some holidays have been out of all and any contact.
That may not be the case this time, but it's a possibility.
Point being, it'll be fixed when it's fixed and complaining repeatedly in the forums has rarely ever solved it

I see why the feedbacks are felt like complaints, but what it is meant as is an heads up that people want to do work and that idle CPUs are being wasted. People think that this is too important not to be mentioned because people care, and they get a bit bummed out when the reply can be interpreted as "what ever..." I guess no one is expecting people to leave their families to fix this, but it is a disappointment that there is no one who can spend ten minutes in a remote session to reboot the servers, just in case that helps.

To build a strong and lasting community there must be an "us". There must be some feeling of "we are all in on this together". Right now that feeling is diminishing, and that is not good.

I do hope there will be made some effort to both stopping this current bug to reappear, and for a solution where low effort incident resolving can be done.

This kind of comment never goes down well with me...

- "Idle CPUs" is 100% always a user failure - or "bug" as you mistifyingly want to call it
- If "people think this is too important not to be mentioned" then they'll have missed it already having been mentioned a dozen times
- "ten minutes" - yeah, ok...
- "community", "us" - <puke>

Ok, I have gotten your message and taken my computer off line.

Are you saying that no one can remote into and reboot the servers? If so, that is not good.
There is a _lot_ of computing and good will lost if there are millions of jobs available and no one can download them.

In the past, some holidays have been out of all and any contact.
That may not be the case this time, but it's a possibility.
Point being, it'll be fixed when it's fixed and complaining repeatedly in the forums has rarely ever solved it

I see why the feedbacks are felt like complaints, but what it is meant as is an heads up that people want to do work and that idle CPUs are being wasted. People think that this is too important not to be mentioned because people care, and they get a bit bummed out when the reply can be interpreted as "what ever..." I guess no one is expecting people to leave their families to fix this, but it is a disappointment that there is no one who can spend ten minutes in a remote session to reboot the servers, just in case that helps.

To build a strong and lasting community there must be an "us". There must be some feeling of "we are all in on this together". Right now that feeling is diminishing, and that is not good.

I do hope there will be made some effort to both stopping this current bug to reappear, and for a solution where low effort incident resolving can be done.

This kind of comment never goes down well with me...

- "Idle CPUs" is 100% always a user failure - or "bug" as you mistifyingly want to call it
- If "people think this is too important not to be mentioned" then they'll have missed it already having been mentioned a dozen times
- "ten minutes" - yeah, ok...
- "community", "us" - <puke>

Ok, I have gotten your message and taken my computer off line.

There are over 30 other Boinc Projects that would love to have your pc crunch for them.

Ok, I have gotten your message and taken my computer off line.

There are over 30 other Boinc Projects that would love to have your pc crunch for them.

As does this project.

Work available to process, but not being sent out, is a project issue that they need to resolve.
To get results, they need to supply the work and fix whatever has caused the supply to come to a halt.

---

Grant
Darwin NT

Work available to process, but not being sent out, is a project issue that they need to resolve.

I think that we cannot see solution until next week....monday, i hope

---

Work available to process, but not being sent out, is a project issue that they need to resolve.

I think that we cannot see solution until next week... Monday, I hope

You can hope, but anything better than what I said before would pleasantly surprise me

The week of Monday 4th January is favourite now - and not the beginning of that week either.

In fact, in some years, stop-start supply problems have continued to the end of January, though given there's 11million in the pre-queue we may be spared this time.
Wish I was kidding, but past experience tells me this is what we have to expect.

---

Ok, I have gotten your message and taken my computer off line.

There are over 30 other Boinc Projects that would love to have your pc crunch for them.

As does this project.

Work available to process, but not being sent out, is a project issue that they need to resolve.
To get results, they need to supply the work and fix whatever has caused the supply to come to a halt.

Yes they would but the sporadic work makes it difficult for some people to figure things out, especially newbies or those that have focused solely on a single project that's always had work over the years. Those of us who understand how to make Boinc work for US have no problems.

Work available to process, but not being sent out, is a project issue that they need to resolve.

I think that we cannot see solution until next week... Monday, I hope

You can hope, but anything better than what I said before would pleasantly surprise me

The week of Monday 4th January is favourite now - and not the beginning of that week either.

In fact, in some years, stop-start supply problems have continued to the end of January, though given there's 11million in the pre-queue we may be spared this time.
Wish I was kidding, but past experience tells me this is what we have to expect.

And that's the problem with a Project that takes weekends off and seems to treat the tasks as 'a nice thing but not necessary to get done today and not tomorrow is okay too'. It's just life at Rosetta and has been that way for a very long time.

And that's the problem with a Project that takes weekends off and seems to treat the tasks as 'a nice thing but not necessary to get done today and not tomorrow is okay too'. It's just life at Rosetta and has been that way for a very long time.

It is probably in the nature of the work they send out to us. It is model development as I understand it. But they apparently do the actual folding and design of the proteins themselves.
So if we are out of work for a while, they don't really see the effects. They just make it up by sending out more work later.

---

And that's the problem with a Project that takes weekends off and seems to treat the tasks as 'a nice thing but not necessary to get done today and not tomorrow is okay too'. It's just life at Rosetta and has been that way for a very long time.

It is probably in the nature of the work they send out to us. It is model development as I understand it. But they apparently do the actual folding and design of the proteins themselves.
So if we are out of work for a while, they don't really see the effects. They just make it up by sending out more work later.

Yup that's my impressions too.

You can hope, but anything better than what I said before would pleasantly surprise me

The week of Monday 4th January is favourite now - and not the beginning of that week either.

In fact, in some years, stop-start supply problems have continued to the end of January, though given there's 11million in the pre-queue we may be spared this time.
Wish I was kidding, but past experience tells me this is what we have to expect.

And that's the problem with a Project that takes weekends off and seems to treat the tasks as 'a nice thing but not necessary to get done today and not tomorrow is okay too'. It's just life at Rosetta and has been that way for a very long time.

It's not a weekend - it's a Xmas/New Year break. Once a year, not once every week.
People deserve a proper break and I'm not inclined to demand they're dragged in to suit, what are essentially, hobbyists.
I have no idea how anyone gets the idea their priorities are more relaxed than ours. How condescending. I don't doubt for a second it's entirely the other way round.

The impression I do get is users think the project's work starts when tasks are downloaded and ends when they're returned. Except that's our job, not theirs.
It would seem obvious their work is all the preparation they do to create batches of tasks that test whatever their ideas are, then doing something with what returns and evaluating them as to what the output means and how it can be used.
That is, everything before we even see tasks, then everything after they're returned. And nothing much at all with what we do.

And that's a far better explanation of why nothing much gets done when situations like the one we have arise.

We're all here voluntarily, doing what the project needs when they need it - and if they don't need anything then we do nothing but wait for when they have a need again.
The idea that the project is here to keep our PCs fed with tasks is bonkers, tail-wagging-dog kind of crazy - and I don't know why people would ever think otherwise.
But people do and start coming out with stuff about "community" and "Rosetta is us", which I will always find head-shakingly bizarre #Cranks

---

People deserve a proper break and I'm not inclined to demand they're dragged in to suit, what are essentially, hobbyists.

No need to go in, just do a remote login & restart. If it fixes it, good. If not, then it can wait till they do go in.

But people do and start coming out with stuff about "community" and "Rosetta is us", which I will always find head-shakingly bizarre #Cranks

Which is probably why Rosetta is such a small project- that very lack of community.

---

Grant
Darwin NT

Which is probably why Rosetta is such a small project- that very lack of community.

Very true Grant (SSSF). Switched my CPU threads to Folding@Home. If they don't care much, why should we bother.

I know it's the holidays but an official word would have made all the difference, people wasting time troubleshooting their clients, rebooting systems, etc. lol

People deserve a proper break and I'm not inclined to demand they're dragged in to suit, what are essentially, hobbyists.

No need to go in, just do a remote login & restart. If it fixes it, good. If not, then it can wait till they do go in.

No need to do anything at all. Honestly, this is not some critical service they are running, it's a BOINC project, if it's down for a couple of days or even weeks, nothing will change except that they might need to publish some papers a bit later. Nothing, that I would expect anyone of them to regularly interrupt their vacation to check if the servers are running OK. That's not a vacation than anymore.

I know it's the holidays but an official word would have made all the difference, people wasting time troubleshooting their clients, rebooting systems, etc. lol

If people are wasting time for this instead of simply checking the server status page, what makes you think they will check if there are some other type of news about it? The "official word" regarding tasks ready to send is already there, updating every 10 minutes or so, people just need to read it.

---

.

Sure, people are just donating hardware, time, power bills and more for free. Gee, we owe Rosetta everything and should be grateful that they are giving us some numbers to crunch. Lord forbidd some one took 10 minutes to do a remote log on just to see if it was an easy fix some where. Or wrote a couple ow words on the home page on why idling CPUs is a good thing.

News flash, Rosetta needs us, we do not need Rosetta. If Rosetta does not want to engage in the community then there is no community. Apparently there is so much hardware for Rosetta that they do not need any more. And reading some of the comments here it looks like it would be a burden for Rosetta to get more hardware to crunch numbers on. So do like I did, took my computer offline and uninstalled Boinc. Best advice Sid Celery has ever given.

So do like I did, took my computer offline and uninstalled Boinc. Best advice Sid Celery has ever given.

Tasks for computer 4415639
Interesting, you don't seem to have run out of tasks, 14 still in progress, but uninstalled BOINC because servers are not sending new ones?

---

.