| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: No more immediate upload/download? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 21
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hey,
I recently had to reinstall everything due to a dying hard drive. On my old system, when Boinc finished a work unit, it would immediately upload it and then immediately download the next one. Since reinstalling things, Boinc no longer does that. Sometimes it will do it soon after finishing and other times it just sits there and refuses to do anything until I force an update. I have 8 units being worked at once. Sometimes when I force an update, it will only download 1-2 units. I then have to repeat that over and over until it gets 8. The only work around right now I have found is to change how many units I download at a time. By having a larger cache of units, it sometimes can continuously run without having nothing to do. The only problem with that is that the Clean Energy project only gets done every now and then since it no longer replaces the unit from clean energy with another one and instead grabs another project. Very aggravating. I have it set to connect to the internet whenever it needs to. It's set as always available. The only thing different that I can tell is that I have a much newer version than the old machine because i had not updated it in a long time. Any ideas of how to get Boinc to go back to uploading/downloading when it finishes a unit? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
From BOINC: "Ready To Report" tasks status and how to understand them:
When RtR's are not cleared or new work is not fetched, it is possible that the client got confused. Frequent changing of profile settings & local preferences and repeated panic states (see discussions on High Priority / Earliest D Deadline First (EDF) processing, which can cause such conditions to develop). BOINC needs 1 or 2 weeks to find it's balance and understand *particularly* if multiple distributed computing grids are attached to the client. Best is to decide on what's wanted, make the changes and leave it be. talk to the hand Resist the urge to micromanage Hope this helps. As a side note, what's your setting for "% of CPU TIME"? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The only thing different that I can tell is that I have a much newer version than the old machine because i had not updated it in a long time. So, what version might that be? Would not say that the 6.13 alpha's are exactly production ready, and that one does have substantial different work fetch behavior. If it is, parts of the control files are not backward compatible to 6.12 and earlier, so you'd have to clean out BOINC and fetch a supported version. 6.10.58 is the one WCG prefers, but on Linux certainly had zero issue with 6.12.33. BTW. System date is something to check. New clients do start out with odd behavior, but if running 24/7 (Activity menu "Run Always", Network Always available", and preference set to "Connect every.... 0.00 days"). Things should balance soon, particularly if only working on WCG. Plz, don't set your additional buffer / cache too high. 1-2 Days is more than enough to meet any outage time WCG might have. And should it persist, post a good stretch of message log [without hitting the update button], so we can see the completion, uploading, reporting and fetch activities. Oh, and do run a benchmark via the advanced menu. That may have been borged. Do that when only BOINC is running and all other apps such as your browser are not loaded. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I recently updated to version 6.12.34 and added Seti to my projects, since then it will not return my results or get new tasks for WCG, msg is Scheduler request failed: failure when receiving data from the peer ?
Should I get rid of Seti? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The causal relation is more likely your upgrade of BOINC and not Seti. [6.12.34 and up have a known bug causing problems at WCG for some].
Plz post copy of the message log. 10 lines before and after that *peer* error (which often is caused by a wrong system date). Several Start Here FAQs exist with that *peer* keyword. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
since deleting all waiting transfers I have no further peer msgs but no Wcg projects running, just Seti, here is the log::
25/11/2011 10:59:00 | SETI@home | Started download of 14oc11aa.22903.17245.3.10.221 25/11/2011 10:59:06 | SETI@home | Finished download of 14oc11aa.22903.17245.3.10.221 25/11/2011 11:40:00 | World Community Grid | Sending scheduler request: Requested by project. 25/11/2011 11:40:00 | World Community Grid | Reporting 6 completed tasks, requesting new tasks for CPU 25/11/2011 11:40:01 | | Project communication failed: attempting access to reference site 25/11/2011 11:40:01 | World Community Grid | Scheduler request failed: Failure when receiving data from the peer 25/11/2011 11:40:02 | | Internet access OK - project servers may be temporarily down. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I see
25/11/2011 11:40:01 | World Community Grid | Scheduler request failed: Failure when receiving data from the peer Got a proxy somewhere? See this help item with the exact message: http://www.worldcommunitygrid.org/help/viewTopic.do?shortName=proxy Let us know. --//-- P.S. 6.12.34 caused some an issue with connecting to WCG, which 6.12.33 does not. To download just edit the download address you have for 6.12.34. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ok, I downloaded the current version and ran a repair, now I have lost WCG & Seti from my projects, the version number is now showing 6.10.58 and it has lost my proxy settings and will not allow me to update them all options are greyed out.........
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Don't think anything is lost, yet, and good you confirm it was a proxy acting up.
Not sure how you managed to run a repair of 6.10.58 over 6.12.34. Normally if downgrading to a lower version it will run as as a normal install and replace the newer (but wont work with the next client... compatibility issues.) Does BOINC Manager say it's connected to the localhost, right hand bottom? --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
ran the install again, chose the Remove option, then ran the install when finished, all up and running again with WCG & Seti on version 6.10.58
----------------------------------------[Edit 2 times, last edit by Former Member at Nov 28, 2011 10:49:14 AM] |
|||
|
||||
|
|