[PROBLEM] Raspi 3b: Missing libaudiofile.so.1 after upgrade 4.2 -> 4.3

[TheOldPresbyope]

No MPD running and I can see this error in the daemon.log:
Oct  8 13:01:09 moodeB mpd[901]: /usr/local/bin/mpd: error while loading shared libraries: libaudiofile.so.1: cannot open shared object file: No such file or directory

This was on an instance of Moode that I'd not used for a few months, and I upgraded via the shell command as recommended. IIRC it was working OK last time I used it.

Suggestions? While I'd rather repair what I have, I'm open to just re-installing from scratch but I wanted to check before I upgraded a couple of other instances...

That's odd.

I just looked at a running moOde r4.3 (installed directly from image, not as an upgrade to r4.2)

Code:

pi@moode:/usr/lib/arm-linux-gnueabihf $ ls -l libaudio*
lrwxrwxrwx 1 root root     21 Mar 16  2017 libaudiofile.so -> libaudiofile.so.1.0.0
lrwxrwxrwx 1 root root     21 Mar 16  2017 libaudiofile.so.1 -> libaudiofile.so.1.0.0
-rw-r--r-- 1 root root 186272 Mar 16  2017 libaudiofile.so.1.0.0

The file dates suggest these should not have been touched in an upgrade, but I don' know the details of the upgrade process.

What does your broken moOde show? If only the links (e.g., libaudio.file.so.1) are missing you can recreate them from the command line using the ln command, e.g.

Code:

pi@moode:/usr/lib/arm-linux-gnueabihf $ sudo ln -s libaudiofile.so.1.0.0 libaudiofile.so.1

If the target file libaudiofile.so.1.0.0 itself is missing, then you could try copying it over from another moOde instance and recreating the link to it as above if it is missing too.

Please note that this is a bandaid fix. It does not address whatever mechanism caused the file and/or link to go AWOL. There may have been other breakage as well.

Regards,
Kent