Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 77 times and has 1 reply
mobluse
Cruncher
Sweden
Joined: Apr 5, 2020
Post Count: 2
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
MCM task is ready to start, but never starts

According to BOINCTUI my Samsung Android phone has a task that is in a state Wait that doesn't start:
Wait - World Community Grid 33h 99h 44h Mapping Cancer Markers - MCM1_0229522_2902_1
Both TUI and Manager are newly started, so the information comes from the phone. I also restarted the phone before starting TUI and Manager.

The phone also runs a non CPU intensive task: WUProp@Home, but even if I suspend that the WCG MCM task doesn't start.

I cannot get new tasks from other projects because:
Not requesting tasks: don't need (job cache full)

It seems that the WSG task that does never start blocks other tasks.

Then I aborted that task an a new WCG task was downloaded, but that also waits ready to start forever:
Application
Mapping Cancer Markers 7.61
Name
MCM1_0229838_9119
State
Ready to start
Received
Sat 18 Jan 2025 11:36:18 PM CET
Report deadline
Fri 24 Jan 2025 11:36:18 PM CET
Estimated computation size
29,166 GFLOPs
Executable
wcgrid_mcm1_map_7.61_arm-android-linux-gnu

About my phone:
Product name samsung GT-S6790N - SDK: 16 ABI: armeabi-v7a
CPU type ARM
ARMv7 Processor rev 9 (v7l) [Impl 0x41 Arch 7 Variant 0x2 Part 0xc09 Rev 9]
Number of processors 1
Operating System Android
3.0.15-1379436 (Android 4.1.2)
BOINC version 7.18.1
[Jan 18, 2025 11:33:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Michael E.@ team Carl Sagan
Cruncher
U.S.A.
Joined: Jul 18, 2010
Post Count: 28
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MCM task is ready to start, but never starts

As I mentioned privately to mobluse, my guess is that some resource is low and it prevents the work unit from starting. I encountered this with Rosetta years ago.

I stumbled upon the option to control the types of messages in the Event Log.

In the Advanced View, choose Options > Event Log Options...

There are many options and I only have file_xfer, task, and sched_ops checked (enabled) on my system, which is likely the default.

Would enabling something like cpu_sched_status show additional message types related to a low resource?

Or is there another BOINC tool that might help?
[Jan 25, 2025 4:41:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread