I recently upgraded a machine from Mint 20.3 to Mint 21. I was running BOINC v7.20.2 before the upgrade: when I finished, BOINC was there, but at version 7.18.1

So, Mint 21 couldn't handle the PPA source I'd used before (subsequently confirmed), but knew how to load a version (still running fine) from its own resources. But I didn't see where it came from.

I chose Mint in the first place because I'm an experienced user and developer for Windows, and I wanted an easy transitional pathway for my first fumblings with Linux. I think first about using the GUI tools provided by Mint, and only drop back to terminal when absolutely necessary.

Found it:

When I installed Mint 21 and then apt install boinc packages, I got 7.18.1 (pre-release). I read on the forums (somewhere, I forget where) that the 'pre-release' tag was a mistake and should have been taken out before release. Had no problems with it. I've got multiple clients on the same machines and it all works fine.

On the subject of Mint 21, I've installed the 32bit libraries (following Ubuntu 22 instructions):

sudo apt-get install lib32ncurses6 lib32z1 lib32stdc++-12-dev

but the HadSM4 tasks are failing with the familiar 'computation error' on start. Has anyone else found this? The complicating factor is this is a WSL instance. I have Mint 21 on another machine and everything works fine on there.

BOINC v7.18.1 for Linux is a rogue release. BOINC never officially released v7.18.1 for the classic desktop operating systems - only for Android. My interpretation is that the Linux Repo community mis-read the release notes, and went ahead anyway. But nobody has ever owned up.

Some repos got it to work anyway, others report errors. When we finally get v7.22.(0), I'll kick butt until everyone's on the same page. (NB - there'll be a hotfix release for MacOS 13 and Xcode 14 only in the next few days, to fix a graphics / screensaver problem. For every other OS - ignore it.

BOINC v7.18.1 for Linux is a rogue release. BOINC never officially released v7.18.1 for the classic desktop operating systems - only for Android. My interpretation is that the Linux Repo community mis-read the release notes, and went ahead anyway. But nobody has ever owned up.

Which boinc version did you eventually put on your Mint 21 Richard? I couldn't tell from the earlier messages.

And I'm interested to know if you've (or anyone) had any errors from Mint21 with the 32bit libraries (re: my earlier message).

I ended up (so far) keeping the v7.18.1 from the repos. I got errors trying to re-attach to the PPA for test releases:

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.qwXTG8l2nT/gpg.1.sh --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys E36CE452F7C2AE96FB1354901BCB19E03C2A1859
gpg: key 1BCB19E03C2A1859: "Launchpad costamagnagianfranco-ppa" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

I've emailed Gianfranco, but not had a reply.

My installation was an in-situ upgrade from Mint 20.3, which had working 32-bit libraries. I haven't tried to run a CPDN task since then: is there an easy way to check whether the libraries are still there and working, or should I just grab a task and try it? Everything else, like GPU drivers, survived the upgrade.

My installation was an in-situ upgrade from Mint 20.3, which had working 32-bit libraries. I haven't tried to run a CPDN task since then: is there an easy way to check whether the libraries are still there and working, or should I just grab a task and try it?

Grabbing a task is the ultimate test of course. Try running 'sudo dpkg --print-foreign-architectures', if you get 'i386' Mint should have 32bit compatibility libraries installed from the earlier version & they should have been updated along with the 64bit ones during the upgrade. If I remember right (not at my PC right now), they are either in /usr/lib or /usr/lib32.

It passed the 'i386' test, so I've grabbed one (well four, actually, but I'll hold three back) - see how it runs while I'm out at the pub.

Glenn, your computers are only reporting 1 task in progress on WSL2 Mint and none on regular (no errors on either). I was curious to see what errors you're getting. I don't think Mint is a standard WSL distribution so you must have done a custom kernel installation. That could be a problem but not sure why it would be. I got tasks on WSL2 Ubuntu 22.04 and after about 8 hours they're still running fine.

is there an easy way to check whether the libraries are still there and working, or should I just grab a task and try it? Everything else, like GPU drivers, survived the upgrade.

run ldd on the executable and it will list dpendencies. You may then need to do some research to work out exactly which package contains the one you want for a particular distribution. Sometimes in the past, I have found the right package when the instructions don't work by increasing the version number by one. If there are unmet dependencies these will be shown.

ldd hadsm4_um_8.02_i686-pc-linux-gnu
	linux-gate.so.1 (0xf7f5f000)
	libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7f20000)
	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7e19000)
	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7e14000)
	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7a00000)
	/lib/ld-linux.so.2 (0xf7f61000)

Thanks both. The task is running, and well into its stride - over 2.5%. I can pull out details of the library file versions installed in the morning, if anyone needs them.

And the pub team is looking happy with 'a noisy night' * - not been too many of them recently. A good end to a trying week.

(*) In that pub, meaning 'a lively buzz of conversation' - not anything more sinister.

Glenn, your computers are only reporting 1 task in progress on WSL2 Mint and none on regular (no errors on either). I was curious to see what errors you're getting. I don't think Mint is a standard WSL distribution so you must have done a custom kernel installation. That could be a problem but not sure why it would be. I got tasks on WSL2 Ubuntu 22.04 and after about 8 hours they're still running fine.

I get computation error very quickly after it starts. The classic symptom of a library issue. Installing a clean Mint in WSL was an attempt to see if it would work as my WSL Ubuntu is a bit messy now. Neither works despite making sure I had the libraries in place (ldd - as Dave says). I thought the ld config files were messed up with Ubuntu, but now I'm wondering whether it's my WSL installation. Anyway, I've given up with it, life's too short. Black Friday is coming up and there are some tempting reductions on AMD processors to build another PC....

The servers have stubbornly refused to give my two quiet machines any HadSM4, probably knows I prefer OpenIFS tasks, which I thought might be out today but last minute checks have delayed to next week.

This one failed with

unzip:  cannot find or open /mnt/d/boinc-client-linux/boinc-client/projects/climateprediction.net/hadsm4_se_8.02_i686-pc-linux-gnu.zip, /mnt/d/boinc-client-linux/boinc-client/projects/climateprediction.net/hadsm4_se_8.02_i686-pc-linux-gnu.zip.zip or /mnt/d/boinc-client-linux/boinc-client/projects/climateprediction.net/hadsm4_se_8.02_i686-pc-linux-gnu.zip.ZIP.

This is different from the standard missing libs error.

<stderr_txt>
../../projects/climateprediction.net/hadsm4_8.02_i686-pc-linux-gnu: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

</stderr_txt>

Makes me wonder about a permissions error of some sort?

unzip: cannot find or open /mnt/d/boinc-client-linux/boinc-client/projects/climateprediction.net/hadsm4_se_8.02_i686-pc-linux-gnu.zip
That's not a missing lib problem. boinc client can't find the actual model executable which lives in the 'projects' directory. If you have run hadsm4 tasks before this will already exist in that directory, unless the version number has increased in which case it should have been downloaded for the task.
1/ check the full path shown in the error : does that directory actually exist? I note it's not /var/lib/boinc-client/.
2/ if the directory exists, check ownership; is it owned by 'boinc'? (or do you start it manually as yourself?)
3/ as it's not /var/lib/boinc-client, are the links from /var/lib ok? Or if you use --datadir on the boinc commandline, check that path, or check the path in the systemctl override file.
4/ if all that checks out, check the file size of the hadsm4_se_8.02_i686-pc-linux-gnu.zip file, is it zero bytes? If it exists try unzipping it yourself.
5/ if the file does not exist, or unzipping it fails, I suggest do a 'reset project' from the boincmgr window (with the correct --datadir), which will trigger a re-download of the files.

My guess is there's something wrong in the bionc config. I also move my boinc-client dir and have more than once got ownership wrong.

Running ldd on the binary for last night's Mint 21 task (still running fine) gives:

ldd hadsm4_8.02_i686-pc-linux-gnu
	linux-gate.so.1 (0xf7fb2000)
	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7f91000)
	libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7f8c000)
	libstdc++.so.6 => /lib/i386-linux-gnu/libstdc++.so.6 (0xf7d58000)
	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7c50000)
	libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7c29000)
	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf79f4000)
	/lib/ld-linux.so.2 (0xf7fb4000)

Glenn, I may have an idea as to why you're having issues with WSL2. Looking at the error log of prior tasks (on Ubuntu) such as this one, https://www.cpdn.org/result.php?resultid=22227096, if understand it correctly, it seems like you're trying to run BOINC on WSL2 but your files are on Windows drive. Is that right? If so, that seems like a complicated set up and although I can't say why specifically this doesn't work, I'm not surprised that it doesn't. I know I have issues accessing some BOINC directories on Ubuntu using Windows File Explorer.

Your one CPDN task on WSL2 Mint is still showing in progress, still hasn't been reported as error. If your Mint set up is also complicated that could be the reason Mint isn't working either.

It seems to me like you've complicated things somewhere. :-) Installing everything with default parameters and in default locations, there should be no issues. I have WSL2 Ubuntu 22.04 on Ryzen 5900X and Intel i7-4790 and both work fine. I made a modification to Linux BOINC client to be able to control it from the Windows BOINC manager on both PCs for easier management but other than that everything is default.

I don't know how big this new release was but it got emptied out pretty quickly this time, probably just bad luck that you didn't get any on other machines.

Glenn, I may have an idea as to why you're having issues with WSL2. Looking at the error log of prior tasks (on Ubuntu) such as this one, https://www.cpdn.org/result.php?resultid=22227096, if understand it correctly, it seems like you're trying to run BOINC on WSL2 but your files are on Windows drive. Is that right? If so, that seems like a complicated set up and although I can't say why specifically this doesn't work, I'm not surprised that it doesn't. I know I have issues accessing some BOINC directories on Ubuntu using Windows File Explorer.

It seems to me like you've complicated things somewhere. :-) Installing everything with default parameters and in default locations, there should be no issues. I have WSL2 Ubuntu 22.04 on Ryzen 5900X and Intel i7-4790 and both work fine. I made a modification to Linux BOINC client to be able to control it from the Windows BOINC manager on both PCs for easier management but other than that everything is default.

I'm open to all suggestions. I could try that though I don't think that's it. OpenIFS tasks run just fine, it's only the HadSM4.

The WSL image (all Ubuntu files and boinc executables) are still in their default system location. I only moved the /var/lib/boinc-client dir off my NVMe as I didn't want it hammered (it has Windows on it too). The only caveat I found was you need to enable extended metadata so that userid & groupid can be set correctly on a mounted disk (see https://devblogs.microsoft.com/commandline/chmod-chown-wsl-improvements/). Otherwise WSL & Windows boinc-client co-exist happily on my internal HDD in their own location (both win11 & ubuntu clients write to the same HDD in separate dirs).

Without frequent tasks it's quite time-consuming to test different things. And frankly, I'd rather spend my time fixing the 32bit issue. Sarah's given me the virtual machine they use to build HadSM4 so I was going to have a look at that. Could also be hardware? (not something I know much about) but this HP MB has already given me trouble installing more RAM. Another test would be to create virtualbox Ubuntu rather than WSL and see if that works. But, without tasks, it's tedious.

If I get some spare time I'll create a new WSL Ubuntu and try it. I'll let you know and send you a (virtual) prize if it's right :)

I'm open to all suggestions. I could try that though I don't think that's it. OpenIFS tasks run just fine, it's only the HadSM4.

OpenIFS tasks run in the slots directories. HadSM4's run in the task directories which are sub-directories of projects/climateprediction.net/

Hopefully that difference is the clue you need.

To be fair, HadSM4 calls the executables from the slot directory and uses that as the working directory, but most of the calls are softlinks: BOINC automatically follows them back to the project directory.

Mine is running in slot 6:

26 items, totalling 6.1 MB (6.1 MB on disk)

/var/lib/boinc-client/slots/6# dir -s -h
total 5.9M
5.8M 172075			    4.0K hadsm4_a0tn_201311_4_938_012155629.zip
4.0K a0tn_938_atmos.gz		    4.0K hadsm4_data_8.02_i686-pc-linux-gnu.zip
   0 boinc_lockfile		    4.0K hadsm4_se_8.02_i686-pc-linux-gnu.zip
8.0K boinc_mmap_file		    4.0K hadsm4_um_8.02_i686-pc-linux-gnu.zip
4.0K boinc_task_state.xml	    4.0K ic_N144_200302_000017.nc.gz
4.0K boinc_ufs_cpdnout1.zip	     12K init_data.xml
4.0K cpdnout1.zip		    4.0K ozone_c6_N144_1310-1409.gz
4.0K cpdnout2.zip		    4.0K SO2DMS_c6_N144_1310-1409.gz
4.0K cpdnout3.zip		       0 stderr.txt
4.0K cpdnout4.zip		    4.0K sulpc_ox_A2_1990_N144L38.gz
4.0K cpdnout_out.zip		    4.0K uvc_GLO_ice_water_030507.gz
4.0K cpdnout_restart.zip	    4.0K VOLC38_LR.gz
4.0K hadsm4_8.02_i686-pc-linux-gnu  4.0K xpaep_Q_2013_c5day_s6.gz