as of last update 22.01 utc servers are still down.

As of 3 Jan 2009 1:09:06 UTC (updated every 10 minutes)

servers down again, 354 tasks ready to go out.
main page says there are just 7 tasks ready to go.

i will be out of work pretty soon. boosted my run time to 8 hrs.

any news?

There was some work over 1.000 tasks, one work spliter was running.

Now both are offline again, such is life. I'm out of work for Rosetta.

pete.

---

Looks like the admins are off celebrating the long weekend -- we might well be out of work until sometime on Monday.

There was some work over 1.000 tasks, one work spliter was running.

Now both are offline again, such is life. I'm out of work for Rosetta.

pete.

---

There are 24,000 in the queue now. I filled up my quota.

---

Morning all.

It is in Oz anyway!

Looks like both spliters are down again, no work until someone gives them a kick again.

pete.

---

It is not just a matter of starting a job. The reason they are inactive is because the queue of tasks is apparently empty. "so fill the queue"... yes, I'm sure they will. Until then, there isn't any work unless tasks pass deadlines, or report failures.

---

Rosetta Moderator: Mod.Sense

It is not just a matter of starting a job. The reason they are inactive is because the queue of tasks is apparently empty. "so fill the queue"... yes, I'm sure they will. Until then, there isn't any work unless tasks pass deadlines, or report failures.

When will there be new work?

It is not just a matter of starting a job. The reason they are inactive is because the queue of tasks is apparently empty. "so fill the queue"... yes, I'm sure they will. Until then, there isn't any work unless tasks pass deadlines, or report failures.

When will there be new work?

2 days ago I started Rosetta@Home, merely to have my computer doing something. Seti@Home ran dry because of a server problem which took like forever to be fixed (I'm sure the guys at Berkely did all they could do but sometimes it just takes a while). Now I am almost out of work at Rosetta as well.
Does this happen often? I mean do I have to set my workbuffer at a large amount of days to be able to keep doing work, without running dry? What are your experiences?

Does this happen often? I mean do I have to set my workbuffer at a large amount of days to be able to keep doing work, without running dry? What are your experiences?

My experience has been that brief outages are common, but extended outages are rare. In the past, a two day queue would ride out nearly all of them.

I'm currently using a shorter queue than that because I believe that earlier results are more useful. The Rosetta team can use these preliminary results to tweak the next batch of WUs.

I shall not state anything spectacular saying that these outages are annoying - especially after problems with Work Units themselves.

It is a double pity as my BOINC@Poland team chose Rosetta@Home as their project of the month for January - just to see problems with fetching data and some WUs.

I'm afraid that what supposed to be an advertisement and encouragement for some crunchers to help and stay with Rosetta could bring a contrary effect.

I shall not state anything spectacular saying that these outages are annoying - especially after problems with Work Units themselves.

It is a double pity as my BOINC@Poland team chose Rosetta@Home as their project of the month for January - just to see problems with fetching data and some WUs.

I'm afraid that what supposed to be an advertisement and encouragement for some crunchers to help and stay with Rosetta could bring a contrary effect.

With today only being the 4th and with the Holidays almost over I would guess that your Team will have plenty of time to more than make up for a few bad days. I would expect everything to be back in tip top shape sometime tomorrow, the 5th. Congratulations on selecting Rosetta for your Teams Project of the Month!! I wish you all well.

---

out of work on RAH for the first time since I joined this project.
now running einstein 100% until something else comes in.
this is the lowest level RAH has ever gone to.
hope that the rest of 2009 will be better.

It is not just a matter of starting a job. The reason they are inactive is because the queue of tasks is apparently empty. "so fill the queue"... yes, I'm sure they will. Until then, there isn't any work unless tasks pass deadlines, or report failures.

Not sure if I'm misunderstanding this. Do you mean that there's no input to the rah_make_work* servers or just that they aren't running to output anything?

---

Also, the server status page is showing:

Program___ Host Status
transitioner boinc Not running

What does this do? Anything we should concern ourselves with?

---

Im not getting work... No changes have been made to preferences.

Boinc requests XXXXX seconds of work but just gets 0 tasks...

???

guys, the simplest version of this whole thing is that the system is 'broken'.
there is NO work
there is nothing WE can do, but WAIT.
when the team comes in on monday morning pacific time,they will get on this.

i am out of work and so are allot of other people, so we just sit and wait.

Also, the server status page is showing:

Program___ Host Status
transitioner boinc Not running

What does this do? Anything we should concern ourselves with?

If you review all of the posts on the message boards for the past 3 days, you will find two themes. One is that people are upset because they got work, and it encountered errors or ran much too long. The other is they are unable to get work.

When pockets of tasks are hit that error out quickly, the queue of tasks can become depleted rather quickly.

Do you mean that there's no input to the rah_make_work* servers

That puts it well Sid, yes. I just didn't feel most people would understand a statement like that. Also, depending on what the Project Team has in progress, they may need to test new tasks on Ralph first as well, before releasing new work here.

All the tasks you are seeing come out are just the WUs that are being reissued due to errors by the first party, or expiring deadlines. This is why there are so few.

---

Rosetta Moderator: Mod.Sense

Do you mean that there's no input to the rah_make_work* servers

That puts it well Sid, yes. I just didn't feel most people would understand a statement like that. Also, depending on what the Project Team has in progress, they may need to test new tasks on Ralph first as well, before releasing new work here.

All the tasks you are seeing come out are just the WUs that are being reissued due to errors by the first party, or expiring deadlines. This is why there are so few.

Amazed that an untechnical person like me got that right. But I'm a process engineer so I guess I appreciate the process even if I'm unqualified in the detail.

So this takes the problem to a whole other level. Best to just wait.

I'm just reminded of a remark made by a manager of mine a few years ago:
"There's 24 hours in a day and it's not essential to sleep or take holidays in the short-term..."

He wasn't popular either...

---

Do you mean that there's no input to the rah_make_work* servers

That puts it well Sid, yes. I just didn't feel most people would understand a statement like that. Also, depending on what the Project Team has in progress, they may need to test new tasks on Ralph first as well, before releasing new work here.

All the tasks you are seeing come out are just the WUs that are being reissued due to errors by the first party, or expiring deadlines. This is why there are so few.

Amazed that an untechnical person like me got that right. But I'm a process engineer so I guess I appreciate the process even if I'm unqualified in the detail.

So this takes the problem to a whole other level. Best to just wait.

I'm just reminded of a remark made by a manager of mine a few years ago:
"There's 24 hours in a day and it's not essential to sleep or take holidays in the short-term..."

He wasn't popular either...

interesting quote for sure....