It shows you are on BOINC 7.17.0, (the current recommended version is 7.4.22)

It also indicates that the task did not complete the first model within the 1hr preferred runtime plus 4hr watchdog timeout. The task was created in a way that causes it not to go out to another host for validation. So the one error was "too many", and the WU (which, sometimes, could be more than just the task that went to you) was ended. And then I guess as the watchdog went to end the task, it found no output file.

In a nutshell, you hit a long running model against the smallest possible runtime, and it was ended for you.

With 64 processor cores, how many threads is BOINC trying to run? Is it a hyperthreaded CPU? This would cause BOINC to attempt 128 active tasks, which would then make the 128GB of memory rather tight. (actually a quick search, it looks like there are 32 physical cores, hyperthreaded to 64 active threads).

I would suggest bumping CPU utilization back to 100% as dcdc suggests (we've seen odd issues with <100% in the past). And dial back the CPU count %. Maybe start at 50% and work your way up.

Have you run any stress tests on the machine? CPU or memory tests? Sometimes R@h ends up being the first stress test a machine has seen.

Also, have you checked for any updates to your Linux version?

I'm not seeing others reporting hangs like this. So, what else could be unique about your machine? (besides that it is such a BEAST of a machine! :)

Are you sure it's not overheating? Rosetta might push the FPU or RAM harder than other projects. Can the machine handle a stress test like P95?

D

I see your linux machine shows that it has 64 processors, and 128GB of memory, and is running:
Linux LinuxMint
Linux Mint 19.3 Tricia [5.3.0-42-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)]

Is the machine running a mix of BOINC projects? Is it running other types of work as well?

With that many tasks running, it would be possible that one got to a point that it was using excessive memory. But I believe the BOINC core monitors that and insulates the rest of the system by making the task wait for memory or ending it.

Just looking at a few of the failed tasks, their peak memory was about 1.2 GB.

Hang conditions are always difficult. Have you seen this happen a few times?

Is BOINC allowed to use most of that memory (CPU preferences)? What about the disk? Is BOINC allowed to use plenty of disk space? (say 2GB per task)

I can only suggest using the settings to run on less than 100 percent of your CPUs and see if this helps.

I am having issues with Rosetta jobs on my Linux machine. The machine randomly becomes unrepsonsive and I have to power cycle in order to get it back. The power cycle obviously purges the issue but also any evidence of what caused it. I only have this issue when running Rosetta jobs. Has anyone else had this issue? I would appreciate some help.

Thanks,
Greg

Possible memory/swap issues? Maybe the machine is starting to use a good amount of swap space? How much memory does the machine have?
Charlie

I am having issues with Rosetta jobs on my Linux machine. The machine randomly becomes unrepsonsive and I have to power cycle in order to get it back. The power cycle obviously purges the issue but also any evidence of what caused it. I only have this issue when running Rosetta jobs. Has anyone else had this issue? I would appreciate some help.

Thanks,
Greg

Not something that I’ve experienced but the evidence should still exist in /var/logs/...