| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Invalid or missing account key [RESOLVED] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Curly2
Cruncher Joined: Nov 24, 2008 Post Count: 10 Status: Offline Project Badges: 
|
I got this message on a host attached via BAM with the weak authenticator:
----------------------------------------14.03.2012 09:02:01 World Community Grid Sending scheduler request: Requested by user. 14.03.2012 09:02:01 World Community Grid Requesting new tasks 14.03.2012 09:02:01 World Community Grid [sched_op_debug] CPU work request: 72000.72 seconds; 0 idle CPUs 14.03.2012 09:02:07 World Community Grid Scheduler request completed: got 0 new tasks 14.03.2012 09:02:07 World Community Grid [sched_op_debug] Server version 700 14.03.2012 09:02:07 World Community Grid Message from server: Invalid or missing account key. To fix, remove and add this project . 14.03.2012 09:02:07 World Community Grid Project requested delay of 3600 seconds Device id is 1258797, BOINC version 6.10.18 on WinXP 32bit. Detaching and reattaching didn't help, either through BAM or directly in BOINC Manager (everything with weak authenticator). It's the first this host to request for new tasks after the BOINC upgrade on the WCG project. Other hosts (attached with email/password) work properly. So what's wrong?  [Edit 2 times, last edit by Curly2 at Mar 14, 2012 8:31:11 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Don't know. Why use the weak key and not the proper account key, while attaching to your own account? See FAQ: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=4925#164717
Far as I know, unless the client was originally manually successfully attached to WCG, BAM will not be able to do the attach, often in fact detaching WCG unless the default flag is set to attach WCG to a new host. Certainly don't know how you attach through BOINC Manager using the weak key as what you wrote "either through BAM or directly in BOINC Manager (everything with weak authenticator)". Latter uses member name / password for WCG, not email/password. --//-- |
||
|
|
Curly2
Cruncher Joined: Nov 24, 2008 Post Count: 10 Status: Offline Project Badges:
|
Don't know. Why use the weak key and not the proper account key, while attaching to your own account? See FAQ: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=4925#164717 There are some good reasons using the weak authenticator. Far as I know, unless the client was originally manually successfully attached to WCG, BAM will not be able to do the attach, often in fact detaching WCG unless the default flag is set to attach WCG to a new host. Previously the host was successfully attached to WCG via BAM and the weak authenticator. I set to "no new work" some days ago to do other projects. The message came up when I allowed new work again. The host was attached to BAM and WCG all the time. Certainly don't know how you attach through BOINC Manager using the weak key as what you wrote "either through BAM or directly in BOINC Manager (everything with weak authenticator)". Latter uses member name / password for WCG, not email/password. Attaching with weak authenticator to BAM means using the weak authenticator as username and password. Checking the attach checkbox for a project means attaching this project using the weak authenticator. This works for some projects (that support the weak authentication) but not for all. I got it running again by attaching WCG manually with the weak authenticator. So it's not a problem for me anymore. [Edit 1 times, last edit by Curly2 at Mar 14, 2012 2:47:33 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
OK, well associating BOINC on public computer has kind of my reservation v.v. ownership and authorization to install. I'm sure it is all above board though.
Since the issue is closed, please edit the opening post title and insert [RESOLVED] as I did to my post, so all visitors know the issue is done. Happy crunching. --//-- |
||
|
|
|