Hello world,
I was wondering if this happened to anyone else? I read on the project homepage:

>July 8, 2004
>We have moved the scheduling server to another >machine in order to free up CPU and memory for the >DB server. Active clients will fail 10 times to >connect to the old scheduling server and then will >self correct by contacting the master URL. To force >the correction right away, simply detach and then(re)>attach the project.

So I did just that; detach and then (re)attach to the project...

Stupid me, all the WUs I had crunched already (but were not uploaded yet due to the server outages at SETI) were gone and all the ones I had downloaded too :-(
So please beware: following SETI instructions might not always be advisable...

Anyway, at least we do get some status info from the guys at Berkeley again... :-)

<a> [/url]

Worked fine on both my units, did you reattach using http://setiboinc.ssl.berkeley.edu/sah/

Unfortunately, unless you update the project before detaching you will lose completed work. Perhaps the message should be re-worded?

> Unfortunately, unless you update the project before detaching you will lose
> completed work. Perhaps the message should be re-worded?
>
>

Thanks Lowfield,

I think they should re-word the message...

Anyway, I'll be updating befor detaching in the future... :-)

<a> [/url]

OOPS

[/url] [/url]

> Worked fine on both my units, did you reattach using
> http://setiboinc.ssl.berkeley.edu/sah/

But that's not the url you should be using.

From the boinc news page: "June 22, 2004 The URL of this project is http://setiathome.berkeley.edu. If you joined using a different URL, please detach and attach to this URL."

Prior to June 22, the correct url was the setiboinc url. Eventually, that url will simply stop working and you'll get no more work with no explanation of why - kind of like the old maggie url did during beta.

That said, detaching will always cause you to lose any work still on your system. If you plan to detach, ideally, you should deplete all your work first.

Hi Darren,

I did use http://setiathome.berkeley.edu

but again, I should have updated first... MY FAULT... :-)

Just trying to save others from making stupid mistakes...

But I still think "they" should re-word the message on the homepage.

<a> [/url]

Another way that is safer to get through the 10 connections is to update and check the messages until you get a succeeded message. This will, however request work from some project just before the success.

And on top of it all, when you detach, (re) attach to the project you get a new computer ID...

This new ID can then be merged with the original one and you're left with the new ID. So my computer becomes 56116 after being 17445 for a while...

This really starts to remind me of those days in May 1999... :-(

Well, I think I'll just leave everything as it is, keep crunching and look at SETI again next month.

Sh..

Good night everyone... :-)

<a> [/url]

> > Worked fine on both my units, did you reattach using
> > http://setiboinc.ssl.berkeley.edu/sah/
>
> But that's not the url you should be using.
>
> From the boinc news page: "June 22, 2004 The URL of this project is
> http://setiathome.berkeley.edu. If you joined using a different URL, please
> detach and attach to this URL."
>
> Prior to June 22, the correct url was the setiboinc url. Eventually, that url
> will simply stop working and you'll get no more work with no explanation of
> why - kind of like the old maggie url did during beta.
>
> That said, detaching will always cause you to lose any work still on your
> system. If you plan to detach, ideally, you should deplete all your work
> first.
>
>
>

Detaching & reattaching to the Project has got to be the most Stupid Advice I have ever heard of. What about all the Wu's that will be dumped when people take this advice and then everybody's sitting around for the next 2 weeks wondering why they can't get no Wu's Verified. It will be because of this advice, thats why...

I suggest you just manually update your PC or PC,s, thats what I did and it wasn't that big of a deal, I have a lot of WU's Cached and just didn't feel like dumping them so they would have to be reissued in 2 weeks ...

Another way that is safer to get through the 10 connections is to update and check the messages until you get a succeeded message. This will, however request work from some project just before the success.
=========

Yes John, thats what I did, I figured it was better to do that then dump the Cached WU's I had and just let them sit around until the got reissuied...

> Another way that is safer to get through the 10 connections is to update and
> check the messages until you get a succeeded message. This will, however
> request work from some project just before the success.
> =========
>
> Yes John, thats what I did, I figured it was better to do that then dump the
> Cached WU's I had and just let them sit around until the got reissuied...
>

That's what I wanted to do.... But ever since the notice went up I haven't been able to update - all I get is :
2004-07-08 16:45:52 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2004-07-08 16:45:52 - No schedulers responded

I was hoping the project was down, but I see the webpage is running. I've tried to update dozens of times and don't get through. I don't want to detach and re-attach, but if it doesn't get throguh in the next couple of hours I guess I will have to.

Yeah detaching is catastrophic, and bad advice, it completely destroys your project directory, leaving you to download the client again, and a load of new WUs and reassigns your computer to a new host ID.

> Yeah detaching is catastrophic, and bad advice, it completely destroys your
> project directory, leaving you to download the client again, and a load of new
> WUs and reassigns your computer to a new host ID.
>
>

Well, that's still what is says one should do on the project homepage... :-(

I think Berkely is so busy trying to fix their servers they just don't have the time to read the forums and change things in time...

Thanks anyway for all the great tips... better late than never :-)

<a> [/url]

I am running on a Linux system. I was just looking at the client_state.xml file to try and figure out if there is a way to fool it into thinking that it has failed 10 times straight away.
Maybe setting or to 10.

Reason I am asking this is that I am on a dialup an don't want to lose all my current work, nor have to stay online for hours until it fails 10 times.

Any ideas anyone?

> Detaching & reattaching to the Project has got to be the most Stupid
> Advice I have ever heard of. What about all the Wu's that will be dumped when
> people take this advice and then everybody's sitting around for the next 2
> weeks wondering why they can't get no Wu's Verified. It will be because of
> this advice, thats why...
>
> I suggest you just manually update your PC or PC,s, thats what I did and it
> wasn't that big of a deal, I have a lot of WU's Cached and just didn't feel
> like dumping them so they would have to be reissued in 2 weeks ...
>
It may seem a bit silly but it is the only way for anyone who is still attached to the setiboinc URL. Only if you are attached to http://setiathome.berkeley.edu you can update to get the new scheduler URL.

John Keck
BOINCing since 2002/12/08

> It may seem a bit silly but it is the only way for anyone who is still
> attached to the setiboinc URL. Only if you are attached to
> http://setiathome.berkeley.edu you can update to get the new scheduler URL.

This is what I ran in to. Detaching was the only way to make it work. Not to mention my host ID in the low 3,000s. :(

<a> [/url]

After you have lost your CS then you get this?!?!?!?! Why is the conection always failing????:

--- - 2004-07-09 13:45:02 - Fewer active results than CPUs; requesting more work
--- - 2004-07-09 13:45:08 - Fewer active results than CPUs; requesting more work
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:45:08 - Requesting 23466 seconds of work
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:45:08 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:45:11 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:45:11 - No schedulers responded
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:45:11 - Deferring communication with project for 1 minutes and 0 seconds
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:46:11 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:46:14 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:46:14 - No schedulers responded
http://setiboinc.ssl.berkeley.edu/sah/ - 2004-07-09 13:46:14 - Deferring communication with project for 1 minutes and 0 seconds

Is this a way to limited member to get more WU??????????
Come on Perople Give us the INFO remeber we are doing this for free, but that dosen't give you the right to give us the wrong advice and ignoring us!!! Please keep us informe all the time. not just sporadic... We are here for you!!!! but we need to hear from you!!!
the Only RealBigSwede

Come get your BOINC T-Shirt @ [url=http://www.t-shirt.here.ws]the RealBigSwede's T-shirt Place<a>

[/url] [/url]