Not only for me, all users before also got these defective WUs.
Could please someone stop sending out this waste?

Could please someone stop sending out this waste?

May I humbly submit...
If Adria learns from this setback it is not a waste, it becomes a step that had to be taken to move on. This is how research is conducted. Trial and error. It is not being presented for our entertainment as competitors, so it carries the caveat that experiments sometimes fail.

(I hope that wasn't put too bluntly, I think I maybe was channeling Karl Popper there.) 😉

---

"Together we crunch
To check out a hunch
And wish all our credit
Could just buy us lunch"

Piasa Tribe - Illini Nation

Of course an experiment can go wrong. But as I requested - then the experiment shall be stopped. In best case the experiment is pre-tested as beta-version with just a few WUs before it starts for all users.

How many other Linux users are having difficulty running this sparse release of acemd3 tasks?

I haven't been successful on any of my Linux hosts.

Looking at the other wingmen that are offered the tasks, I see similar failures from other Linux wingmen.

And usually the task is finally completed by a Windows host. They seem to have no issues with the tasks.

I've never had any issues with the acemd3 task in the past.

And I have no issues with the ATMbeta tasks when they are offered.

Exactly the same here on my Linux hosts for current ACEMD 3 tasks.
They all fail after a few seconds, with no clue about the reason.

Stderr output

<core_client_version>7.20.5</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
04:36:04 (51194): wrapper (7.7.26016): starting
04:36:21 (51194): wrapper (7.7.26016): starting
04:36:21 (51194): wrapper: running bin/acemd3 (--boinc --device 0)
04:36:22 (51194): bin/acemd3 exited; CPU time 0.000000
04:36:22 (51194): app exit status: 0x1
04:36:22 (51194): called boinc_finish(195)

And eventually, the same WU succeeds when a new task arrives a Windows host.
I've reset GPUGRID project at BOINC Manager, and no variation.
No problem witn ATMbeta tasks on the same hosts.

Exactly the same here on my Linux hosts for current ACEMD 3 tasks.
They all fail after a few seconds, with no clue about the reason.

Stderr output

<core_client_version>7.20.5</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
04:36:04 (51194): wrapper (7.7.26016): starting
04:36:21 (51194): wrapper (7.7.26016): starting
04:36:21 (51194): wrapper: running bin/acemd3 (--boinc --device 0)
04:36:22 (51194): bin/acemd3 exited; CPU time 0.000000
04:36:22 (51194): app exit status: 0x1
04:36:22 (51194): called boinc_finish(195)

And eventually, the same WU succeeds when a new task arrives a Windows host.
I've reset GPUGRID project at BOINC Manager, and no variation.
No problem witn ATMbeta tasks on the same hosts.

I have seen this before, a few years ago, on few occasions. It happened when the license for the Linux app expired, and the project management forgot to renew it. Sometimes, it was the other way, the Windows license expired, and all the Windows computers would fail and the Linux computers would succeed.

If you move the clock on your computer to before the expiration date of the app, before the task starts, the task would succeed, but boinc interface would be "unresponsive"......

you're right

$ ./acemd3
#
# ACEMD version 3.5.1
#
# Copyright (C) 2017-2022 Acellera (www.acellera.com)
#
# When publishing, please cite:
# ACEMD: Accelerating Biomolecular Dynamics in the Microsecond Time Scale
# M. J. Harvey, G. Giupponi and G. De Fabritiis,
# J Chem. Theory. Comput. 2009 5(6), pp1632-1639
# DOI: 10.1021/ct9000685
#
# Arguments:
# input: input
# platform:
# device:
# ncpus:
# precision: mixed
#
# Licence:
# Check floating licence:
# ACELLERA_LICENCE_SERVER -- not defined
# ACELLERA_LICENSE_SERVER -- not defined
# Check node-locked licence:
# ACELLERA_LICENCE_FILE -- not defined
# ACELLERA_LICENSE_FILE -- not defined
# /opt/acellera/licence.dat -- DENIED (Unable to locate target file)
# /opt/acellera/license.dat -- DENIED (Unable to locate target file)
# /home/ian/.acellera/licence.dat -- DENIED (Unable to locate target file)
# /home/ian/.acellera/license.dat -- DENIED (Unable to locate target file)
#
# This version of ACEMD has expired!
# You should update to the latest version.
# If you want to continue using this version, you need a licence.

---

Gianni replied that they are on it for the fix.

I have seen this before, a few years ago, on few occasions. It happened when the license for the Linux app expired, and the project management forgot to renew it. Sometimes, it was the other way, the Windows license expired, and all the Windows computers would fail and the Linux computers would succeed.

this has happened several times in the past. The team found out about the expiration of a license only after tasks started failing.
I never understood what's the problem with making a note in a calendar some time before the expiration date of a license, so that the license could be renewed in time.