| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: Completed tasks not reporting |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 79
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Don't go standing behind that mule, they kick back hard
 |
||
|
|
asdavid
Veteran Cruncher FRANCE Joined: Nov 18, 2004 Post Count: 521 Status: Offline Project Badges: 
|
It works now:
----------------------------------------30/01/2015 12:46:47 | World Community Grid | update requested by user 30/01/2015 12:46:48 | World Community Grid | Sending scheduler request: Requested by user. 30/01/2015 12:46:48 | World Community Grid | Reporting 1 completed tasks 30/01/2015 12:46:48 | World Community Grid | Requesting new tasks for CPU 30/01/2015 12:46:51 | World Community Grid | Scheduler request completed: got 3 new tasks
Anne-Sophie
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi.
----------------------------------------I started having problems some time last week to, I'm having trouble downloading as well they start then stop, then start again taking longer to get tasks. Sun 01 Feb 2015 09:52:22 AEDT | World Community Grid | Requesting new tasks for CPU Sun 01 Feb 2015 09:52:25 AEDT | World Community Grid | Scheduler request completed: got 8 new tasks Sun 01 Feb 2015 09:52:27 AEDT | World Community Grid | Started download of ugm1.ugm1_ugm1_07489_a_0013.txt.gzb Sun 01 Feb 2015 09:52:27 AEDT | World Community Grid | Started download of ugm1.ugm1_ugm1_07489_b_0000.txt.gzb Sun 01 Feb 2015 09:57:28 AEDT | | Project communication failed: attempting access to reference site Sun 01 Feb 2015 09:57:28 AEDT | World Community Grid | Temporarily failed download of ugm1.ugm1_ugm1_07489_a_0013.txt.gzb: transient HTTP error Sun 01 Feb 2015 09:57:28 AEDT | World Community Grid | Temporarily failed download of ugm1.ugm1_ugm1_07489_b_0000.txt.gzb: transient HTTP error edit // Website is slower at times to, not having any problem with any others.  [Edit 1 times, last edit by Former Member at Jan 31, 2015 11:17:17 PM] |
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 786 Status: Offline Project Badges: 
|
I had the same, http errors and slow downloads from around 22:50 to 23:20 UTC.
----------------------------------------Now running at full speed again. Paul.
Paul.
|
||
|
|
asdavid
Veteran Cruncher FRANCE Joined: Nov 18, 2004 Post Count: 521 Status: Offline Project Badges:
|
Feeder Problem is coming again
----------------------------------------09/02/2015 17:02:27 | World Community Grid | Reporting 4 completed tasks 09/02/2015 17:02:27 | World Community Grid | Requesting new tasks for CPU 09/02/2015 17:02:29 | World Community Grid | Scheduler request completed: got 0 new tasks 09/02/2015 17:02:29 | World Community Grid | Server error: feeder not running (My time is UTC +1) It is not systematic (occurring several times, then working, then coming back: not working during the night, ok in the morning, and KO again now) I do not have idea of how to make it work from my side 
Anne-Sophie
|
||
|
|
Steve W
Advanced Cruncher Joined: Dec 9, 2005 Post Count: 110 Status: Offline Project Badges: 
|
OK. Just to make sure this is recorded as an ongoing intermittent thing one of my machines was apparently getting the message again yesterday:
17/02/2015 23:10:50 | World Community Grid | Server error: feeder not running Looking at the logs it seems to have cleared itself by 18/02/2015 10:10 but it does mean another almost 12 hours unable to contact the server to report or request work. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Recommend to run with Minimum Buffer of 1.0 days, additional work buffer 0.0. This way you get a trickle backfill as work completes and are pretty much set to bridge any transient and longer hick-ups and outages, to include these 'feeder not running' bugs.
----------------------------------------As to the reporting, there's 2 parts 1) The uploading of the result files, which is normally immediate if having a standing connection. 2) The Ready to Report confirmation that does not happen until the completion of 1) is confirmed. Latter is of lesser urgency, does not hold up new work requesting, which the former can, if there are too many uploads stalled (2 times CPU threads). As said though, with a 1 day buffer there's hardly ever an 'out of work, idle cores' issue. [Edit 1 times, last edit by Former Member at Feb 18, 2015 10:50:18 AM] |
||
|
|
Steve W
Advanced Cruncher Joined: Dec 9, 2005 Post Count: 110 Status: Offline Project Badges:
|
I just increased the buffer as suggested to make sure I have plenty of work for when these issues occur and when it went to fetch additional work:
18/02/2015 11:17:11 | World Community Grid | Server error: feeder not running Aaarrgh! |
||
|
|
Steve W
Advanced Cruncher Joined: Dec 9, 2005 Post Count: 110 Status: Offline Project Badges:
|
OK, so still no new work since my last post. Just the server error message.
On a side note looking at SekeRobs message, tasks upload fine. It is the reporting of completed tasks and requesting of new tasks which fails. There is the entry in the logs stating that it is "Reporting x completed tasks" and another "Requesting new tasks for CPU" but then the response is: 18/02/2015 16:04:22 | World Community Grid | Scheduler request completed: got 0 new tasks So even though the scheduler request is complete, no new tasks fetched and it doesn't report the task as complete. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Got a sticky on the side of my display with 3 DNS IPs,
1) The automatic ISP IPs 2) Googles 3) OpenDNS Whenever I have funnies, slow, no connecting with parts of WCG, I alternate, by putting the next set on the list into the Router. This refreshes all paths to and from. On the feeder message, it could still be a bug when a fail-over does not drop back to main. That's uplinger/chenna department to sort, or loose business. At some point in time there was something along the line of being locked to the bad half of the 2 servers. Loaded the main comps stdoutdae.txt and stdoutdae.old logs going back to Jan.19, and find not a single entry with 'feeder' in there. Riddled. |
||
|
|
|