Trying to get boinc to run on my MacBook Pro. It'll startup and load the project ( moo!wrapper!) jump to 6.310% complete and then nothing more will happen. The time running keeps going up, the time remaining stays the same and the progress never increases. The computer doesn't get hot and the fans don't kick in. Checking on the activity monitor I can see the 4 instances of the dnet project loaded, but with 0.1% cpu usage. This is also the case with any other project I try to run. Loads, starts but never tries to do anything.

This happens if using preferences local, or web and with always running set

this is the first bit of the log. Tell me anything else you need to see.

Thanks

Mon 3 Jul 11:16:38 2023 | | cc_config.xml not found - using defaults
Mon 3 Jul 11:16:38 2023 | | Starting BOINC client version 7.22.2 for x86_64-apple-darwin
Mon 3 Jul 11:16:38 2023 | | log flags: file_xfer, sched_ops, task
Mon 3 Jul 11:16:38 2023 | | Libraries: libcurl/7.79.1 SecureTransport zlib/1.2.11 c-ares/1.17.2
Mon 3 Jul 11:16:38 2023 | | Data directory: /Library/Application Support/BOINC Data
Mon 3 Jul 11:16:39 2023 | | OpenCL: Intel GPU 0: Intel(R) Iris(TM) Graphics 6100 (driver version 1.2(Aug 31 2020 23:17:11), device version OpenCL 1.2, 1536MB, 1536MB available, 403 GFLOPS peak)
Mon 3 Jul 11:16:39 2023 | | OpenCL CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Mon 3 Jul 11:16:39 2023 | | Host name: Marks-MacBook-Pro.local
Mon 3 Jul 11:16:39 2023 | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz [x86 Family 6 Model 61 Stepping 4]
Mon 3 Jul 11:16:39 2023 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe pni pclmulqdq dtes64 mon dscpl vmx est tm2 ssse3 fma cx16 tpr pdcm sse4_1 sse4_2 x2apic movbe popcnt aes pcid xsave osxsave seglim64 tsctmr avx rdrand f16c
Mon 3 Jul 11:16:39 2023 | | OS: Mac OS X 10.13.6 (Darwin 17.7.0)
Mon 3 Jul 11:16:39 2023 | | Memory: 8.00 GB physical, 745.13 GB virtual
Mon 3 Jul 11:16:39 2023 | | Disk: 894.06 GB total, 743.44 GB free
Mon 3 Jul 11:16:39 2023 | | Local time is UTC +1 hours
Mon 3 Jul 11:16:39 2023 | | VirtualBox version: 6.1.0r135406
Mon 3 Jul 11:16:39 2023 | Moo! Wrapper | General prefs: from Moo! Wrapper (last modified 02-Jul-2023 19:03:50)
Mon 3 Jul 11:16:39 2023 | Moo! Wrapper | Host location: none
Mon 3 Jul 11:16:39 2023 | Moo! Wrapper | General prefs: using your defaults
Mon 3 Jul 11:16:39 2023 | | Preferences:
Mon 3 Jul 11:16:39 2023 | | - When computer is in use
Mon 3 Jul 11:16:39 2023 | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Mon 3 Jul 11:16:39 2023 | | - don't use GPU
Mon 3 Jul 11:16:39 2023 | | - max CPUs used: 4
Mon 3 Jul 11:16:39 2023 | | - Use at most 50% of the CPU time
Mon 3 Jul 11:16:39 2023 | | - suspend if non-BOINC CPU load exceeds 25%
Mon 3 Jul 11:16:39 2023 | | - max memory usage: 2.00 GB
Mon 3 Jul 11:16:39 2023 | | - When computer is not in use
Mon 3 Jul 11:16:39 2023 | | - max CPUs used: 4
Mon 3 Jul 11:16:39 2023 | | - Use at most 50% of the CPU time
Mon 3 Jul 11:16:39 2023 | | - suspend if non-BOINC CPU load exceeds 25%
Mon 3 Jul 11:16:39 2023 | | - max memory usage: 6.40 GB
Mon 3 Jul 11:16:39 2023 | | - Store at least 0.10 days of work
Mon 3 Jul 11:16:39 2023 | | - Store up to an additional 0.10 days of work
Mon 3 Jul 11:16:39 2023 | | - max disk usage: 742.45 GB
Mon 3 Jul 11:16:39 2023 | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Mon 3 Jul 11:16:39 2023 | | Setting up project and slot directories
Mon 3 Jul 11:16:39 2023 | | Checking active tasks
Mon 3 Jul 11:16:39 2023 | Moo! Wrapper | URL http://moowrap.net/; Computer ID 1309202; resource share 100
Mon 3 Jul 11:16:39 2023 | | Setting up GUI RPC socket
Mon 3 Jul 11:16:39 2023 | | Checking presence of 20 project files
Mon 3 Jul 11:16:39 2023 | | Suspending GPU computation - computer is in use
Mon 3 Jul 11:16:49 2023 | | Suspending computation - CPU is busy
Mon 3 Jul 11:17:09 2023 | | Resuming computation
Mon 3 Jul 11:22:09 2023 | | Re-reading cc_config.xml
Mon 3 Jul 11:22:09 2023 | | log flags: file_xfer, sched_ops, task, app_msg_send
Mon 3 Jul 11:22:09 2023 | | [app_msg_send] sent <resume/> to dnetc_r72_1688313590_9_9_0
Mon 3 Jul 11:22:09 2023 | | [app_msg_send] sent <resume/> to dnetc_r72_1688312465_9_9_0
Mon 3 Jul 11:22:09 2023 | | [app_msg_send] sent <resume/> to dnetc_r72_1688314853_9_9_0
Mon 3 Jul 11:22:09 2023 | | [app_msg_send] sent <resume/> to dnetc_r72_1688314855_9_9_0
Mon 3 Jul 11:22:10 2023 | | [app_msg_send] sent <suspend/> to dnetc_r72_1688313590_9_9_0
Mon 3 Jul 11:22:10 2023 | | [app_msg_send] sent <suspend/> to dnetc_r72_1688312465_9_9_0
Mon 3 Jul 11:22:10 2023 | | [app_msg_send] sent <suspend/> to dnetc_r72_1688314853_9_9_0
Mon 3 Jul 11:22:10 2023 | | [app_msg_send] sent <suspend/> to dnetc_r72_1688314855_9_9_0

What happens when you go back to 7.22.1 or earlier? You can look these up in https://boinc.berkeley.edu/dl/?C=M;O=D

PS, for other helpers, read through https://moowrap.net/forum_thread.php?id=658 for more information and what's been asked already. I'm thinking it's something that the science app doesn't like about the new BOINC.

same thing. doesn't work with any version I've tried now

Okay, so then it's something completely different that's causing it.
Going back to what the science application is telling you in the tasks you aborted

https://moowrap.net/result.php?resultid=182560158
Paused... (No mains power)
Pause level raised... (found flagfile)
Pause level lowered... (flagfile cleared)

Versus a task run to end, normally:
https://moowrap.net/result.php?resultid=182562909
Paused... (found flagfile)
Running again after pause... (flagfile cleared)

So something pauses your task immediately internally because it doesn't find (enough?) power.
Is your Macbook a laptop running on battery?

No it was running on mains powers.

The logs may be misleading in some ways because I have been turning things on and off in a vain attempt to fix the issue. The [suspend] message is possibly (?????) the issue but I can not tell what is causing it to suspend the task

Also worth mentioning and to confuse things. That working result looks to have been from when boinc was running on a windows machine I had for work..

Sorry

First exit BOINC fully.
Next, delete the global_prefs.xml file and if it exists (I don't think it does as it doesn't show in your log) the global_prefs_override.xml file (they are in the data directory, but I don't know where that is).
Then go to Moo Wrapper website and reset your preferences, with the Restore Defaults button at the bottom of the preferences page.

Now start BOINC and force a contact with the project (Projects->Select Moo Wrapper->Update). This repopulates the global_prefs.xml file with the default settings from the website. Does that do something?

Also worth mentioning and to confuse things. That working result looks to have been from when boinc was running on a windows machine I had for work..

No, the working result was the same task as yours, but sent to a different computer after you aborted it. Projects send out tasks that have not finished correctly to other systems for them to try and finish.

From his first posting...
The settings I highlighted below in RED are extremely aggressive and the computer will think it's always in use every time a key is pressed or the mouse thinks it has been moved the slightest bit.

Suggestion is for him to change the when in use & when not in use override settings to possiblely be running all the time including letting it use more or all of the 8GB RAM that's available on the PC.

Mon 3 Jul 11:16:39 2023 | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Mon 3 Jul 11:16:39 2023 | | - don't use GPU
Mon 3 Jul 11:16:39 2023 | | - max CPUs used: 4
Mon 3 Jul 11:16:39 2023 | | - Use at most 50% of the CPU time
Mon 3 Jul 11:16:39 2023 | | - suspend if non-BOINC CPU load exceeds 25%
Mon 3 Jul 11:16:39 2023 | | - max memory usage: 2.00 GB
Mon 3 Jul 11:16:39 2023 | | - When computer is not in use
Mon 3 Jul 11:16:39 2023 | | - max CPUs used: 4
Mon 3 Jul 11:16:39 2023 | | - Use at most 50% of the CPU time
Mon 3 Jul 11:16:39 2023 | | - suspend if non-BOINC CPU load exceeds 25%
Mon 3 Jul 11:16:39 2023 | | - max memory usage: 6.40 GB

Mon 3 Jul 11:16:39 2023 | | Suspending GPU computation - computer is in use
Mon 3 Jul 11:16:49 2023 | | Suspending computation - CPU is busy
Mon 3 Jul 11:17:09 2023 | | Resuming computation

ok, tried this but still stuck at 6.310% and not computing still

The "aggression" or otherwise of a set of setting depends on the prime use of the computer.

If this is a work computer then most of them are about right as one doesn't want work being interrupted by other things. There are only a couple of settings that need to be reviewed:

Use at most xx% of CPU time, having this set to anything other than 100% can give some tasks problems as they don't like being interrupted frequently (the cycle time is a fraction of a second, and that can make some applications loose track of their data and their progress)

Max memory usage - 2Gb can be rather small these days, but it depends on how much RAM the computer has, I would suggest this figure being no less than 75% of the computer's RAM.

For a 24/7 cruncher the picture changes dramatically, with my opening comment being "Don't use any sort of laptop for 24/7 crunching, they just aren't designed for it".

well something has changed now. it's loading up dnetc518-macosx-amd64 which is hammering the cpu at 95% and generating heat. but ALSO dent_wrapper1.3_x86_64-apple-darwin which is at 0.1%

but the work unit percentage is not increasing nor is the time to complete decreasing.

to me that seems to have loaded the wrong program for this cpu

Glad to hear that progress is being made and your CPU is now acting as a room heater.
Many applications only update the time & progress indicators at somewhat extended intervals or at key points in the job, which can be very frustrating so don't worry too much about that.
Two things to look at, first how long has the task been running, and second what is the expected task duration as not all tasks have the same run time. For example CPDN is famed for its very long durations, so very low progress rate.
Generally if a task-CPU combination is wrong the task will fail with an error in the first few seconds of execution, not after some time, and from what you've said these tasks are no failing with an error, only taking a long time to show progress.

Many applications only update the time & progress indicators at somewhat extended intervals or at key points in the job, which can be very frustrating so don't worry too much about that.

Yes, I have seen tasks that get stuck in a loop and don't progress but not in the last ten years and then only with some of the CPDN tasks that used to take six months or more to finish.

The next quirk is the cpu is always at 95% even if I change the web preferences or use the local preference
I don’t want it that high, it’ll melt the machine lol

The next quirk is the cpu is always at 95% even if I change the web preferences or use the local preference
I don’t want it that high, it’ll melt the machine lol

Much better to keep temps down by restricting the number of cores BOINC can use. The cores I use are at 99 or 100% virtually all the time. My main machine has liquid cooling so not an issue but with some machines in the past, I would run on 50% of real cores to keep the temp down. The CPU at 95% is pretty normal.

Well, left it running a few days now and it is crunching and reporting back. Not sure why it won’t let me change the cpu usage, but I can limit the number of cores used. So that at least helps with the heat.


Thanks for the help