I did the following on that particular host
(http://climateapps2.oerc.ox.ac.uk/cpdnboinc/show_host_detail.php?hostid=419870):

- installed boinc 6.10.58 (previous was 6.4.5)
- extracted libstdc++.so.6 as symlink to libstdc++.so.6.0.10 from libstdclibstdc++-4.3.0-8.i386.rpm
- started boinc with:
LD_PRELOAD=/home/$HIDDENUSER/boinc/kit/boinc/lib/libstdc++.so.6 /home/$HIDDENUSER/boinc >/dev/null 2>&1 &


That libstdc++ version might not work, or even crash, on Fedora 8,
but let's give it a try.

I'll post the results.

---

Passed up to the project team for re-enabling of work fetch Adi.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

No, I don't. But I do a regular shutdown and do not just "cut off power". Usually all programs close their files on a system shutdown request or halt the shutdown process if closing is not possible.
I will give it a try and suspend work on the project before shutdown in the next days.

Are all BOINC projects not capable to cope with a regular shutdown process or is this just climateprediction? I mean, is this a problem of the BOINCManager?

Best regards,
Peter

Thank you Thyme Lawn.

I also installed on another host libstdc++ 386 (it's a 64 bit one, it hadn't the compatible one).

I think that, instead of

"no work for your type of computer"

the message to be

"some libraries are missing, please run ldd $name_of_exec_with_missing_libraries to check which one(s)"

The message will be less cryptic (at least for some people :) )...

Or maybe at least

"check <link-on-cpdn-site> for prerequisites to run $app"

Just an idea...

---

I was notified of a bad Boinc installation. The link provided was : http://climateapps2.oerc.ox.ac.uk/cpdnboinc/show_host_detail.php?hostid=1202494

I have removed the project and re-added it, but don't know if that did anything to fix the problem since it won't complete the download of the application.

What can I do to resolve this issue?

Wes

Wes,

The stderr messages for the failed tasks indicated "couldn't start CreateProcess() failed - Access is denied." Your detaching and reattaching may fix that, but you may also want to exclude the BOINC data folder from being scanned by your antivirus/antimalware software.

We need to let the software people know you have attempted to fix the configuration of that PC before they will allow new tasks to download. See if you can exclude that folder from scanning, and let us know, and we'll let the project people know that they should re-enable downloads.

Are all BOINC projects not capable to cope with a regular shutdown process or is this just climateprediction? I mean, is this a problem of the BOINCManager?

Peter,
No. CPDN seems to be unique in the number of large files open simultaneously. (Imagine the number of parameters being modeled, the global grid, vertical layers into the atmosphere and ocean depths, for current model-time and previous time slice, you'll get the idea -- and the necessity. [Numbers for layers and grid vary with model type.])

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Thanks geophi,

I have excluded the Boinc data directory from my antivirus program. Can you let the project people know that they can re-enable downloads?

Wes

Thanks geophi,

I have excluded the Boinc data directory from my antivirus program. Can you let the project people know that they can re-enable downloads?

Wes

Duly notified.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Apparently I have a misconfigured boinc module.
http://climateapps2.oerc.ox.ac.uk/cpdnboinc/show_host_detail.php?hostid=1101060

I've reinstalled boinc.

Other boinc projects seem to be working.

What's my next step?

What's my next step?

Just make sure the project is reset before requesting new work. That will clear out any existing data and allow new data to be downloaded (including the applications), which will then have the correct permissions.

Other boinc projects seem to be working.

BOINC say the permissions problem is not their fault, though it was a change at their end that caused this problem for Macs on CPDN. They also say they won't fix it because that would inconvenience existing BOINC projects. I don't quite see the logic of that, since CPDN is an existing project whose (Mac) users have been severely inconvenienced. Nonetheless, CPDN have developed a fix that should emerge soon with a new type of HADAM3P model. As with many permissions issues, "if it ain't hurting, it ain't working": this is the "hurting" section, but tighter permissions will in future prevent other problems. People will not, of course, post about the problems they are not having.

If you post back here to say that the project has been reset then one of the moderators will send a message to the project staff, who will re-enable that machine.

I received the messagae saying my Mac was crashing models.

The email suggested I provide this link

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/show_host_detail.php?hostid=1097264

I just upgraded my BOINC client on my Mac to V7.0.31. Not sure if that helps to address the issue?

Suggestions welcome.

Thanks

Simon

---

An example model from that host is hadcm3n_o5i3_2100_40_008139322_1. Expanding the 'Stderr' text reveals reports like the following:

execl(/Library/Application Support/BOINC Data/projects/climateprediction.net/hadcm3n_um_6.07_i686-apple-darwin, 132125) failed!

This suggests that the Mac has the permissions problem described in the post immediately before your post. You should follow the suggestions in that post every time you upgrade BOINC Manager, until improved CPDN applications are available that work around the permissions problem.

ok. i have reset the project, so i guess it is eagerly anticipating some work. Do you need to unleash something...
regards
Simon

---

I notified the project people that your PC is ready to go. Unfortunately, right now, the queue on models has run out. Hopefully the supply will get restocked later this week.

OK, project reset

[John Grey wrote:]OK, project reset

Message duly passed on.

[John Grey wrote:]OK, project reset

Message duly passed on.

... and the machine is now enabled. However, there is not any work immediately available.

Mac: 1192040. Maybe that Mac + BOINC 6.12 issue again?

Mac: 1192040. Maybe that Mac + BOINC 6.12 issue again?

Thanks, Belfry: alert passed on.