I've seen this error on several tasks returned yet others run and are completed and validated. Any ideas for fixing it on my end?

Running on a PI4 Ubuntu 20.04 server

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)</message>
<stderr_txt>
Process creation (../../projects/www.mlcathome.org_mlcathome/mlds_9.61_arm-unknown-linux-gnueabihf) failed: Error -1, errno=2
execv: No such file or directory

</stderr_txt>
]]>

Are these errors on the same machine as others that pass? That error indicates that either the client (the boinc client, not our app) couldn't find the executable to run.. which barring a hardware error wouldn't make any sense.

Yes the errors are on the same machine with others that pass. Examples: on 12/29 4 worked and 3 failed, on 12/28 2 failed, on 12/27 2 worked.

It is weird how some work but others don't. If it fails it seems to be right at the start so no run time loss. Is there a log file that might show what's going on?

Could it be that all 64-bit WUs run without problem, but that all 32-bit WUs fail?

do you have this in the cc_config.xml:

<cc_config>
<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<alt_platform>armv7l-unknown-linux-gnueabihf</alt_platform>
</options>
</cc_config>

did you do this:

sudo dpkg --add-architecture armhf
sudo apt update --fix-missing
sudo apt dist-upgrade
sudo apt install libc6:armhf libstdc++6:armhf zlib1g:armhf libfuse2:armhf

Doing all the things I suggested does not even help you with the 32-bit Linux/ARM app on a 64-bit platform, as the 32-bit app seeks for GLIBC 2.28, while 64-bit Linux is at 2.27

Doing all the things I suggested does not even help you with the 32-bit Linux/ARM app on a 64-bit platform, as the 32-bit app seeks for GLIBC 2.28, while 64-bit Linux is at 2.27

-at least in the case of my Jetson Nano's.

My 64-bit Raspberry Pi 4 reports "error while loading shared libraries: libz.so.1"

Dirk, thanks for the suggestions.

My config file did not have
<alt_platform>armv7l-unknown-linux-gnueabihf</alt_platform>
added that line.

The first 3 sudo lines did nothing but the last sudo line did install several packages.

These changes appear to fix the issue! I no longer see the error and all finished tasks(16) so far have ended "Completed and validated".