| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: Auto Opt-In Didn't Work |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
I checked into my small farm this morning and found that I had forgotten to feed my starving lil crunchers some FAAH WUs. I had left the project selection settings on Beta-only. Of my 3 crunchers, one had run completely dry and another (a 2-core unit) had just 1 beta WU. The third was chewing on 2 beta WUs (1 per core).
----------------------------------------I had auto opt-in selected and the new MCM project had been enabled by the script, but I had not gotten any MCM work. I turned off the MCM setting, saved, turned it back on, and saved again. Almost immediately my queues started filling up with new work. Something is not working right with the auto opt-in script. Cheers   |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
I checked into my small farm this morning and found that I had forgotten to feed my starving lil crunchers some FAAH WUs. I had left the project selection settings on Beta-only. Of my 3 crunchers, one had run completely dry and another (a 2-core unit) had just 1 beta WU. The third was chewing on 2 beta WUs (1 per core). I had auto opt-in selected and the new MCM project had been enabled by the script, but I had not gotten any MCM work. I turned off the MCM setting, saved, turned it back on, and saved again. Almost immediately my queues started filling up with new work. Something is not working right with the auto opt-in script. Cheers FWIW it worked fine on all my machines. Could you have an incorrect setting?
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges:
|
FWIW it worked fine on all my machines. Could you have an incorrect setting? Hi nanoprobe. Do you have an example of what you are thinking/suggesting?The fix was easy. I turned off the MCM setting and turned it back on. I didn't change anything else. The script that the techs ran yesterday turned it on. Before Fix: 9435 World Community Grid 11/9/2013 8:54:02 AM Sending scheduler request: To fetch work. 9436 World Community Grid 11/9/2013 8:54:02 AM Requesting new tasks for CPU 9437 World Community Grid 11/9/2013 8:54:03 AM Scheduler request completed: got 0 new tasks 9438 World Community Grid 11/9/2013 8:54:03 AM Message from server: No tasks sent 9439 World Community Grid 11/9/2013 8:54:03 AM Message from server: No tasks are available for the applications you have selected. After Fix (and filling queue): 9530 World Community Grid 11/9/2013 9:04:59 AM Sending scheduler request: To fetch work. 9531 World Community Grid 11/9/2013 9:04:59 AM Requesting new tasks for CPU 9532 World Community Grid 11/9/2013 9:05:01 AM Scheduler request completed: got 0 new tasks 9533 World Community Grid 11/9/2013 9:05:01 AM Message from server: No tasks sent 9534 World Community Grid 11/9/2013 9:05:01 AM Message from server: No tasks are available for Mapping Cancer Markers 9535 World Community Grid 11/9/2013 9:05:01 AM Message from server: No tasks are available for the applications you have selected. 9536 World Community Grid 11/9/2013 9:05:01 AM Message from server: This computer has finished a daily quota of 5 tasks It appears that although the project was selected, the feeder wasn't recognizing it. Cheers [edited to highligh change in server message] [Edit 1 times, last edit by NixChix at Nov 9, 2013 10:10:36 PM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
During the time I was receiving betas only I had the "Please opt me into new projects as they become available" checked for all my device profiles. When the MCM1 tasks went live I started receiving tasks without any further intervention on my part. Could you have not selected the opt in option for the profile you were running at the time the project started? If you did then I have no answer as to why you didn't start getting them automatically.
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
mmstick
Senior Cruncher Joined: Aug 19, 2010 Post Count: 151 Status: Offline Project Badges: 
|
There are no tasks available and hasn't been for some time now.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well I am getting new ones, just got 4.......
|
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges:
|
I did have opt-in automatically set and I did get automatically set. However, my crunchers had empty queues and were asking for work as the log excerpt above shows. I did not get work for MCM until I unchecked the box and then rechecked. One can see how the status message changed after that. The feeder didn't think it was selected.
----------------------------------------If any of techs or admins care to check into it... otherwise I don't have anything else to share about it. Cheers |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Are you sure it didn't opt-in?
http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,35788 Looks to me you ran out of MCM |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges:
|
Are you sure it didn't opt-in? That's just it. It did automatically opt-in, but that didn't start the flow going. The project selection was automatically set in all my profiles by the script. MCM and Beta were the only projects selected. However, my queue were dry; I had 10 cores out of 12 just idling. My clients were asking for work, but the feeder wasn't sending any MCM work. I reset the MCM selection on the profile that I am currently using; only then did the feeder start sending MCM work until it reached the daily quota.http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,35788 Looks to me you ran out of MCM You can see the difference in the server messages above. It clearly shows that the feeder didn't think the project was selected. Resetting the project selection is the only thing I did to get the flow to start (besides many client refreshes and some colorful words). Cheers [Edit 1 times, last edit by NixChix at Nov 11, 2013 6:19:05 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello NixChix,
I am just guessing here. The website has a data structure containing your projects, but it only sends a copy of this structure to your BOINC program if it is requested. When BOINC starts on your computer, it requests this information from the server. I think that your computers were already running when the change was made on the website. A manual UPDATE would solve this problem quickly. Alternatively, BOINC may have some flag to update the projects and other settings the next time the BOINC client makes a scheduler request which was not set this time. But I can not remember hearing of such a flag. But logically it should exist. So something went wrong. Either the script was incorrectly designed and did not set the hypothetical update flag or the BOINC server code is incorrectly designed. I am betting on the script.  Lawrence |
||
|
|
|