Restarting message. |
![]() |
| log in |
Questions and Answers : Wish list : Restarting message.
| Author | Message |
|---|---|
|
I am getting a message about restarting a particular work unit as follows | |
| ID: 698804 · | |
|
It doesn't. It tells you that the Seti application is doing its hourly switch with any other project's application. Only those projects which tasks run for under the amount of 'switch every x minutes' and those running through a wrapper, will not show this behaviour as they'll run in one sweep. | |
| ID: 698890 · | |
|
Ok. Thanks again for your help! | |
| ID: 698918 · | |
|
I would like to question that theory. I do not have that option set yet one of my units keeps switching as described by the original poster. I have three units in my tasks list yet only one keeps switching back to zero, not any other percentage, just zero. Im getting extremely fustrated as its now spent 5 hours and never reached above 7%. Yet in the same time the other two have reached around 40% and only one of them runs at a time. If this is an issue for multiple users then the team needs to have a look at the units as there is clearly a problem. If anyone can help, contact me at hainus1@hotmail.com Thanks | |
| ID: 709314 · | |
|
Just abort the task that is returning to zero percent. It'll probably be something in the task that doesn't like to be checkpointed or otherwise do what it's supposed to. | |
| ID: 709320 · | |
|
Something has come up on this. If you still have the problem, do you use BOINC's CPU throttling? | |
| ID: 712156 · | |
|
Ageless, | |
| ID: 712846 · | |
I've been using CPU throttling almost for ever (at least on my laptops) and it's been more than 6 months now that it gives me no issues whatsoever. What has come up in regards to restarting? When using CPU throttling, tasks would tend to restart. Especially on systems that were only attached to one project. A fix should be in 5.10.42, which can be gotten from http://boinc.berkeley.edu/download_all.php Anyone still reading and having the problem, please try it out and report back. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 713043 · | |
When using CPU throttling, tasks would tend to restart. Especially on systems that were only attached to one project. Nope, never had that problem, at least on the throttled machines, all running OSX. As I said earlier, I used to have a restarting issue (exit with zero status), but that was due to sync-DNS-lookups forcing hartbeat to fail and it's another problem. 5.10.42 brought async-DNS-lookups from what I can see, thus eliminating restarting tasks completely for me. What the other people are talking about is stubborn WUs which occasionally get through the checkup servers, that refuse to get over a CERTAIN % no matter what. ____________ | |
| ID: 713099 · | |
|
Also about the time of 5.10.42, there was a fix to directory scans in BOINC. Instead of opening each and every file to get the file size, the information is retrieved from the directory. This cut the time to find the total size of a directory from > 120 seocnds to < 1 second on one of my computers. This 120 seconds was longer than the heartbeat so every 2 to 3 minutes there would be a 2 minute pause - wihch restarted the task that was running. | |
| ID: 713654 · | |
|
I guess you have hundreds of tasks waiting to run... Wow ((c)Neo)... | |
| ID: 713779 · | |
I guess you have hundreds of tasks waiting to run... Wow ((c)Neo)... Actually, no. It was one project that insisnted on having a few thousand files per task... ____________ BOINC WIKI | |
| ID: 713786 · | |
Questions and Answers : Wish list : Restarting message.
| Copyright © 2013 University of California |