I have just added a new host. I am an existing user so can't say for certain everything is fixed but that part of it is at least.

02/02/2024 12:12:07 | climateprediction.net | Scheduler list fetch from https://climateprediction.net/ failed: transient HTTP error

OK,
Andy knows about the problem. There are infrastructure changes happening at Oxford involving the virtual machines. He will sort out whatever needs it when the IT department there have finished.

Version of BOINC Manager on Linux 7.16.16. On Windows 11 I had latest version.

Currently no work for Linux machines in any case though hopefully there will be soon.

29/01/2024 22:03:20 | climateprediction.net | Scheduler list fetch from https://climateprediction.net/ failed: transient HTTP error
29/01/2024 22:03:21 |  | Project communication failed: attempting access to reference site
29/01/2024 22:03:22 |  | Internet access OK - project servers may be temporarily down.

Project communication failed: attempting to reference site
Internet access OK - project servers might be temporarily down 

ASAP

The expectation of at least one of the researchers, is that people will only download the same number of tasks as they have processor cores, and run them immediately, without stopping to run work from other projects.
Then get another bunch and do the same.

I recall that the project does not actually use/need the deadlines. They are there just because BOINC environment requires to have one.

While true that the project does not currently use deadlines, if they were to start using them, it would enable tasks to be re-issued in time to be of use to the researchers. At the time things were set up with long deadlines, all the work was generated and processed at Oxford. Now universities from all over the world generate the work and often do need it much more quickly. These days while they might still get credit, tasks returned a year after being issued are of no use to the scientists.

Ah yes I see, credit has been granted.

I did not realize that the credit was only updated on a weekly basis. Thank you for the heads up. It was not a well known fact to me a returning "newcomer". But now I know, so thank you.

What are the messages saying (in the Event Log) ?

Tue 29 Oct 2019 20:21:37 GMT | climateprediction.net | Scheduler request completed: got 0 new tasks

Also I kept running 2 LHC@home tasks at the same time, which use VirtualBox. However I suspended those for about 2 hours to see if things will get better but didn't notice any improvement in crunching progress of CPND task.

Hummm. The LHC VBox tasks will take a lot of memory, at least CMS and ATLAS. When you suspend them, if you have "leave applications in memory" enabled, they will hang around in memory. So I wouldn't run them at all.
I don't even try to run the native LHC tasks on my machines with a lot more memory and cache. Just exit LHC entirely and run CPDN for a while.

Good luck with the switch out of VBox. I have never attempted such a thing.

That would be over 25 days per work unit, which is a bit slow for that CPU. I would expect at least twice that fast.
Are you running other projects? Normally VBox does not exact much of a penalty, but maybe it does not work well with N216.
The caching requirements for N216 are a bit strange.

Hello,

I snatched one of those tasks on my Linux host but after 2 days of crunching WU failed with no credit granted.

Was WU faulty?

https://www.cpdn.org/cpdnboinc/result.php?resultid=21733569

Three trickles have been reported so I imagine you will get credit for them by end of play tomorrow when the weekly credit script has run. (assuming all goes to plan!)


The -ve theta detected means the model has produced an impossible climate for example a negative air pressure. Some tasks in a batch often push the limits of what might happen and if they are too far out this happens. That result is still useful.

On Ubuntu 16.04 LTS this command worked to satisfy the dependencies

sudo apt-get install lib32ncurses5 lib32z1 gcc-4.7-multilib

However, Mint 19.1 is based on Ubuntu 18.04 LTS so may have different dependencies.

You may be able to substitute

lib32stdc++-6-dev

for

gcc-4.7-multilib

in the above command. If that doesn't work, the output from that command may give you an explanation of what replacement dependency is needed.

As a last resort, you can also do a

sudo ldd on the hadcm3s executables (probably 2 of them with different names) and .so file in the (probably) /var/lib/boinc-client/projects/climateprediction.net directory to see what dependencies are left to be satisfied.

process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
../../projects/climateprediction.net/hadcm3s_8.34_i686-pc-linux-gnu: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory