1) Forums : News : Recent outage explanation (Message 21952)
Posted 10 Oct 2018 by Variable
Post:
Still having issues I take it? There is a noticeable shortage of work units...
2) Forums : Technical Support : Getting Error Message VM Job unmanageable (Message 21587)
Posted 30 Nov 2017 by Variable
Post:
I have gotten some of this behavior on my machines as well, particularly when first starting up the project. It is difficult to pin down a cause as to why. Eventually the problem has gone away, sometimes by switching from say 1 task with 8 threads to an equivalent 2 tasks with 4 threads, or vice versa. Or sometimes by doing nothing. It's odd.
3) Forums : Technical Support : Execution cap? (Message 21586)
Posted 30 Nov 2017 by Variable
Post:
Yes, that's what it was. *facepalm*

I had reinstalled Boinc and forgotten to set the computing preferences back to 100%. It was set at a suspiciously identical 60% in the preferences. Now everything is back to running 'full power'.
4) Forums : Technical Support : Execution cap? (Message 21576)
Posted 25 Nov 2017 by Variable
Post:
I'm noticing on one of my machines running Cosmology that it does not run equivalent tasks as fast as a different machine. When I dug down into the details and looked at what virtualbox is doing, the slower machine has a 60% "execution cap" applied to each task in virtualbox, which the faster machine does not. So even though it has the same 8ncpu setting in its app_config, it's only running at 60% the speed of the faster machine. These two computers have same OS (win10), same Boinc version (7.6.33), same virtualbox version (5.2.0). This execution cap does not seem to be a global setting in virtualbox, it is specific to each virtual machine running. I can change the cap setting up to 100%, but then when I come back later and new tasks are running the cap has been reset to 60%.

If you sit and watch it run, the cap is not applied till the task is well underway, almost like the cosmology code is requesting it? What's happening here? I'm having to run two tasks at 8ncpu's each to get roughly the same processor utilization on this machine as I do from one task on my other machine.
5) Forums : Technical Support : Excluded from Gridcoin? (Message 21575)
Posted 23 Nov 2017 by Variable
Post:
Not sure if this is a temporary thing or not, but Cosmology has been excluded from the active project list on Gridcoin for the last day or so. Is there some issue with the project server(s) here, not reporting stats?
6) Forums : Technical Support : camb_boinc2docker erroring due to time? (Message 21568)
Posted 28 Oct 2017 by Variable
Post:
I tried running the multi-core app again today on this machine and now it seems to be working. Right now I'm running 2 tasks at 4 threads apiece, no errors. Weird. I didn't make any config changes to the machine at all.
7) Forums : Technical Support : camb_boinc2docker 2.04 not respecting ncpu limit (Message 21565)
Posted 27 Oct 2017 by Variable
Post:
Actually I think I Just figured it out. It was running tasks that had been downloaded right after attaching this machine to the project, and they were all calling 8 threads (the max this box has), I could see it in the VBox manager. I aborted all those, and now the new tasks that just downloaded are only using the ncpus that I'm specifiying. Problem seems to be solved.
8) Forums : Technical Support : camb_boinc2docker 2.04 not respecting ncpu limit (Message 21564)
Posted 27 Oct 2017 by Variable
Post:
As the title says, I'm trying to limit the number of threads cosmology will use on my 4790 box but it is not respecting the limit I put in the app_config file:

<app_config>

<project_max_concurrent>1</project_max_concurrent>

<app_version>
<app_name>camb_boinc2docker</app_name>
<plan_class>vbox64_mt</plan_class>
<avg_ncpus>3</avg_ncpus>
</app_version>

</app_config>

BOINC is recognizing the config file and I can see the task says (3 CPUs), yet as soon as I turn it on it slams CPU usage to 100%, with no other competing tasks running. This renders the machine unusable and actually locked it up earlier today. Any ideas to fix this?
9) Forums : Technical Support : camb_boinc2docker erroring due to time? (Message 21557)
Posted 23 Oct 2017 by Variable
Post:
Virtualization is turned on in the BIOS, I had to turn it on in order to run LHC@home which also uses VirtualBox. The machine has 16GB of RAM which was only maybe ~50% utilized while these work units were running. Are there any rules of thumb on boinc2docker tasks vs number of vCPU's assigned vs system RAM?
10) Forums : Technical Support : camb_boinc2docker erroring due to time? (Message 21555)
Posted 23 Oct 2017 by Variable
Post:
From just sitting there and watching this machine for a while, it would run the camb_boinc2docker units for 15-20mins, enough to complete most of the work unit, but then fails with the error I pasted previously.
11) Forums : Technical Support : camb_boinc2docker erroring due to time? (Message 21554)
Posted 23 Oct 2017 by Variable
Post:
Fixed - it should not be hidden now
12) Forums : Technical Support : camb_boinc2docker erroring due to time? (Message 21552)
Posted 22 Oct 2017 by Variable
Post:
Hi - I started trying out this project the last day or so. The legacy app seems to run fine but the VM app appears to be constantly erroring. Other VM projects like LHC have run fine. It's saying "exceeded elapsed time limit". Any ideas what's happening?

10/22/2017 2:05:32 PM | Cosmology@Home | Aborting task camb_boinc2docker_32028_1508609789.343757_0: exceeded elapsed time limit 1028.38 (86400.00G/85.93G)
10/22/2017 2:05:58 PM | Cosmology@Home | Computation for task camb_boinc2docker_32028_1508609789.343757_0 finished
10/22/2017 2:05:58 PM | Cosmology@Home | Output file camb_boinc2docker_32028_1508609789.343757_0_r618894800_0 for task camb_boinc2docker_32028_1508609789.343757_0 absent
10/22/2017 2:05:58 PM | Cosmology@Home | Starting task wu_102117_170958_0_0_0