SETI@HOME and SETI beta acting up


log in

Advanced search

Message boards : Number crunching : SETI@HOME and SETI beta acting up

Author Message
Anthony Chapman
Volunteer tester
Avatar
Send message
Joined: 16 Apr 08
Posts: 30
Credit: 2,801,579
RAC: 0
United States
Message 1004953 - Posted: 17 Jun 2010, 0:30:00 UTC

When seti came back up today I had all kinds of problems. One of witch was I was told to detach and reattach to seti. So i did and now when I try to attach to seti beta it gives me the attached message. Then the two projects stop working right. wont get new work and both projects say the same name now. seti beta just says seti@home.

6/16/2010 5:13:56 PM Fetching configuration file from http://setiweb.ssl.berkeley.edu/beta/get_project_config.php
6/16/2010 5:14:02 PM http://setiweb.ssl.berkeley.edu/beta/ Master file download succeeded
6/16/2010 5:14:07 PM http://setiweb.ssl.berkeley.edu/beta/ Sending scheduler request: Project initialization.
6/16/2010 5:14:07 PM http://setiweb.ssl.berkeley.edu/beta/ Requesting new tasks for CPU and GPU
6/16/2010 5:14:09 PM SETI@home Scheduler request completed: got 0 new tasks
6/16/2010 5:14:09 PM SETI@home You used the wrong URL for this project
6/16/2010 5:14:09 PM SETI@home The correct URL is http://setiathome.berkeley.edu/
6/16/2010 5:14:09 PM SETI@home You seem to be attached to this project twice
6/16/2010 5:14:09 PM SETI@home We suggest that you detach projects named SETI@home,
6/16/2010 5:14:09 PM SETI@home then reattach to http://setiathome.berkeley.edu/
6/16/2010 5:14:09 PM SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
6/16/2010 5:14:09 PM SETI@home Consider detaching this project, then trying again
6/16/2010 5:14:09 PM SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project .

Profile Questor
Volunteer tester
Send message
Joined: 3 Sep 04
Posts: 362
Credit: 150,972,245
RAC: 32,461
United Kingdom
Message 1004957 - Posted: 17 Jun 2010, 0:40:35 UTC - in response to Message 1004953.

When seti came back up today I had all kinds of problems. One of witch was I was told to detach and reattach to seti. So i did and now when I try to attach to seti beta it gives me the attached message. Then the two projects stop working right. wont get new work and both projects say the same name now. seti beta just says seti@home.

6/16/2010 5:13:56 PM Fetching configuration file from http://setiweb.ssl.berkeley.edu/beta/get_project_config.php
6/16/2010 5:14:02 PM http://setiweb.ssl.berkeley.edu/beta/ Master file download succeeded
6/16/2010 5:14:07 PM http://setiweb.ssl.berkeley.edu/beta/ Sending scheduler request: Project initialization.
6/16/2010 5:14:07 PM http://setiweb.ssl.berkeley.edu/beta/ Requesting new tasks for CPU and GPU
6/16/2010 5:14:09 PM SETI@home Scheduler request completed: got 0 new tasks
6/16/2010 5:14:09 PM SETI@home You used the wrong URL for this project
6/16/2010 5:14:09 PM SETI@home The correct URL is http://setiathome.berkeley.edu/
6/16/2010 5:14:09 PM SETI@home You seem to be attached to this project twice
6/16/2010 5:14:09 PM SETI@home We suggest that you detach projects named SETI@home,
6/16/2010 5:14:09 PM SETI@home then reattach to http://setiathome.berkeley.edu/
6/16/2010 5:14:09 PM SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
6/16/2010 5:14:09 PM SETI@home Consider detaching this project, then trying again
6/16/2010 5:14:09 PM SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project .


Are you using an account manager? I use BAM and had a problem earlier this evening with a machine that only is attached to S@H. Everything suddenly changed to saying S@H beta. It couldnt connect because it wasnt registered but unfortuately managed to upload a few tasks which are now lost to main. Resynchronizing with BAM flipped everything back to normal.


____________
GPU Users Group



Anthony Chapman
Volunteer tester
Avatar
Send message
Joined: 16 Apr 08
Posts: 30
Credit: 2,801,579
RAC: 0
United States
Message 1004959 - Posted: 17 Jun 2010, 0:44:31 UTC - in response to Message 1004957.

No I don't use an account manager. This is just weird!!!!

Profile Questor
Volunteer tester
Send message
Joined: 3 Sep 04
Posts: 362
Credit: 150,972,245
RAC: 32,461
United Kingdom
Message 1004969 - Posted: 17 Jun 2010, 0:58:43 UTC - in response to Message 1004959.
Last modified: 17 Jun 2010, 1:04:24 UTC

No I don't use an account manager. This is just weird!!!!


BAM may have been a red herring. I had also had various ADSL problems and DNS issues (but assumed they were just local problems) - I wonder if something screwy happened and the wrong IPs were somehow resolved.

As you say weird.

This was my screen at the time. From 22:37 until I resynced at 23:00 it was connected to Beta.

16/06/2010 22:34:47 SETI@home Sending scheduler request: To fetch work.
16/06/2010 22:34:47 SETI@home Reporting 1 completed tasks, requesting new tasks for CPU and GPU
16/06/2010 22:35:14 SETI@home Scheduler request completed: got 0 new tasks
16/06/2010 22:35:14 SETI@home Message from server: Project has no jobs available
16/06/2010 22:37:30 SETI@home Sending scheduler request: To fetch work.
16/06/2010 22:37:30 SETI@home Requesting new tasks for GPU
16/06/2010 22:37:56 SETI@home Computation for task 17dc09ac.15550.10701.10.10.77_1 finished
16/06/2010 22:37:56 SETI@home Starting 17dc09ac.14698.11519.9.10.109_1
16/06/2010 22:37:56 SETI@home Starting task 17dc09ac.14698.11519.9.10.109_1 using setiathome_enhanced version 608
16/06/2010 22:37:57 SETI@home Beta Test Scheduler request completed: got 0 new tasks
16/06/2010 22:37:57 SETI@home Beta Test You used the wrong URL for this project
16/06/2010 22:37:57 SETI@home Beta Test The correct URL is http://setiweb.ssl.berkeley.edu/beta/
16/06/2010 22:37:57 SETI@home Beta Test Using the wrong URL can cause problems in some cases.
16/06/2010 22:37:57 SETI@home Beta Test When convenient, detach this project, then reattach to http://setiweb.ssl.berkeley.edu/beta/
16/06/2010 22:37:57 SETI@home Beta Test Message from server: Invalid app version description
16/06/2010 22:37:57 SETI@home Beta Test Message from server: Invalid app version description
16/06/2010 22:37:57 SETI@home Beta Test Message from server: Can't find host record
16/06/2010 22:37:57 SETI@home Beta Test Message from server: Invalid or missing account key. To fix, detach and reattach to this project .
16/06/2010 22:37:58 SETI@home Beta Test Started upload of 17dc09ac.15550.10701.10.10.77_1_0
16/06/2010 22:38:04 SETI@home Beta Test Finished upload of 17dc09ac.15550.10701.10.10.77_1_0
16/06/2010 22:41:50 SETI@home Beta Test Computation for task 17dc09ac.14698.11519.9.10.109_1 finished
16/06/2010 22:41:50 SETI@home Beta Test Starting 17dc09ac.19671.10701.11.10.66_1
16/06/2010 22:41:50 SETI@home Beta Test Starting task 17dc09ac.19671.10701.11.10.66_1 using setiathome_enhanced version 608
16/06/2010 22:41:52 SETI@home Beta Test Started upload of 17dc09ac.14698.11519.9.10.109_1_0
16/06/2010 22:41:59 SETI@home Beta Test Finished upload of 17dc09ac.14698.11519.9.10.109_1_0
16/06/2010 22:45:45 SETI@home Beta Test Computation for task 17dc09ac.19671.10701.11.10.66_1 finished
16/06/2010 22:45:45 SETI@home Beta Test Restarting task 07mr07am.20835.9070.9.10.137_0 using setiathome_enhanced version 608
16/06/2010 22:45:47 SETI@home Beta Test Started upload of 17dc09ac.19671.10701.11.10.66_1_0
16/06/2010 22:45:54 SETI@home Beta Test Finished upload of 17dc09ac.19671.10701.11.10.66_1_0
16/06/2010 22:59:55 SETI@home Beta Test Computation for task 17dc09ac.7891.9065.7.10.220_0 finished
16/06/2010 22:59:55 SETI@home Beta Test Starting 08mr07ak.21508.9479.12.10.127_2
16/06/2010 22:59:55 SETI@home Beta Test Starting task 08mr07ak.21508.9479.12.10.127_2 using setiathome_enhanced version 603
16/06/2010 22:59:55 SETI@home Beta Test Starting 17dc09ac.19671.476.11.10.160_1
16/06/2010 22:59:55 SETI@home Beta Test Starting task 17dc09ac.19671.476.11.10.160_1 using setiathome_enhanced version 603
16/06/2010 22:59:55 SETI@home Beta Test Starting 17dc09ac.19671.476.11.10.154_0
16/06/2010 22:59:55 SETI@home Beta Test Starting task 17dc09ac.19671.476.11.10.154_0 using setiathome_enhanced version 603
16/06/2010 22:59:57 SETI@home Beta Test Starting 17dc09ac.19671.10701.11.10.65_1
16/06/2010 22:59:57 SETI@home Beta Test Starting task 17dc09ac.19671.10701.11.10.65_1 using setiathome_enhanced version 608
16/06/2010 22:59:58 SETI@home Beta Test Started upload of 17dc09ac.7891.9065.7.10.220_0_0
16/06/2010 23:00:05 SETI@home Beta Test Finished upload of 17dc09ac.7891.9065.7.10.220_0_0
16/06/2010 23:00:27 SETI@home Beta Test Computation for task 17dc09ac.7891.9065.7.10.210_0 finished
16/06/2010 23:00:27 SETI@home Beta Test Restarting task 17dc09ac.19671.1294.11.10.142_0 using setiathome_enhanced version 603
16/06/2010 23:00:29 SETI@home Beta Test Started upload of 17dc09ac.7891.9065.7.10.210_0_0
16/06/2010 23:00:37 SETI@home Beta Test Finished upload of 17dc09ac.7891.9065.7.10.210_0_0
16/06/2010 23:02:04 SETI@home Beta Test Computation for task 17dc09ac.19671.1294.11.10.142_0 finished
16/06/2010 23:02:04 SETI@home Beta Test Starting 24dc09aa.14770.2112.16.10.119_0
16/06/2010 23:02:04 SETI@home Beta Test Starting task 24dc09aa.14770.2112.16.10.119_0 using setiathome_enhanced version 603
16/06/2010 23:02:07 SETI@home Beta Test Started upload of 17dc09ac.19671.1294.11.10.142_0_0
16/06/2010 23:02:10 SETI@home Beta Test update requested by user
16/06/2010 23:02:12 SETI@home Beta Test Sending scheduler request: Requested by user.
16/06/2010 23:02:12 SETI@home Beta Test Reporting 5 completed tasks, requesting new tasks for CPU and GPU
16/06/2010 23:02:13 SETI@home Beta Test Finished upload of 17dc09ac.19671.1294.11.10.142_0_0
16/06/2010 23:02:38 Fetching configuration file from http://bam.boincstats.com/get_project_config.php

16/06/2010 23:02:41 SETI@home Scheduler request completed: got 2 new tasks
16/06/2010 23:02:43 SETI@home Started download of 17dc09ac.15550.14791.10.10.124
16/06/2010 23:02:43 SETI@home Started download of 17dc09ac.15550.14791.10.10.69


Edit: Ah just noticed another post on the same topic - message 1004878 http://setiathome.berkeley.edu/forum_thread.php?id=60375 - obviously a glitch in the Matrix.
____________
GPU Users Group



Profile LiliKrist
Volunteer tester
Avatar
Send message
Joined: 12 Aug 09
Posts: 333
Credit: 143,167
RAC: 0
Indonesia
Message 1004971 - Posted: 17 Jun 2010, 1:04:05 UTC

I have the same problem too =/


17/06/2010 7:53:57 SETI@home Beta Test update requested by user
17/06/2010 7:54:06 SETI@home Scheduler request completed: got 0 new tasks
17/06/2010 7:54:06 SETI@home Message from server: Project has no jobs available
17/06/2010 7:54:11 SETI@home Beta Test Sending scheduler request: Requested by user.
17/06/2010 7:54:11 SETI@home Beta Test Reporting 3 completed tasks, requesting new tasks
17/06/2010 7:54:21 SETI@home Scheduler request completed: got 0 new tasks
17/06/2010 7:54:21 SETI@home You used the wrong URL for this project
17/06/2010 7:54:21 SETI@home The correct URL is http://setiathome.berkeley.edu/
17/06/2010 7:54:21 SETI@home You seem to be attached to this project twice
17/06/2010 7:54:21 SETI@home We suggest that you detach projects named SETI@home,
17/06/2010 7:54:21 SETI@home then reattach to http://setiathome.berkeley.edu/
17/06/2010 7:54:21 SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
17/06/2010 7:54:21 SETI@home Consider detaching this project, then trying again
17/06/2010 7:54:21 SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project.
17/06/2010 7:55:01 SETI@home update requested by user
17/06/2010 7:55:02 SETI@home Sending scheduler request: Requested by user.
17/06/2010 7:55:02 SETI@home Reporting 3 completed tasks, requesting new tasks
17/06/2010 7:55:12 SETI@home Scheduler request completed: got 0 new tasks
17/06/2010 7:55:12 SETI@home You used the wrong URL for this project
17/06/2010 7:55:12 SETI@home The correct URL is http://setiathome.berkeley.edu/
17/06/2010 7:55:12 SETI@home You seem to be attached to this project twice
17/06/2010 7:55:12 SETI@home We suggest that you detach projects named SETI@home,
17/06/2010 7:55:12 SETI@home then reattach to http://setiathome.berkeley.edu/
17/06/2010 7:55:12 SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
17/06/2010 7:55:12 SETI@home Consider detaching this project, then trying again
17/06/2010 7:55:12 SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project.
17/06/2010 7:55:17 SETI@home Sending scheduler request: To fetch work.
17/06/2010 7:55:17 SETI@home Requesting new tasks
17/06/2010 7:55:27 SETI@home Scheduler request completed: got 0 new tasks
17/06/2010 7:55:27 SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
17/06/2010 7:55:27 SETI@home Consider detaching this project, then trying again

____________


N = R x fp x ne x fl x fi x fc x L

Highlander
Avatar
Send message
Joined: 5 Oct 99
Posts: 145
Credit: 31,427,355
RAC: 9,902
Germany
Message 1004981 - Posted: 17 Jun 2010, 1:35:35 UTC
Last modified: 17 Jun 2010, 1:42:30 UTC

Something similar and very weired happend here also:

dieser 45 SETI@home 17.06.2010 03:00:32 Scheduler request completed: got 0 new tasks 46 SETI@home 17.06.2010 03:00:32 Message from server: Project has no jobs available 47 SETI@home 17.06.2010 03:01:48 Sending scheduler request: To fetch work. 48 SETI@home 17.06.2010 03:01:48 Requesting new tasks for CPU 49 SETI@home Beta Test 17.06.2010 03:01:51 Scheduler request completed: got 0 new tasks 50 SETI@home Beta Test 17.06.2010 03:01:51 You used the wrong URL for this project 51 SETI@home Beta Test 17.06.2010 03:01:51 The correct URL is http://setiweb.ssl.berkeley.edu/beta/ 52 SETI@home Beta Test 17.06.2010 03:01:51 Using the wrong URL can cause problems in some cases. 53 SETI@home Beta Test 17.06.2010 03:01:51 When convenient, detach this project, then reattach to http://setiweb.ssl.berkeley.edu/beta/ 54 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Invalid app version description 55 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Invalid app version description 56 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Can't find host record


Since that time, Boinc Manager tells me, that im taking part @ Seti Beta ...
Never joined there (and no detach/attach game here), so failure msg is out of the air.
Hope they can clear this stuff up. Great luck, that i was not able to DL to much WUs to crunch (about 10), so that i can switch NNT on and do some more of my backup project, till the dust settles once again :-)

Edit:
Ups, seems, this was only a small hickup: after 2 manual updates, i'm back @ normal Seti ...
____________

Sidewinder
Avatar
Send message
Joined: 15 Nov 09
Posts: 65
Credit: 3,446,050
RAC: 0
United States
Message 1004987 - Posted: 17 Jun 2010, 1:58:55 UTC - in response to Message 1004981.

Something similar and very weired happend here also:

dieser 45 SETI@home 17.06.2010 03:00:32 Scheduler request completed: got 0 new tasks 46 SETI@home 17.06.2010 03:00:32 Message from server: Project has no jobs available 47 SETI@home 17.06.2010 03:01:48 Sending scheduler request: To fetch work. 48 SETI@home 17.06.2010 03:01:48 Requesting new tasks for CPU 49 SETI@home Beta Test 17.06.2010 03:01:51 Scheduler request completed: got 0 new tasks 50 SETI@home Beta Test 17.06.2010 03:01:51 You used the wrong URL for this project 51 SETI@home Beta Test 17.06.2010 03:01:51 The correct URL is http://setiweb.ssl.berkeley.edu/beta/ 52 SETI@home Beta Test 17.06.2010 03:01:51 Using the wrong URL can cause problems in some cases. 53 SETI@home Beta Test 17.06.2010 03:01:51 When convenient, detach this project, then reattach to http://setiweb.ssl.berkeley.edu/beta/ 54 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Invalid app version description 55 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Invalid app version description 56 SETI@home Beta Test 17.06.2010 03:01:51 Message from server: Can't find host record


Since that time, Boinc Manager tells me, that im taking part @ Seti Beta ...
Never joined there (and no detach/attach game here), so failure msg is out of the air.
Hope they can clear this stuff up. Great luck, that i was not able to DL to much WUs to crunch (about 10), so that i can switch NNT on and do some more of my backup project, till the dust settles once again :-)

Edit:
Ups, seems, this was only a small hickup: after 2 manual updates, i'm back @ normal Seti ...



Yep, same here. After a couple of manual update requests, S@H fixed itself.
____________

Richard HaselgroveProject donor
Volunteer tester
Send message
Joined: 4 Jul 99
Posts: 8633
Credit: 51,584,145
RAC: 48,674
United Kingdom
Message 1005192 - Posted: 17 Jun 2010, 11:29:17 UTC

Suggestion for Volunteer Testers receiving the "You seem to be attached to this project twice" error message - in other words, computers genuinely attached to both the main project and the Beta project.

Perform the following steps, in order:


  • Suspend networking activity
  • Shut down BOINC completely
  • Edit client_state.xml (yadda yadda, you're testers, you should know the drill by now)
  • Find the second SETI@home project section (the one with <master_url> http://setiweb.ssl.berkeley.edu/beta/)
  • Change the <project_name> to "SETI@home Beta Test"
  • Save changes and close
  • Restart BOINC
  • On the Projects tab, select the project you can now identify as SETI@home Beta Test, and suspend it.
  • Re-enable networking


Then wait until the project staff arrive in (their) morning. I've sent some diagnostic emails.

Profile Hellsheep
Volunteer tester
Send message
Joined: 12 Sep 08
Posts: 428
Credit: 784,780
RAC: 0
Australia
Message 1005199 - Posted: 17 Jun 2010, 11:52:06 UTC - in response to Message 1005192.

Suggestion for Volunteer Testers receiving the "You seem to be attached to this project twice" error message - in other words, computers genuinely attached to both the main project and the Beta project.

Perform the following steps, in order:

  • Suspend networking activity
  • Shut down BOINC completely
  • Edit client_state.xml (yadda yadda, you're testers, you should know the drill by now)
  • Find the second SETI@home project section (the one with <master_url> http://setiweb.ssl.berkeley.edu/beta/)
  • Change the <project_name> to "SETI@home Beta Test"
  • Save changes and close
  • Restart BOINC
  • On the Projects tab, select the project you can now identify as SETI@home Beta Test, and suspend it.
  • Re-enable networking


Then wait until the project staff arrive in (their) morning. I've sent some diagnostic emails.



Already done. :) Thanks though. :P

____________
- Jarryd

Terror Australis
Volunteer tester
Send message
Joined: 14 Feb 04
Posts: 1715
Credit: 205,818,781
RAC: 27,715
Australia
Message 1005238 - Posted: 17 Jun 2010, 13:10:05 UTC
Last modified: 17 Jun 2010, 13:12:26 UTC

I received the error on 2 machines that have never been connected to Beta. I was tipped off to the cause of the problem when Reschedule gave the following error

cannot find seti@home in the client_state.xml file

I checked the client state file and found this
<project>
<master_url>http://setiathome.berkeley.edu/</master_url>
<project_name>SETI@home Beta Test</project_name>
<symstore></symstore>
<user_name>Brodo</user_name>


Since I put it right I still get the "Your app_info.xml file doesn't have a usable version of SETI@home Enhanced." error and the "reached daily quota" error but there's one less line of red to deal with :-)

Can someone please explain how the error was created ?

Brodo

Richard HaselgroveProject donor
Volunteer tester
Send message
Joined: 4 Jul 99
Posts: 8633
Credit: 51,584,145
RAC: 48,674
United Kingdom
Message 1005385 - Posted: 17 Jun 2010, 20:50:43 UTC - in response to Message 1005192.

Then wait until the project staff arrive in (their) morning. I've sent some diagnostic emails.

The Beta server appears to be functional again (no announcement, even privately - that would be too much to hope).

There are even signs of a validator running, for the first time in 10 days.

Message boards : Number crunching : SETI@HOME and SETI beta acting up

Copyright © 2014 University of California