Questions and Answers :
Windows :
LHC contacting, um, Seti?
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 28 Sep 04 Posts: 1 Credit: 1,543 RAC: 0 |
What on earth is going on here> LHC@home - 2004-10-05 14:38:57 - Requesting 5372 seconds of work LHC@home - 2004-10-05 14:38:57 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi LHC@home - 2004-10-05 14:39:01 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded LHC@home - 2004-10-05 14:39:01 - Message from server: Invalid or missing authenticator. Visit this project's web site to get an authenticator. LHC@home - 2004-10-05 14:39:01 - No work from project LHC@home - 2004-10-05 14:39:01 - Deferring communication with project for 1 minutes and 0 seconds |
 xmal Send message Joined: 17 Sep 04 Posts: 10 Credit: 1,157,113 RAC: 0 |
Take a look at this thread: http://lhcathome.cern.ch/forum_thread.php?id=644 --- |
 Send message Joined: 27 Sep 04 Posts: 36 Credit: 29,315 RAC: 0 |
This is a known issue to the BOINC developers over @ Seti. Sometimes the BOINC client confuses the projects. It is normally cleared after a successful connect to the scheduler. The preceeding poster hasn't read the following line: LHC@home - 2004-10-05 14:39:01 - Message from server: Invalid or missing authenticator. Visit this project's web site to get an authenticator. Which means BOINC has actually contacted the Seti server and rejected the LHC authenticator. greetz, Uli |
©2024 CERN