System says using wrong url, than tells me it can't find host record, invalid or missing account key. Then it tells me to detach and reattach to project. How does this get fixed? Patrick
Same problem here, but only 2 to upload
2/24/2010 6:58:30 PM SETI@home Sending scheduler request: To report completed tasks.
2/24/2010 6:58:30 PM SETI@home Reporting 2 completed tasks, not requesting new tasks
2/24/2010 6:58:35 PM SETI@home Scheduler request completed
2/24/2010 6:58:35 PM SETI@home You used the wrong URL for this project
2/24/2010 6:58:35 PM SETI@home The correct URL is http://setiathome.berkeley.edu/
2/24/2010 6:58:35 PM SETI@home You seem to be attached to this project twice
2/24/2010 6:58:35 PM SETI@home We suggest that you detach projects named SETI@home,
2/24/2010 6:58:35 PM SETI@home then reattach to http://setiathome.berkeley.edu/
2/24/2010 6:58:35 PM SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
2/24/2010 6:58:35 PM SETI@home Consider detaching this project, then trying again
2/24/2010 6:58:35 PM SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project.
____________
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
My machine has completed a Scheduler Request. Hopefully things will return to "normal" if there is sucha a thing around here.
Regards
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
My machine has completed a Scheduler Request. Hopefully things will return to "normal" if there is sucha a thing around here.
Regards
Well, check the Q&A. My machine now thinks that Beta is the main project.
____________
Mine as well.
____________
Me too, and there's this non-reassuring "Database Error" message sitting above the messages on forum pages, and for that matter while I'm writing this reply the message is just under the thread name.
And since I can't report any of my complete wus, I have no RAC and am surprised it let me post at all...
We do appear to be back but as you say where?. just reported the following WU's after restart due to one of bills updates.
25/02/2010 08:57:59 Starting BOINC client version 6.10.19 for windows_intelx86
25/02/2010 08:57:59 log flags: file_xfer, sched_ops, task
25/02/2010 08:57:59 Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
25/02/2010 08:57:59 Data directory: C:\ProgramData\Boinc
25/02/2010 08:57:59 Running under account advent9509
25/02/2010 08:57:59 Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU @ 2.40GHz [x86 Family 6 Model 15 Stepping 7]
25/02/2010 08:57:59 Processor: 4.00 MB cache
25/02/2010 08:57:59 Processor features: fpu tsc pae nx sse sse2 pni mmx
25/02/2010 08:57:59 OS: Microsoft Windows Vista: Home Premium x86 Edition, Service Pack 2, (06.00.6002.00)
25/02/2010 08:57:59 Memory: 2.00 GB physical, 4.23 GB virtual
25/02/2010 08:57:59 Disk: 291.25 GB total, 183.54 GB free
25/02/2010 08:57:59 Local time is UTC +0 hours
25/02/2010 08:57:59 NVIDIA GPU 0: GeForce GT 220 (driver version 19562, CUDA version 3000, compute capability 1.2, 1024MB, 131 GFLOPS peak)
25/02/2010 08:57:59 SETI@home Found app_info.xml; using anonymous platform
25/02/2010 08:57:59 Not using a proxy
25/02/2010 08:58:00 AQUA@home URL http://aqua.dwavesys.com/; Computer ID 34784; resource share 100
25/02/2010 08:58:00 Leiden Classical URL http://boinc.gorlaeus.net/; Computer ID 73017; resource share 100
25/02/2010 08:58:00 FreeHAL@home URL http://freehal.net/freehal_at_home/; Computer ID 20348; resource share 100
25/02/2010 08:58:00 SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5310019; resource share 100
25/02/2010 08:58:00 SETI@home Beta Test URL http://setiweb.ssl.berkeley.edu/beta/; Computer ID 23245; resource share 100
I have suspeded work for now
7462603 2574983 25 Feb 2010 0:07:30 UTC 25 Feb 2010 8:59:06 UTC Validate error 2,822.95 210.63 115.48 --- SETI@home Enhanced v6.09 (cuda23)
7462600 2577329 25 Feb 2010 0:07:30 UTC 25 Feb 2010 8:59:06 UTC Validate error 1,828.93 135.52 65.93 --- SETI@home Enhanced v6.09 (cuda23)
7462579 2439243 25 Feb 2010 0:07:30 UTC 25 Feb 2010 8:59:06 UTC Validate error 3,541.41 235.11 124.74 --- SETI@home Enhanced v6.09 (cuda23)
7462529 2575381 25 Feb 2010 0:07:30 UTC 25 Feb 2010 8:59:06 UTC Validate error 12,636.82 213.82 189.40 --- SETI@home Enhanced v6.09 (cuda23)
7011924 2442733 14 Dec 2009 19:49:35 UTC 29 Dec 2009 0:50:30 UTC Validate error 26,773.15 22,492.63 78.67 --- SETI@home Enhanced v6.03
Michael
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
Mine after sitting trying to get the master file from the scheduler, managed to reconnect on its own. Is anyone else still having the problem?
Regards
Edit:
The Database error has been corrected.
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
Yes.
2/25/2010 2:18:37 PM SETI@home Sending scheduler request: To report completed tasks.
2/25/2010 2:18:37 PM SETI@home Reporting 2 completed tasks, not requesting new tasks
2/25/2010 2:18:42 PM SETI@home Scheduler request completed
2/25/2010 2:18:42 PM SETI@home You used the wrong URL for this project
2/25/2010 2:18:42 PM SETI@home The correct URL is http://setiathome.berkeley.edu/
2/25/2010 2:18:42 PM SETI@home You seem to be attached to this project twice
2/25/2010 2:18:42 PM SETI@home We suggest that you detach projects named SETI@home,
2/25/2010 2:18:42 PM SETI@home then reattach to http://setiathome.berkeley.edu/
2/25/2010 2:18:42 PM SETI@home Already attached to a project named SETI@home (possibly with wrong URL)
2/25/2010 2:18:42 PM SETI@home Consider detaching this project, then trying again
2/25/2010 2:18:42 PM SETI@home Message from server: Invalid or missing account key. To fix, detach and reattach to this project.
____________
Still have the problem.
____________
Still have the problem.
Here too, the client data is trashed for seti beta, showing it as main project still. Methinks manual edit is necessary, and someone has asked that question over in Q&A but there's been no response.
Edit: fwiw I fixed the scheduler URL and project name in my client_state.xml, looking at the copy from an older boinc data backup for correct info. These appeared to be the only two fields that had been changed.
Still can't report the work of course, but I'm no longer getting errors, just the "project servers may be temporarily down" (no kidding). Suspended the project again until the scheduler is back up.
E.g.:
2/25/2010 15:01:28 SETI@home Beta Test update requested by user
2/25/2010 15:01:32 SETI@home Beta Test Sending scheduler request: Requested by user.
2/25/2010 15:01:32 SETI@home Beta Test Reporting 17 completed tasks, not requesting new tasks
2/25/2010 15:01:33 Project communication failed: attempting access to reference site
2/25/2010 15:01:35 Internet access OK - project servers may be temporarily down.
2/25/2010 15:01:37 SETI@home Beta Test Scheduler request failed: Server returned nothing (no headers, no data)
looks MUCH better than the identity crisis it was reporting earlier.
____________
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
generally, if the server can not be contacted for a while it tries to get the master url from the scheduler.
As far as your authenicator, that should be left alone.
From the Client_State.xml for the Seti Beta section should look like this
<project>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<project_name>SETI@home Beta Test</project_name>
<symstore></symstore>
<user_name>Pappa</user_name>
<team_name>HT</team_name>
Your account is in
account_setiweb.ssl.berkeley.edu_beta.xml
<account>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<authenticator>1e7ab27b980aebac841ab12437a368a9</authenticator>
<project_name>SETI@home Beta Test</project_name>
<project_preferences>
The authenticator you can get from Your Account page on Seti Beta. I tend to keep a copy hanging around for emergency's
Regards
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
I wasn't able to convince the 2nd Seti@Home that is should be Seti@Home Beta Test.
I had to delete "client_state_prev.xml" so the changes I made in the main one would take effect. Then each time it connected it just switched back from Seti@Home Beta Test to Seti@Home.
Ended up just detatching.
generally, if the server can not be contacted for a while it tries to get the master url from the scheduler.
As far as your authenicator, that should be left alone.
From the Client_State.xml for the Seti Beta section should look like this
<project>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<project_name>SETI@home Beta Test</project_name>
<symstore></symstore>
<user_name>Pappa</user_name>
<team_name>HT</team_name>
Your account is in
account_setiweb.ssl.berkeley.edu_beta.xml
<account>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<authenticator>1e7ab27b980aebac841ab12437a368a9</authenticator>
<project_name>SETI@home Beta Test</project_name>
<project_preferences>
The authenticator you can get from Your Account page on Seti Beta. I tend to keep a copy hanging around for emergency's
Regards
found my client state saying
the account file seems in order as is.
Fingers crossed.
Failed, log is:
And the client state is back to saying it is the main project.
____________
found my client state saying
<project>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<project_name>SETI@home</project_name>
<symstore></symstore>
...
<scheduler_url>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</scheduler_url>
the account file seems in order as is.
Over in Main John McLeod VII said something and I checked,
the <scheduler_url> line needs to be changed as well in addition to what Pappa has said.
The above two are the key lines. After I changed both I got my work units reported. I'm a happy camper, but I've go no idea how many beta users may not yet know they have a problem. Perhaps a better write up and sticky it for a while.
____________
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
I am not sure how I can formulate a Bug report to Boinc Alpha.
For myself, I Suspened everything until uploads started to happen. I did see Seti Beta get to the point where a Master File request happened and looked a files and saw some things Zero'd.
In the mean time I was doing backup projects (still waiting for everything to clear, grrhhhhh). Seti Beta was offline to allow for Seti Main.
I do know that "Web" was redirected, DNS changes (short term). There are still database issues with accessing many things. Part, I suspect are permissions for related tables and part are corrupted (or gone) tables.
So the big part is, my account xml file still held the Scheduler URL and my Account Key.
So we may never know how big the crash "was." We might get/have hints.
For myself, if the Tech News actaully told how bit the crash was, Users might (yes that is a big assumption) be more tolerant. At least they have information. Communcations is key working thourgh issues.
Regards
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
I am not sure how I can formulate a Bug report to Boinc Alpha.
For myself, I Suspened everything until uploads started to happen. I did see Seti Beta get to the point where a Master File request happened and looked a files and saw some things Zero'd.
In the mean time I was doing backup projects (still waiting for everything to clear, grrhhhhh). Seti Beta was offline to allow for Seti Main.
I do know that "Web" was redirected, DNS changes (short term). There are still database issues with accessing many things. Part, I suspect are permissions for related tables and part are corrupted (or gone) tables.
So the big part is, my account xml file still held the Scheduler URL and my Account Key.
So we may never know how big the crash "was." We might get/have hints.
For myself, if the Tech News actaully told how bit the crash was, Users might (yes that is a big assumption) be more tolerant. At least they have information. Communcations is key working thourgh issues.
Regards
Pappa,
I don't really think it is a BOINC alpha bug report type of thing. I think it is more of a warning to BOINC project admin's to be sure they don't redirect via DNS from one project to another. JM7 said the scheduler URL is an embed in the home page so with the redirect the client state file gets corrupted. This isn't a program bug as much as a staff configuration error. Not sure there is an automated way to right the situation now without making a bigger mess. Only thing might be special error messages for the log file. I wouldn't ask anyone to write a special scheduler to check the account key in another project!
Fortunately more people who run Beta check their machines, so they may see it in their log files. Unfortunately the suggested fix in the log tosses away any pending work units. If they are lucky they look at the project pages for a fix first.
Perhaps Eric or Dr. A might have an idea on this. Personally I think it is worthy of a note on the beta project home page. At least a mea culpa if nothing else. I am tolerant. I know that repairs frequently make things worse before they get better. They had to get a message up and I understand. If it ever is needed again, hopefully the same error won't be made again. All one can ask. Learn from the school of hard knocks. At least we seem to have a work around. If the word about that gets circulated it is all we can do.
____________
You guys need to fix this, in a few days I'm going to lose 1100 completed Wu's
System says using wrong url, than tells me it can't find host record, invalid or missing account key. Then it tells me to detach and reattach to project. How does this get fixed? Patrick
You guys need to fix this, in a few days I'm going to lose 1100 completed Wu's
System says using wrong url, than tells me it can't find host record, invalid or missing account key. Then it tells me to detach and reattach to project. How does this get fixed? Patrick
Don't detach. That throws away the work!
I don't think they -- seti staff -- can fix it without unfixing everyone in the main project. Obviously that isn't acceptable. That means, you are going to have to fix it by hand.
If you want to save your work units check and edit as per Pappa's note
and also check and edit per my note
All I can tell you is that fixed me. I think it should work for everyone, but I'm not a BOINC developer so I'm shot-gunning.
If you try it, please let us all know if it works or not.
____________
found my client state saying
<project>
<master_url>http://setiweb.ssl.berkeley.edu/beta/</master_url>
<project_name>SETI@home</project_name>
....
the account file seems in order as is.
According to some yesterday's notes, I've tried to change the <project_name> already yesterday - it cured the initial client's warnings about duplicate projects, but worked just until the next scheduler request (now it is understandable why), so I've "repaired" the name again and temporarily suspended the Beta.
Over in Main John McLeod VII said something and I checked,
the <scheduler_url> line needs to be changed as well in addition to what Pappa has said.
<project_name>SETI@home Beta Test</project_name> ... <scheduler_url>http://setiboinc.ssl.berkeley.edu/beta_cgi/cgi</scheduler_url>
The above two are the key lines. After I changed both I got my work units reported. I'm a happy camper...
Yes, changing also the scheduler's URL cured my client completely and it was able to report finished tasks.
Thanks all of you!