Get the following for ~ 2 hrs:

SETI@home Beta Test - 2005-06-26 20:20:39 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi
SETI@home Beta Test - 2005-06-26 20:20:43 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi failed
SETI@home Beta Test - 2005-06-26 20:20:43 - No schedulers responded
SETI@home Beta Test - 2005-06-26 20:20:43 - Deferring communication with project for 1 minutes and 0 seconds
--- - 2005-06-26 20:20:56 - Suspending network activity - user request
--- - 2005-06-26 21:07:21 - Resuming network activity
SETI@home Beta Test - 2005-06-26 21:07:21 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi
SETI@home Beta Test - 2005-06-26 21:07:26 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi failed
SETI@home Beta Test - 2005-06-26 21:07:26 - No schedulers responded
SETI@home Beta Test - 2005-06-26 21:07:26 - Deferring communication with project for 1 minutes and 0 seconds

---

Aloha, Uli

Yes i have been having the same problem.

---

<a href="http://setiweb.ssl.berkeley.edu/beta/status.php">status.php</a> nearly everything is red there

---

Same here, but S@H-public seems to have similar probs, look

4.19 didn't have the bugfixed parser yet but the later versions of BOINC should recognize the scheduler reply :

"Project is temporarily shut down for maintenance" and request_delay=3600 it says


I can access public without problems btw., just a few minutes ago I got new work.


For the accessibility of the schedulers I have those

<img src="http://oct31.org/boinc_sched/SETI_Beta.png"> for Beta

<img src="http://oct31.org/boinc_sched/SAH.png"> for Public

but I don't parse what the scheduler says, just check if there's a properly formed XML reply. It is refreshed every 15 minutes so using it in message boards doesn't put additional load on the project servers.

---

4.19 didn't have the bugfixed parser yet but the later versions of BOINC should recognize the scheduler reply :

"Project is temporarily shut down for maintenance" and request_delay=3600 it says

Just curious , is this the message everyone else is getting ?

2005-06-27 06:13:16 [SETI@home Beta Test] Scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi failed with a return value of 500
2005-06-27 06:13:16 [SETI@home Beta Test] No schedulers responded

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>

That's the same message I'm receiving.

6/27/2005 10:45:35 AM|SETI@home Beta Test|Scheduler request to http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi failed with a return value of 500
6/27/2005 10:45:35 AM|SETI@home Beta Test|No schedulers responded

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=2230">

Eric M. over at Pirates identified this as an internal server error. IIRC there is a thread in the S@H NC boards where PDB has been logging errors like this. Rom is aware of it and (I don't want to misquote him) asked someone (Timothy I think it was) to install "symbols" to get a better read on the error.

June 27, 2005
We're seeing a conflict with the way that the beta (which is using a newer BOINC version than setiathome) is interacting with the public project. We've turned off the beta until we can get the SETI@home boinc software updated.

First page info

Let's detach and mug away all waiting to reported and waiting to be crunched work units already gotten and let the dev people time to do first the mandatory basic setup of this project.

It looks like, it's to early to support this project.

Right now, the farm has 55 WUs to crunch and 42 waiting to be reported.

It's a honor to support an emerging project, but it's a waste of effort and contributed cpu-time, when the project is "not ready".

Even it's a beta project, please close the doors, until it's ready...

Einstein and predictor are waiting;-)

seeU later !

...Even it's a beta project, please close the doors, until it's ready...
Einstein and predictor are waiting;-)
seeU later !

You're absolutely right, more for other projects, that are at least working. Dam'ned, lots of cycles wasted (again!). Detaching...

---

Aloha, Uli

...Even it's a beta project, please close the doors, until it's ready...
Einstein and predictor are waiting;-)
seeU later !

You're absolutely right, more for other projects, that are at least working. Dam'ned, lots of cycles wasted (again!). Detaching...

Yes ! perfect chance for me to overtake some people here the second it comes back online haha ! er .. i mean .. *cough* yes i'm detaching too... *wink*

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>

Front page news reiterated:

June 27, 2005
We're seeing a conflict with the way that the beta (which is using a <b>newer BOINC version</b> than setiathome) is interacting with the public project. We've turned off the beta until we can get the SETI@home boinc software updated.

Newer Boinc version? I thought everyone was still using 4.19 to 4.45 versions. There are two of us officially running 4.46 AFAIK. Do you think they meant newer Application?

tony

Newer Boinc version? I thought everyone was still using 4.19 to 4.45 versions. There are two of us officially running 4.46 AFAIK. Do you think they meant newer Application?

I think you'll find they are talking about server-side stuff and not client-side.
That's my guess anyway...

---

Cheers,
Gary.

So exactly how long is this project supposed to be down?

---

me@rescam.org

Me, I went with the Suspend &amp; reset route. Don't want to give up my low IDs :)

To those who feel that their CPU cycles on this project have been "wasted" so far, this is in the nature of a beta project. Those CPU cycles haven't been wasted, but have caught a problem that might have been carried on into production and affected a far wider client base. If you expect that everything is going to proceed in a straight line towards a final release ready code, you're in for some disappointment. Aren't you a bit of a fair-weather friend? You knew the job was dangerous when you signed up. This is akin to the responses that lead the developers to remove public access to the beta core client code.

---

Beta credits always get wiped anyway, so if you're worried about credits, I suggest not running beta.

Beta credits always get wiped anyway, so if you're worried about credits, I suggest not running beta.

Not in it for the credits ...

Just the fame and fortune ;)

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>

So exactly how long is this project supposed to be down?

I'm not sure when it will be up....but....

I've been talking with Eric Korpela, the developer of SETI@home, and he has rewritten a source file (chirpfft.cpp..I confirmed it) but if you have any WUs in your cache, you can keep crunching with your current cruncher. That's why I'm not complaining ;)

And IMHO some people were using wrong crunchers (i.e. SETI@home public cruncher on this beta project.....) and it has made the trouble. That's what the june 27 news article means.

Next Windows cruncher sounds faster than the current one because it will use fftw library (maybe the one I compiled now) and Linux cruncher probably won't have graphics capability......he wrote.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

So exactly how long is this project supposed to be down?

I'm not sure when it will be up....but....

I've been talking with Eric Korpela, the developer of SETI@home, and he has rewritten a source file (chirpfft.cpp..I confirmed it) but if you have any WUs in your cache, you can keep crunching with your current cruncher. That's why I'm not complaining ;)

And IMHO some people were using wrong crunchers (i.e. SETI@home public cruncher on this beta project.....) and it has made the trouble. That's what the june 27 news article means.

Next Windows cruncher sounds faster than the current one because it will use fftw library (maybe the one I compiled now) and Linux cruncher probably won't have graphics capability......he wrote.

Doh i killed the remaining WU's =/ the news on the 26th made me think we were going to have to reset.
Luckily i kept the 35'ish completed WU's sitting around ( well lucky if everyone else in the quorum hasn't reset ).

Tetsuji , did he let you get your hands on the source for the new cruncher ? =)

---

<a href="http://www.boincsynergy.com"><img src="http://www.boincsynergy.com/images/stats/comb-950.jpg"></a>