It's mostly because they use Unix on main frame computers.

There's something like 400 CPU-years of work queued.

Yes, and all of it is set to run only on Os’s that are run by only a tiny minority of the public. Windows is run on about 87% of all the home computers in the World.

I sent an e-mail on this issue to the person who usually troubleshoots such problems.

Any response?

Response to moderator's email list.

Thanks, yes I am aware of this. It should be running again shortly.

This may well mean that the script will not run again till the early hours of Thursday morning.

You can also use the BOINC command line interface to manage the the client. See:

Yes I was managing BOINC from the command line until I got a work around. However I like to play and often build my own BOINC client and manager from source code using the testing versions and would quite like to get back into being able to do that on the laptop.

Looking at the failures for these and the N144 tasks, most of the failures that are not down to missing 32bit libs are from machines running large numbers of these tasks concurrently. (Often 16, 24 or even more in some cases.) Some of these machines are failing nearly everything they get. If this applies to you, please try under computing preferences, reducing the number of cores in use. A lot of computer time is being wasted by this issue.

Well, now that you put me up to it, I checked the last twelve successful completions on all machines.
Nine of them show the segfaults, and three don't. Some of each are from each machine, both Intel and Ryzen.

I won't try to do a statistical analysis.

The project are looking at measures to deal with the large number of computers missing the 32bit libraries or otherwise crashing everything on these and other Linux tasks.

Each task will now get a maximum of 5 attempts rather than the three we have seen in the past. This may mean a small increase in the number of tasks that fail on all computers being received. They are also looking at blocking computers from getting tasks till they sort things out. If the latter is effective I guess the former may only be a temporary measure.

One particularly egregious host was found that had crashed over a thousand of these!

I know from testing, that models on hyperthreaded computers run better if the hyperthreading is left on, but not used.
e.g. on my Haswell, only run 4 models.

This leaves the rest for the OS.

But how well do the 16, 24, 32 core computers fare?

It's possible that bottlenecks in getting to the FPU for so many at once may be a hindrance.

Any thoughts?

[Nairb wrote]... My question is, are these models restartable. In other words if I get 25 days into a model and there is a power cut...

The model saves intermediate files as it runs - "checkpoint" files - and these files should allow the model to continue after a PC restart. Sometimes the models won't restart from the checkpoint file and will fail, but usually the models are fine.

Just managed to get 4 new tasks. They are the Wah2_safr50-... Its says they have a runtime of approx 30days. My question is, are these models restartable. In other words if I get 25 days into a model and there is a power cut... And I lose the 4 models its a waste of effort.

ta
Nairb

Perfect time for the project to clear the problems log and work on the wish list ;)

The future is a strange place. You'll just have to wait and see.

and I have two sam25s at 10% on 10th day. Expected to finish in 100 days ;) I've reduced the load to 2 full cores so let's see if I get some gain on the sam25s

No real difference btw 2 or 4 cores on my i5-2520M sec/Ts almost the same. And I still keep one global from 766 now at 61% after 14 days I will just leave it until it crashes as expected.

I had 5 overnight and this morning. All failed within 90secs. When I get problem sets like this I pause anything already running and start the rogue ones. Gets through the failures quicker.