| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc Version 6.10.17 has been released |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 34
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
A quick follow up.
Now LTD is at zero, you shouldn't hit the same problem again. You are exactly correct! After the client dug itself out of the "Work Fetch Priority" hole, it started and is now working very much like version 6.2.15. My confidence for 6.10.17 is now very high so I plan to leave it running on this machine indefinitely and will try cache changes and maybe switching GPU back on once I know WCG works properly. no idea about the FIFO-issue, hopefully they'll run more or less in order now... Fifo seems to be generally working fine now. It did skip down about 3 WU's a while ago but quickly back filled in between so at least the oldest WU's are getting the attention in time. Thanks much for the info as I now see how this client works compared to prior ones. PS: my Father was born in Oslo  |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges: 
|
It's just that AFAIK none of the v6.2.xx-managers, including the WCG-one, can specify #cpu, so how do you manage in your local preferences to override the "use lowest of #cpu and %cpu"? (without manually editing the override-file that is). You are right, my words "the second line is what matters" meant that it is the only one you can change. But the migration feature of 6.2.28 is still there and picks the other parameter from the website profile.I have edited by initial post which now reads If you are using BOINC's local preferences the second parameter is the only one you can override but the migration feature of 6.2.28 is still taking the lower of both parameters, therefore you must still make sure that the line On multiprocessors, at most use: 8 processors is correctly set in the website profile associated with this device. Thanks for catching this mistake. Jean. |
||
|
|
lfc-rule
Cruncher Joined: Mar 26, 2009 Post Count: 2 Status: Offline Project Badges: 
|
Come across from windows and cannot get the BOINC (latest release) for intel Mac to work.
the programme sticks at the point when it states in the client manager retrieving current status. the grey box states communicating with the BOINC client. Any ideas ? |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
Come across from windows and cannot get the BOINC (latest release) for intel Mac to work. the programme sticks at the point when it states in the client manager retrieving current status. the grey box states communicating with the BOINC client. Any ideas ? Unfortunately windows-only, so can only guess it's mostly similar on Mac... If you've got lots of tasks, it can take some seconds before responds. But if you've waited a minute or something it's unlikely this is the problem. Firewall or virus-scanners? If there is something like this on Mac, check they're not interferring... Not enough access-rights? If you're not running as administrator, it's possible this is a problem. Uninstall & re-install making sure "everyone" can run will maybe fix this (there was something about Snow Leopard and access-rights, but not sure how the solution for this works in case you're using SL...) Screwed-up installation? Try doing a repair of BOINC. Also, atleast for some problems on windows, a re-boot works, so try this on the Mac also...  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
lfc-rule
Cruncher Joined: Mar 26, 2009 Post Count: 2 Status: Offline Project Badges:
|
Come across from windows and cannot get the BOINC (latest release) for intel Mac to work. the programme sticks at the point when it states in the client manager retrieving current status. the grey box states communicating with the BOINC client. Any ideas ? Sorry guy/girls i feel a bit stupid. A simple reboot fixed the problem. A cure for cancer is back on course!!!!!!! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, if it's due to a current lack of HFCC and nothing else, changing clients won't change the behaviour. Increasing "additional..." cache-setting to maybe 1 day will probably help in this instance, since less chance of running-out of work before manages to re-fill with work. If "no work available" is accompanied with something else besides listing the sub-project being out of work, please post the relevant messages showing this. The message I had been getting with 6.6.36 is an message at the top of the simple view window saying ERROR and no indication that this error was due to "no work available". When I go to advanced view to use update for the project, I get work immediately. I did update to 6.10.17 on both of my machines and I have not had this condition occur since that time. It also looks like I am able to get more WUs for whatever "sub-project" I am working on. Thanks for all of the help, Dave [Edit 1 times, last edit by Former Member at Nov 5, 2009 4:06:57 PM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
V6.10.18 for windows is now released, containing the following changes:
----------------------------------------Rom 5 November 2009 - MGR: Use mixed case keyboard accelerators instead of all caps, the wxGetTranslation function is case sensitive even though the rest of the menu code does not care about case. Rom 6 November 2009 - Update to OpenSSL 0.9.8l All new translations for all languages are included in this release. So basically only a couple cosmetic changes, and there's little reason to upgrade from v6.10.17. Appart for the known bug with Aqua, there's been very few reported problems, especially since 17.0% of scheduler-requests to SETI@home now is with v6.10.17, and 0.83% with v6.10.18. Since there will be more v6.10.xx-releases, for most users there's little reason to upgrade at this point. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
martin64
Senior Cruncher Germany Joined: May 11, 2009 Post Count: 445 Status: Offline Project Badges: 
|
V6.10.18 for windows [...] All new translations for all languages are included in this release. So basically only a couple cosmetic changes, and there's little reason to upgrade from v6.10.17. ...except if you were confused about the mix of e.g. German and English language buttons in the manager. This is now fixed. Except for one or two of the WCG-specific buttons, which don't seem to be translated  Regards, Martin  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
v6.10.17 is showing Work Done and Avg. Work Done as 0.0
Stats work fine for SETI so it might be a WCG problem. It's a clean install on XP SP2. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
v6.10.17 is showing Work Done and Avg. Work Done as 0.0 Stats work fine for SETI so it might be a WCG problem. It's a clean install on XP SP2. According to this: http://www.worldcommunitygrid.org/stat/viewCo...es%5B0%5D.value=Sir+Clark Nothing has been returned from the member Sir Clark. So the data in WCG is indeed correct. Or did you mean KWSN Sir Clark? Something has indeed been returned: http://www.worldcommunitygrid.org/stat/viewCo...0%5D.value=KWSN+Sir+Clark |
||
|
|
|