Will anybody be around to fire up the validators and/or scheduler before Monday (once the deleters are done)?

In the news they write that plan to stay offline until Friday, but it's Saturday here and we dont't know the status of the deletion. Hope that wen they wake up at berkeley, they switch on all.

It's possible to add the deleter backlog in the status page Rom?

---

GHz
BOINC.Italy

Okay, here is an update.

Right now there are roughly 600,000 files left for the file deleter to deal with. Current estimates say the file deleters should be finished by tomorrow morning.

The reason that the validators are down is because both the validators and file deleters were getting in each others way in the upload directory. So the current line of thinking is let the file deleter queue drain quickly and then attempt to bring the project up and see if the validator queue can hold it’s own after a day or two of the project being up and people have reported in and have new work to crunch. If the validator cannot keep up then the project will be brought back down and the validator queue will be drained and the project will be brought back up.

While it hasn’t been stated, I believe that if S@H is still having problems after all of that then the upload directory is going to be moved to a different device and file system which should be better able to deal with a lot of small files better.

is this why i am not getting any work units at the moments

Thanks for this update - would it be possible for someone to update the main SETI page with it so folks don't have to go searching in the forums for it?

is this why i am not getting any work units at the moments

Yes ! Anything in front end is down ... So it's why you can't upload AND download.

Thanks Rom for your update.

One thing I don't get is why not draining the WFV queue to at least 500 000 before coming back live. You're going to get 1 000 000 results back as soon as you'll open the upload, so isn't it risky ?

The file system is there for 1 000 000 results (1024*1024) as far as I'm not mistaken, so it will be slow for long before catching, and stopping the project with 2 000 000 results will take much more time than with the current 1 000 000 waiting.

I believe that finshing the clean up before coming on line would be safer.

---

"In a world without walls and fences, who needs windows and gates ?"
for the team

Hi folks ... are there any plans to add new/better HW to the existing one ? There were many problems in the availibility of the system all year long, and you people at seti is giving their best to keep going ...
Warm Regards from Buenos Aires

---

An additional thought: If the bottle neck is the WU processing at seti, and the the 'work' at each invididual machine .. would it make sense to send 'larger' (i.e. more time consuming) units to the users, and so the amount of WU processed per day will be smaller ? just an idea ...
regards
andres

---

it's 0920 EDT and all of the server processes have been disabled

---

it's 0920 EDT and all of the server processes have been disabled

Yes, but it's now 04:30 Berkeley time and it's died! Looks like somebody is in at the lab REALLY EARLY (Either that or Matt L or somebody did it through an SSH or something).

---

With regard to working week ends, firstly this is still not life and death. So, if you work 365 days a year, then you can have the expectation that so will everyone else. Not a realistic expectation, but, an expectation none the less.

Still along those lines, watching the post times and changes to CVS the UCB people do seem to work long and odd hours. So, they may still come in this week end. But, again, why should this be an expectation? And don't tell me it is a public project. Finding ET tomorrow, or next week, or even later is not that critical.

With regard to the hand-shaking problems, there are supposed to be changes in the client and server side programs to do this better. One of the issues to be addressed is the problems with regard to the "ghost" work units being issued. Because this increases complexity, and normal practice is to not make systems more complex than needed (which should be a warming thought for those that think BOINC is too complex - they did try to use the simplest protocol - and our experience is that it was too simple - so we get a change) until proven otherwise.

So, as with all things, patience is a virtue. For those into instant gratification, the source code is available, feel free to fix all of the problems today and send your perfectly executing system to UCB c/o Rom or Dr. Anderson ...

(parenthetical note: It sure seems that the people with the greatest expectations of perfection, and the most critical of the current system would have by now created the perfect "BOINC Lite" for us to use. I wonder what is holding up the production? Does anyone know? Oh, and feel free to work this weekend on the code ...)

---

it's 0920 EDT and all of the server processes have been disabled

Yes, but it's now 04:30 Berkeley time and it's died! Looks like somebody is in at the lab REALLY EARLY (Either that or Matt L or somebody did it through an SSH or something).

Oh boy, time to clear up some misconceptions...

1. UTC is fixed and does not observe Daylight Savings Time. The time zone that comprises England does, so while England floats ahead in the summer, UTC should always be a fixed constant.

2. Berkeley is in the Pacific (US) time zone and is three hours behind the Eastern US and eight behind the UK. As of this writing (0942 EDT / 1342 UTC) it's eighteen minutes shy of 7 AM there.

:o)

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

(parenthetical note: It sure seems that the people with the greatest expectations of perfection, and the most critical of the current system would have by now created the perfect "BOINC Lite" for us to use. I wonder what is holding up the production? Does anyone know? Oh, and feel free to work this weekend on the code ...)

All the world is filled with great expectorations, but most of them don't mean spit... ;o)

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

You are perfectly right in your remarks, as often...
But to keep the enthousiasm going,... the least that everyone deserves is some kind consideration concerning INFORMATION...
Most considerate and well behaving people on this boards HAVE/HAD lots of patience,... but it would help to be a little bit more informed than how this is going the last two days. From the point of public relations I would call it a real disaster.

Greetings,
HP

---

All the world is filled with great expectorations, but most of them don't mean spit... ;o)

What the Dickens does this mean?

Pip

---

Oh boy, time to clear up some misconceptions...

1. UTC is fixed and does not observe Daylight Savings Time. The time zone that comprises England does, so while England floats ahead in the summer, UTC should always be a fixed constant.

2. Berkeley is in the Pacific (US) time zone and is three hours behind the Eastern US and eight behind the UK. As of this writing (0942 EDT / 1342 UTC) it's eighteen minutes shy of 7 AM there.

:o)

Right, and I was just making an observation as to the status of the servers. I know how UTC works. Where's the misconception?

---

All the world is filled with great expectorations, but most of them don't mean spit... ;o)

What the Dickens does this mean?

Pip

Expectoration

We're scheduling and validating now!

Sounds a good plan (Apart from the scheduler)!

---

With regard to working week ends, firstly this is still not life and death. So, if you work 365 days a year, then you can have the expectation that so will everyone else. Not a realistic expectation, but, an expectation none the less.

The difference is that seti, and the other projects, amount to a hobby. There is no life or death, no money to be lost, if it's down for 10 minutes or down for 10 weeks. This model, as it is now, would last about a week in the 'real' world where working or being on call 24/7/365 does have life and death or financial bottom line consequences.

With regard to working week ends, firstly this is still not life and death. So, if you work 365 days a year, then you can have the expectation that so will everyone else. Not a realistic expectation, but, an expectation none the less.

The difference is that seti, and the other projects, amount to a hobby. There is no life or death, no money to be lost, if it's down for 10 minutes or down for 10 weeks. This model, as it is now, would last about a week in the 'real' world where working or being on call 24/7/365 does have life and death or financial bottom line consequences.

Ok, if patience is what you want, along with understanding, then that's what you'll get.

Bill

---

Rom, I'm sitting here with 685 work units waiting to upload, some have drifted past due by a day or two, many others are getting close. Will Berkeley take into account the down time and allow these work units as finished on time or am I just generating heat at a time when CALISO would prefer that I use my "appliances" sparingly?

---

well the server status changed again... the deleters are offline....
(at 15:10 UTC)

---

Mark