Posts by marmot

log in
1) Message boards : Number crunching : How to add this project on BOINC for Android (video) (Message 4011)
Posted 14 Jul 2016 by marmot
Here's a video I found on how to add this project to BOINC for Android.

(Yeah, I didn't find the 'add by URL' ability for 20 minutes... doh...)

Oh, and shouldn't there be a Q&A section for Android now?
2) Message boards : Number crunching : WU on one machine never ends. (Message 3650)
Posted 8 Feb 2016 by marmot
Removing the project and re-adding seemed to get WU to actually report again but there are still 3 old WU that read as In Progress.

No way to abort them client side nor here.
3) Message boards : Number crunching : WU on one machine never ends. (Message 3647)
Posted 7 Feb 2016 by marmot
I reset the project twice now and aborted the WU. The first one had been going 12 days and kept saying it had about 11 seconds left. Today, on the same machine, there was one that had been going 26 hours and was still counting about 1 minute 11 seconds.
It's like the work units are in and asymptotic countdown that will take at least a month to finally click over the last second.

What other methods can I try to repair this?

The machine used to work and used to have two clients to split the work load. I tried merging the two ID's but the database says they are incompatible. Is this part of the problem? Should I try to force a new cross ID?

I only see one WU but the last contact was today and shows three WU in progress and that is after resetting the project.

55703061 54492885 7 Feb 2016, 5:48:07 UTC 17 Feb 2016, 5:48:07 UTC In progress --- --- --- Data collect version 4 v4.20 (nci)
55673139 54465380 5 Feb 2016, 22:37:22 UTC 15 Feb 2016, 22:37:22 UTC In progress --- --- --- Data collect version 4 v4.20 (nci)
55616038 54412637 3 Feb 2016, 22:11:02 UTC 13 Feb 2016, 22:11:02 UTC In progress --- --- --- Data collect version 4 v4.20 (nci)
4) Message boards : Number crunching : Validate error's (Message 3560)
Posted 30 Dec 2015 by marmot
Thanks a lot!

Here's the solution from that post (I don't understand why quote or code tags are eliminating white characters on these forums):

    <cmdline>-p xxxx</cmdline>

Where xxxx = your client's non-standard port other than 31416.

5) Message boards : Number crunching : mult clients (Message 3559)
Posted 30 Dec 2015 by marmot

Is it still necessary to use app_info.xml? I'm not running multiple clients, but am running boinc on a port other than 31416 and found it only needed the following in an app_config.xml:

<app_config> <app_version> <app_name>data_collect_v4</app_name> <plan_class>nci</plan_class> <avg_ncpus>0.01</avg_ncpus> <cmdline>-p 31417</cmdline> </app_version> </app_config>

This requires a boinc client version of 7.2.39 or higher.

This is just what I needed for splitting into two clients on my 6-core and getting WUProps to read the second client.

The fetch algorithm doesn't read app_config files and so doesn't calculate in the <project_max_concurrent>2</> for ATLAS on an 8GB RAM machine or the 2 core max that the project at vLHC dictates. Nor does the work fetch seem to account for high resource setting project that is out of work for days, which is much more common than I expected. DENIS is reworking their servers, Citizen's grid seems to be off for the last month, etc.

Looks like the federal funding for BOINC is gone so the three dedicated coders (Anderson + others) are off while volunteer coders are taking over. I'm hoping they go back to the times of version BOINC 5 and 6 when it was quite easy to running multiple clients and the Windows registry wasn't relied upon and each client had it's own data directory along with a command line switch to tell the client where to find it's data directory. At least the windows installation engine should be fully aware of installing multiple copies and allow startup of multiple managers if they continue to rely on the Windows registry.

Oh I dream of a BOINCMGR.exe GUI that has commands on the left which allow you to assign a project particular cores of your computer, a resource allocation system that doesn't care about RAC but only the amount of hours a project gets on it's assigned cores and a work fetch that never idles a core when work is unavailable on a dedicated project but suspends the projects and then goes down the list from highest resource share to lowest and eventually grabs 1 temporary WU from the next project with work available to keep the cores from idling.
6) Message boards : Number crunching : Validate error's (Message 3557)
Posted 30 Dec 2015 by marmot
Jord(Ageless) suggested I move some of my WU's into a BOINC (those that aren't VBox themselves) virtual machine because the client doesn't handled app_config.xml limits on WU properly.

Instead of using a virtual machine I split BOINC into two clients running 4 and 2 cores on a 6 core machine in order to solve the work fetch issues of idle cores from high resource projects, without work, on that machine (it works really well now) but the WUProp monitoring one of the clients (I think the 4 core doing the most work) gives 90% validation errors even tho there are 30 minute WU's being done.

I am not sure which of these is the 2 core or the 4 core because the two clients are now nameless. Not sure how to fix that. So the two descriptions might actually be swapped.

installed directory client doing 2 cores and GPU
2nd client running 4 cores copied to a new directory running boinc.exe on a new port and manually connecting to it from a second boincmgr.exe process

If I understand correctly WUProp telnets into the client through the standard port instead of actually monitoring the RAM of the machine. Since the second client is moved to port 9000, is this the problem? Can I tell WUProp the new port number?

Home | My Account | Message Boards | Results

Copyright © 2017 Sebastien