| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: No new tasks |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 30
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ah, well, that's 2 programs generating it full-out then... not exactly good reading when doing a fix assist.
|
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
1/31/2013 9:10:37 AM | World Community Grid | [work_fetch] fetch share 0.000 (blocked by prefs) This looks like you've set your WCG-preferences to not do CPU-work... One way to check if this is the case, in BOINC Manager, on the Projects-tab, select WCG and choose "Properties". Not getting CPU-work will show-up as: "Don't fetch tasks for CPU ...... Project preference".  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Found that same line suspicious [see earlier in this thread], but, he sean said he'd only have the trouble since the latest outage [Jan.29], where his log says the last website device profile change was Jan.22
1/31/2013 7:36:51 AM | World Community Grid | General prefs: from World Community Grid (last modified 22-Jan-2013 19:22:39) If this is the issue, having selected to not get CPU work, then the change did not update the global_prefs time stamp of the respective profile... that's ugly if so. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here's what it shows. I don't know why it would change to disallow cpu as I didn't touch a thing and only can run cpu on here.
---------------------------------------- [Edit 1 times, last edit by Former Member at Jan 31, 2013 7:51:21 PM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
If this is the issue, having selected to not get CPU work, then the change did not update the global_prefs time stamp of the respective profile... that's ugly if so. Disabling CPU-work is a Project-specific preference, meaning it should have zero effects on the Global preferences. Unfortunately, WCG have still not fixed this bug, toggling CPU on/off still incorrectly updates the global-prefs time-stamp.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sigh.
----------------------------------------Sean, Don't know why branjo in 2nd reply in thread suggested to open your device profiles and save them again, then hit update [These'things should not get changed by gremlins]. In your case do My Grid > Device Manager > Select Default. Under advanced options "Allow research to run on my CPU? " should say "Yes" and save, do an Update in the client and post the line that prints the profile date/time. It was 22 Jan before, and then should change to Jan.31 per Ingleside's theory. [Edit 1 times, last edit by Former Member at Jan 31, 2013 8:00:14 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That worked. But I have no idea how it just switched on me. Thanks for all the work and at least we all learned something new. *RESOLVED*
|
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges: 
|
Sigh. Sean, Don't know why branjo in 2nd reply in thread suggested to open your device profiles and save them again, then hit update [These'things should not get changed by gremlins]. In your case do My Grid > Device Manager > Select Default. Under advanced options "Allow research to run on my CPU? " should say "Yes" and save, do an Update in the client and post the line that prints the profile date/time. It was 22 Jan before, and then should change to Jan.31 per Ingleside's theory. Because I thought it could be somehow connected to this problem   Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006  [Edit 1 times, last edit by branjo at Jan 31, 2013 8:38:40 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Good linking. In hindcast, the Jan.22 timestamp of the profile being coincidental I suppose. The problem arose after the 29th outage. Just know that in fact, a number of changes to the WCG device profiles *do not* change the timestamp such as changing the project selections. I'll have to test the CPU Tasks Yes/No thing, r... it's a project specific pref, not something that belongs in the global prefs of home/default/work/school. Will report back [if I don't forget... now testing Ubuntu daily build, 13.04 and it *looks* spiffy [but is slow to load from the 3.0 USB stick].
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Having tested this CPU work Yes/ No, set it to No and hit Update which logged:
1/31/2013 10:43:22 PM | World Community Grid | General prefs: from World Community Grid (last modified 31-Jan-2013 22:43:09) Whatever the POV, at least the member gets told that a change was applied to the device profile. Begs the question why the 29th outage set this CPU work No off for Sean. When I select "Don't request more work" in the projects tab, the answer to the question changed to Yes. The message in the event log changed from Don't Need, to 1/31/2013 10:52:30 PM | World Community Grid | Not requesting tasks: "no new tasks" requested via Manager Which at least makes it clear it was a BM action. Enough for today, I'd say. TTYT |
||
|
|
|