I keep getting this over and over! Would appreciate some help. Been with seti since early 1999 and I can't remember haveing to write to the board or seti to fix a problem. Bonic, very discourageing at this point. I have done everything it says to do, I think. I would hate to say goodbye to seti after all these years.

3/21/2005 11:11:33 AM||Starting BOINC client version 4.25 for windows_intelx86
3/21/2005 11:11:33 AM||Invalid account file: account_.xml
3/21/2005 11:11:33 AM|http://setiathome.berkeley.edu/|Using your default project prefs
3/21/2005 11:11:33 AM|http://setiathome.berkeley.edu/|Host ID not assigned yet
3/21/2005 11:11:33 AM||No general preferences found - using BOINC defaults
3/21/2005 11:11:33 AM||Insufficient work; requesting more
3/21/2005 11:11:33 AM|http://setiathome.berkeley.edu/|Requesting 8640.00 seconds of work
3/21/2005 11:11:33 AM|http://setiathome.berkeley.edu/|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
3/21/2005 11:11:55 AM|http://setiathome.berkeley.edu/|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
3/21/2005 11:11:55 AM|http://setiathome.berkeley.edu/|No schedulers responded
3/21/2005 11:11:55 AM|http://setiathome.berkeley.edu/|Deferring communication with project for 1 minutes and 0 seconds
3/21/2005 11:12:55 AM||Insufficient work; requesting more
3/21/2005 11:12:57 AM||Insufficient work; requesting more
3/21/2005 11:12:57 AM|http://setiathome.berkeley.edu/|Requesting 8640.00 seconds of work
3/21/2005 11:12:57 AM|http://setiathome.berkeley.edu/|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
3/21/2005 11:13:19 AM|http://setiathome.berkeley.edu/|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
3/21/2005 11:13:19 AM|http://setiathome.berkeley.edu/|No schedulers responded
3/21/2005 11:13:19 AM|http://setiathome.berkeley.edu/|Deferring communication with project for 1 minutes and 0 seconds

---

Hello Richard,

if you take a look around this board, it would be hard not to find at least a dozen threads about this. The most prominent hint is on the homepage of both Setis:

March 20, 2005
Our Internet link through Cogent went down at around midnight UTC on March 18/19. This is being looked at with an unknown time to fix. In the meantime, data service (upload/download) is unavailable.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Have you forgotten the numerous extended outages classic suffered? BTW, classic is down also. This is not only a SETI BOINC problem.

> I keep getting this over and over! Would appreciate some help. Been with seti
> since early 1999 and I can't remember haveing to write to the board or seti to
> fix a problem. Bonic, very discourageing at this point. I have done everything
> it says to do, I think. I would hate to say goodbye to seti after all these
> years.

... especially when there is no reason to do so.

If you only crunch SETI, and you are deeply concerned about running out of work, on this web site, visit "your account" and "general preferences" change "connect every 'x' days" to something like four or five.

... or add another project -- you can look for alien civilization and gravity waves.

---

Overall I think BOINC will spell the end of Seti@home. I tried the "attach every 5 days" routine with Seti and have run out of work during this outage, a total of 5 machines sitting idle. The next step was to attach to Einsetin and let that run so the CPU cycles aren't wasted. The point is that I joined Seti back in '97 to look for ET which is exactly what I want to do, not look for spinning neutron stars...not to say that looking for spinning neutron stars has no value, but I'm not looking for ET. End result is now Seti won't get 100% of my CPU time.

Bottom line is we're all being treated to a demonstration of a combination of academia, big business and government all "working" together to keep Seti running. Can anyone spell dysfunctional with the speed of drying paint?

To my knowledge, limited as it may be regarding distributed computing, Seti was either the first or among the first such projects. Now it has turned in to a broken shell of what it promised to be. A real shame.

---

> Overall I think BOINC will spell the end of Seti@home. I tried the "attach
> every 5 days" routine with Seti and have run out of work during this outage, a
> total of 5 machines sitting idle. The next step was to attach to Einsetin
> and let that run so the CPU cycles aren't wasted. The point is that I joined
> Seti back in '97 to look for ET which is exactly what I want to do, not look
> for spinning neutron stars...not to say that looking for spinning neutron
> stars has no value, but I'm not looking for ET. End result is now Seti won't
> get 100% of my CPU time.
>
> Bottom line is we're all being treated to a demonstration of a combination of
> academia, big business and government all "working" together to keep Seti
> running. Can anyone spell dysfunctional with the speed of drying paint?
>
> To my knowledge, limited as it may be regarding distributed computing, Seti
> was either the first or among the first such projects. Now it has turned in
> to a broken shell of what it promised to be. A real shame.

Actually, I think SETI says as much about us as it does about life here as it does about life off-planet.

It has been widely reported that SETI has way too much computing power. In fact, if we want to call this a conspiracy, well, if the outage pushes people to other projects, maybe it's a big plot to get you to donate CPU power to E@H, or CPDN.

... but I find the whole conspiracy theory fascinating. Yes, it's big business and the government conspiring to keep knowledge of the Extra-Terrestrials secret, at least until the treaties are in place and we've secured advanced technologies to insure the survival of the American Way!

I don't know how long you've been running BOINC, or when you set "connect every five days" but I do know from earlier outages that it works -- but you have to do that beforehand, not after.

Oh, and by the way, SETI Classic is down hard too -- Classic and BOINC use the same wire, and it's down. How that reflects on BOINC and not Classic isn't entirely clear.

---

> Overall I think BOINC will spell the end of Seti@home.
overall, i seriously doubt this.


> The point is that I joined
> Seti back in '97 to look for ET which is exactly what I want to do, not look
> for spinning neutron stars...not to say that looking for spinning neutron
> stars has no value, but I'm not looking for ET. End result is now Seti won't
> get 100% of my CPU time.

wow, what telescope where you working at?
i could not verify the actual start date, but The American Scientist. "Collective Wisdom". By Brian Hayes. March/April 1998, pg 118-22. Available on the web. talks about the PROPOSED seti@home. my memory recalls 1999, and the registration index at classic only goes to march 1999. i had thought that i got in on the 3rd day of the public release, but that does not appear to be the case. I have followed Dr. Drake's work from the early eighties (considering i was just 7 at the time) and have been involved in whatever tiny way i could be.
regardless, both of us were near the beginning. boinc is not perfect, but it is the best thing yet.

and if you want to work ONLY SETI (which is still far and away my favourite) you should get used to idle time. until astropulse and the southern observatory get online with us, we have enough computational power to keep seti drained dry. we will probably not have enough work even then to keep us users fed.
THAT is why boinc was made instead of updating the science applications again.
>
> Bottom line is we're all being treated to a demonstration of a combination of
> academia, big business and government all "working" together to keep Seti
> running. Can anyone spell dysfunctional with the speed of drying paint?
what part of SETI is government funded? there may be grants, but without the private sector, SETI would not exist.
>
> To my knowledge, limited as it may be regarding distributed computing, Seti
> was either the first or among the first such projects. Now it has turned in
> to a broken shell of what it promised to be. A real shame.
>

i may yet be driven away from the boards until the influx of useless fear of change complaining posts are settled down.

what is happening here is the real shame

---

S@h Berkeley's Staff Friends Club

WOW, I just a new work unit. Its starting to work, YEAH !!!

---

BOINC SYNERGY is an International Team and We Welcome All BOINC Participants!
BOINC Synergy Click to Join BOINC Synergy

Server is deluged with requests though...

> Overall I think BOINC will spell the end of Seti@home. I tried the "attach
> every 5 days" routine with Seti and have run out of work during this outage, a
> total of 5 machines sitting idle. The next step was to attach to Einsetin
> and let that run so the CPU cycles aren't wasted. The point is that I joined
> Seti back in '97 to look for ET which is exactly what I want to do, not look
> for spinning neutron stars...not to say that looking for spinning neutron
> stars has no value, but I'm not looking for ET. End result is now Seti won't
> get 100% of my CPU time.
>
> Bottom line is we're all being treated to a demonstration of a combination of
> academia, big business and government all "working" together to keep Seti
> running. Can anyone spell dysfunctional with the speed of drying paint?
>
> To my knowledge, limited as it may be regarding distributed computing, Seti
> was either the first or among the first such projects. Now it has turned in
> to a broken shell of what it promised to be. A real shame.
>


To bad you are to stiff and can not bend with the changing times.........

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Yeah! Downloaded one little WU. Uploads still failing though. Patience, please. This traffic jam won't clear in a minute.

---

Don't forget their planning to shut down again Tuesday morning, because of the campus power problem which is suppose to be 4 hours.

---

Red Bull Air Racing

Gas price by zip at Seti

> I keep getting this over and over! Would appreciate some help. Been with seti
> since early 1999 and I can't remember haveing to write to the board or seti to
> fix a problem. Bonic, very discourageing at this point. I have done everything
> it says to do, I think. I would hate to say goodbye to seti after all these
> years.

If you click the signature banner or the link below, you will have more than enough reading to keep you and your computer busy even in the "dry" times.

BOINC is a little more involved than SETI@Home Classic, mostly because many of the features of SETI@Home Classic were provided by third party software. In the case of BOINC these are native features.

And with any new program there are some issues, but, these are going away fairly rapidly.

And just a side note, the new SETI@Home will also be using you to process work for Astropulse as an integrated part of SETI@Home.

---

Change is inevitable, except from vending machines. BOINC is a slick piece of code. What I was trying to get across is that because BOINC makes it so easy to attach to alternate projects that Seti, with its problems, will suffer a major loss of computing power.

As far as Seti having too much computing power that is the choice of the participants. As valuable as all the other projects may be and are the choice of the participants regulates where the CPU cycles go. It seems that the question of "are we alone?" is the most compelling one offered so far by distributed computing projects. BOINC makes it easy to dedicate more CPU cycles to Seti by allowing weighting of project priority. The priority doesn't matter much though if Seti is down more often than the other projects.

Maybe it's actually the success of Seti that causes all of the problems. The explosion of users over the years would tax any network/server farm that doesn't have an unlimited budget. That makes it easier to understand the problems Seti has had and, overall, the "up time" has been pretty good in spite of Murphy.

I think everyone has to admit that the recent problems at Seti have been the worst by far. Yes, I remember many other outages over the years, some short and some not so short, but the recent spate has been of historic proportions. Finding out that the project wasn't on a UPS was a wake-up call. I know this is an "academic" project but it does seem to be a major "oversight" not to protect the servers from damage caused by something as common as power problems. The idea of all the work of the project support staff and all the participants being put at that kind of risk is a little disconcerting. I do hope that regular backups are made to alternate media.

Right now I have a total of about 80 WUs waiting to upload, but have plenty of work being processed so BOINC is doing its job. We can all only hope for better days ahead. Keep crunching!

---

> Change is inevitable, except from vending machines. BOINC is a slick piece of
> code. What I was trying to get across is that because BOINC makes it so easy
> to attach to alternate projects that Seti, with its problems, will suffer a
> major loss of computing power.

I am not sure if our experience to this point is really showing that. Based on usage statistics and some feedback from the SETI@Home folks indicate that we are doing roughly the same amount of science as is the SETI@Home Classic project. And we are doing it with fewer Participants. So, the loss may occur, or it might not ...

> As far as Seti having too much computing power that is the choice of the
> participants. As valuable as all the other projects may be and are the choice
> of the participants regulates where the CPU cycles go. It seems that the
> question of "are we alone?" is the most compelling one offered so far by
> distributed computing projects. BOINC makes it easy to dedicate more CPU
> cycles to Seti by allowing weighting of project priority. The priority
> doesn't matter much though if Seti is down more often than the other
> projects.
>
> Maybe it's actually the success of Seti that causes all of the problems. The
> explosion of users over the years would tax any network/server farm that
> doesn't have an unlimited budget. That makes it easier to understand the
> problems Seti has had and, overall, the "up time" has been pretty good in
> spite of Murphy.

Yes it has.

> I think everyone has to admit that the recent problems at Seti have been the
> worst by far. Yes, I remember many other outages over the years, some short
> and some not so short, but the recent spate has been of historic proportions.
> Finding out that the project wasn't on a UPS was a wake-up call. I know this
> is an "academic" project but it does seem to be a major "oversight" not to
> protect the servers from damage caused by something as common as power
> problems. The idea of all the work of the project support staff and all the
> participants being put at that kind of risk is a little disconcerting. I do
> hope that regular backups are made to alternate media.

The problem today is that very few of the UPS out there are really UPS, they are really SPS! And so, the protection is only for total power loss and power sags.

Changes in frequency, spikes, inverse spikes, power-line noise, and many other problems with input power are not handled at all.

> Right now I have a total of about 80 WUs waiting to upload, but have plenty of
> work being processed so BOINC is doing its job. We can all only hope for
> better days ahead. Keep crunching!

Because I have limited my cache and have managed to be lucky enough to be on all of the open projects I have a more limited exposure, though I do have 6 of my own that are patiently waiting to return home ...

---