Just joined the project and downloaded one WU as a test. Unfortunately, it ended immediately with the following error:

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
fuse: failed to exec fusermount: No such file or directory
open dir error: No such file or directory
</stderr_txt>
]]>

Is this an error with the individual workunit or is this a general error with CentOS?
Additional Information:

Jul 20 09:18:25 alpha boinc[2087]: 20-Jul-2020 09:18:25 [MLC@Home] Starting task ParityMachine-1593738798-3305-20_1
Jul 20 09:18:25 alpha kernel: fuse: init (API version 7.31)
Jul 20 09:18:25 alpha kernel: mlds_0.920_x86_[683432]: segfault at 31f ip 00007fa7b4d89a95 sp 00007ffcd8e64da0 error 4 in ld-2.28.so[7fa7b4d74000+29000]
Jul 20 09:18:25 alpha kernel: Code: 00 00 48 8d 3d 26 c6 00 00 e8 17 51 00 00 0f 1f 80 00 00 00 00 f3 0f 1e fa 53 48 89 fb 48 8d 3d 79 3e 21 00 ff 15 7b 44 21 00 <80> bb 1f 03 00 00 00 75 14 8b 83 18 03 00 00 85 c0 74 18 31 f6 48
Jul 20 09:18:25 alpha systemd[1]: Mounting FUSE Control File System...
Jul 20 09:18:25 alpha systemd[1]: Mounted FUSE Control File System.
Jul 20 09:18:25 alpha abrt-hook-ccpp[683438]: Process 683432 (mlds_0.920_x86_64-pc-linux-gnu) of user 985 killed by SIGSEGV - dumping core

Turns out you need to have fuse installed to run mlds.. please install the fuse package and see if that helps.

That was it. I have about 10 WUs running now. Will see how they do before installing fuse on the remaining machines.

Hello,

Encountering almost the same error. I am using Archlinux and having fuse-common, fuse2 and fuse3 packages installed.

fuse: device not found, try 'modprobe fuse' first
open dir error: No such file or directory

Any idea? `modprobe fuse` didn't return anything, nothing changed.

Is FUSE enabled in your kernel?

Right after `modprobe fuse`, tasks started to run smoothly. So you were right, I just had to add fuse to modules load at startup, by creating a fuse.conf in /etc/modules-load.d/ containing "fuse" as per this wiki.
Then `lsmod | grep fuse` shows up "fuse" after reboot :)

Thanks!

Interesting. I'm running MLC on Arch Linux, too, and no extra configuration was needed to get it running. /etc/modules-load.d is empty in my case, yet the fuse module has been loaded anyway.