So, late on a Saturday evening, I get sent WU 27077711. Initial replication 2, quorum 1. Mine was _6, sent after six previous failures.

I could have handled that, because I've installed the required library. But it was 'cancelled by server', because nobody else has.

Everyone, please refer to Message 57067. It only takes seconds, and you don't even have to reboot.

I managed to pick up 3 cryptic scout resends today and successfully crunched and validated them.

I think the solution is for the app to be updated - which should have happened already, not for thousands of users to try and install something extra.
I've installed libboost v1.74 and am getting a different error.
I shouldn't have to diagnose, alter and tweak my system, when the issue is with the app itself - Hopefully the developers will fix this soon.

I think the solution is for the app to be updated - which should have happened already, not for thousands of users to try and install something extra.
I've installed libboost v1.74 and am getting a different error.
I shouldn't have to diagnose, alter and tweak my system, when the issue is with the app itself - Hopefully the developers will fix this soon.

I think the solution is for the app to be updated - which should have happened already, not for thousands of users to try and install something extra.
I've installed libboost v1.74 and am getting a different error.
I shouldn't have to diagnose, alter and tweak my system, when the issue is with the app itself - Hopefully the developers will fix this soon.

I definitely agree. The app should be updated to include the necessary package.

EXCEPTIONAL CONDITION: /home/user/conda/conda-bld/acemd3_1618916459379/work/src/mdio/bincoord.c, line 193: "nelems != 1"

I think the solution is for the app to be updated - which should have happened already, not for thousands of users to try and install something extra.
I've installed libboost v1.74 and am getting a different error.
I shouldn't have to diagnose, alter and tweak my system, when the issue is with the app itself - Hopefully the developers will fix this soon.

I definitely agree. The app should be updated to include the necessary package.

+1

To lacking of libboost v1.74 library, a problem of many wrongly constructed WUs in current batch can be added.
Even with libboost workaround applied locally, these tasks are failing anyway with this other error:

EXCEPTIONAL CONDITION: /home/user/conda/conda-bld/acemd3_1618916459379/work/src/mdio/bincoord.c, line 193: "nelems != 1"

...And they come to extinguish due to "max # of errors" reached.

Since number of tasks in progress is reduced to 3 at this time, it is consistent with Project be flushing the tasks buffer before a new App version is launched.

I've just got a new ADRIA task:

e1s5_I6-ADRIA_test_acemd3_update_KIXCMYB-1-2-RND1396

'test_acemd3_update' sounds hopeful, but:
1) Although created today, it's still being sent out with the ACEMD v2.12 (cuda1121) application.
2) The first user spat their copy out with the familiar libboost error. I got the second copy: I've patched my own machine, and it's running normally.

So, the test doesn't seem to be telling us anything we didn't know already.

I'm done until it gets fixed on the server side. My only boost option is 1.76.0 in gentoo.
1.74.0 isn't available.

I'm done until it gets fixed on the server side. My only boost option is 1.76.0 in gentoo.
1.74.0 isn't available.

That's interesting. I'm betting the fix for the errors for restarting on a different device is what is causing the problem of all tasks starting on device#0.

It must be hard coded to gpu0, or the whatever checks or communication it might have with BOINC to see which GPU is available isn’t being properly communicated so it somehow always thinks gpu0 is available. So every task runs there.
____________