I detached from the seti/boinc project only to find on trying to re-attach that the project URL received via email is no longer valid. Anyone know what the new project URL might be today and for the next couple of minutes?

Thanks

http://setiathome.berkeley.edu
Ich höre immer gerne zu,wenn ich auch nicht immer belehrt werden möchte ;-)

Isn't that the old one?

Mine logs on to:

http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi

No Aziz, that's the address of the Seti RPC scheduler within BOINC. The URL that you use to attach to the project with is as Guido said http://setiathome.berkeley.edu
----------------------
Jordâ„¢

> Isn't that the old one?
>
> Mine logs on to:
>
> http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
>
>
i am not sure but i think this one is for the scheduler, not the project url.
but i have been wrong before :)


<a> [/url]

http://setiathome.berkeley.edu is the one in the email received at account activation, but BOINC reports the following:

2004-07-14 12:20:54 - Couldn't read master page for http://setiathome.berkeley.edu/: error -107
2004-07-14 12:20:54 - Detaching from project - check for URL error

This is the correct URL:

http://setiathome.berkeley.edu (use when you actually "attach" to project)



Ranz


PS To Joseph: Why all the double posts??? I found your question on 3 separate boards. Do you think that's really necessary? And we wonder why the server has problems...

> PS To Joseph: Why all the double posts??? I found your question on 3 separate
> boards. Do you think that's really necessary? And we wonder why the server has
> problems...

You found my replies on all 3 threads as well. ;)
But that shouldn't hurt this server. It's only text. This server and the database server aren't really related, they may live in the same machine (for all we know), but they don't live side by side on the same harddrive/partition.

error -107 is a connection error. The URL is sound, yet you may have to change something on your side, or you just have to wait until the server is up&running normally before you try again.


----------------------
Jordâ„¢

Sorry for the shotgun approach in search of an answer. Guess I picked the wrong day to update to BOINC 3.2 and then try to detach and re-attach to Seti thinking it would solve communications problems with the Seti/BOINC server(s) as per the homepage post:

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
---------------------------------------------------------------

Bad mistake in judgement on my part. You are probably correct about just waiting for the Seti/BOINC server(s) to become operational before trying again to attach back to the project. Errors -113 and -153 also were noted in the message tab section of BOINC from this update.

I guess it's best to check the message boards first as to the Seti/BOINC server operation before doing any updates.

Thanks for the help.




> > PS To Joseph: Why all the double posts??? I found your question on 3
> separate
> > boards. Do you think that's really necessary? And we wonder why the
> server has
> > problems...
>
> You found my replies on all 3 threads as well. ;)
> But that shouldn't hurt this server. It's only text. This server and the
> database server aren't really related, they may live in the same machine (for
> all we know), but they don't live side by side on the same
> harddrive/partition.
>
> error -107 is a connection error. The URL is sound, yet you may have to change
> something on your side, or you just have to wait until the server is
> up&running normally before you try again.
>
>
> ----------------------
> Jordâ„¢
>
>
>

Joseph, one last link for you: All of BOINCs errors :)

And okay, they may not explain that much, but in time we may find out more about them. :)
----------------------
Jordâ„¢

Thank you Jorden,

The error number explanations were helpful in that they started me thinking.
Checking again on my side, I found that my firewall was blocking the new BOINC version 3.20 just installed; which is strange as it flagged me when BOINC initially tried to access the net and I remember giving BOINC firewall permission at that time. It's either a glitch in the firewall, or my understanding of how it operates. I didn't have that problem with BOINC 3.19 though. I will have to remember to double check firewall permissions in the future when updating.

Thanks again for your help. :>)


> Joseph, one last link for you: <a> href="http://boinc.berkeley.edu/error_numbers.h">All of BOINCs errors[/url] :)
>
> And okay, they may not explain that much, but in time we may find out more
> about them. :)
> ----------------------
> Jordâ„¢
>
>
>

You're welcome. :)

Had you asked this in the Windows forums over on Q&P only, we'd may have found this out earlier. :)

----------
Jord.