Have a look at: https://github.com/LibreELEC/LibreELEC.tv/issues/7589 for an immediate fix.
Medium term - we are looking at: https://github.com/LibreELEC/LibreELEC.tv/issues/7602
ugh, forgot to check the issues, I just overlooked the forum and found nothing in Google. Thank you for the incredibly fast answer!
Hello everybody,
I have a problem since last major update to LE 11 on a Raspberry Pi 4. I have a couple of sshfs shares that were automatically mounted via systemd service files at boot time. Now they do not start automatically anymore, and I cannot start them manually neither through systemd. I can mount the drives via command line using the 'sshfs' command (in fact, using the same command that is specified on the unit file). I saw previous problems with a similar setup, but again, this was working OK until I updated last week.
Any ideas? Thanks 
systemd status:
× storage-nfs-Folder.mount - Mount folder from drive
Loaded: loaded (/storage/.config/system.d/storage-nfs-Folder.mount; enabled; preset: disabled)
Active: failed (Result: exit-code) since Sun 2023-03-19 11:13:53 CET; 11min ago
Where: /storage/nfs/Folder
What: /storage/.kodi/addons/virtual.network-tools/bin/sshfs#root@drive:/shares/Folder
CPU: 4ms
Mar 19 11:13:53 libreelec systemd[1]: Mounting storage-nfs-Folder.mount...
Mar 19 11:13:53 libreelec mount[1137]: /storage/.kodi/addons/virtual.network-tools/bin/sshfs: error while loading shared libraries: libfuse3.so.3: cannot open shared object file: No such file or directory
Mar 19 11:13:53 libreelec mount[1133]: mount: mounting /storage/.kodi/addons/virtual.network-tools/bin/sshfs on /storage/nfs/Folder failed
Mar 19 11:13:53 libreelec systemd[1]: storage-nfs-Folder.mount: Mount process exited, code=exited, status=127/n/a
Mar 19 11:13:53 libreelec systemd[1]: storage-nfs-Folder.mount: Failed with result 'exit-code'.
Mar 19 11:13:53 libreelec systemd[1]: Failed to mount storage-nfs-Folder.mount.systemd unit file:
# This is a sample service script to mount NFS shares.
# Please read carefully the comments in this file. For production usage
# you can remove all comments (lines beginning with "#") from this file.
[Unit]
# The description should be used to explain what this servicefile is for
Description=Mount folder from drive
# if we do network mounts like here we *require* 'network-online.service'
# which checks if the network is online
Requires=network-online.service
# our scripts must start *after* 'network-online.service', on timeout and if
# 'network-online.service' fails we can not mount and this scripts fails too
After=network-online.service
# usually we mount networks shares because we want they avaible *before* XBMC starts.
# so XBMC has access to this mounts from beginning. Note: this slows down the boot!
Before=kodi.service
[Mount]
# The share we want mount
What=/storage/.kodi/addons/virtual.network-tools/bin/sshfs#root@drive:/shares/Folder
# Where we want mount this share
Where=/storage/nfs/Folder
# Any options you usually use with the "-o" parameter in the mount command
Options=allow_other,reconnect,default_permissions,IdentityFile=/storage/.ssh/drive
# filesystem type
Type=fuse.sshfs
[Install]
# The target is used by 'systemctl enable <name_of_this_file.mount>' to link
# this service to a runlevel for starting on boot. usually 'multi-user.target'
# is ok here.
WantedBy=multi-user.target
# Important:
# this file must be renamed to <mountpoint>.mount where <mountpoint>, is the FULL path
# where the share will be mounted but slashes "/" MUST BE REPLACED with dashes "-" with .mount
# as extension.
# This means, if we want mount to "/storage/movies2" (see above "Where=/storage/movies2")
# then this file must be renamed to 'storage-movies2.mount' and can be enabled via ssh with the
# command 'systemctl enable storage-movies2.mount'currently working manual command (what + options + where):
/storage/.kodi/addons/virtual.network-tools/bin/sshfs -o allow_other,reconnect,default_permissions,IdentityFile=/storage/.ssh/drive root@drive:/shares/Folder /storage/nfs/Folderfyi, the solution I have managed to keep using updated versions of this add-ons is to use the linuxserver docker repositories. It's possible to keep current (Thoradia version) data by making a backup, or by setting the current config folder of the corresponding addon as the /config volume in the docker command.
Hello thoradia ,
Thanks for the repo, it has been really helpful .
I have been problems with lidarr lately. Every basic error ("couldn't download media cover", "the operation has timed out", for example) ends with an application crash. Although libreelec eventually restarts lidarr again, this keeps happening, flooding me with logs and wearing off my sd card, until eventually lidarr just stops restarting.
I chatted with lidarr developers over discord and they told me to switch from the mono core to the NET one. I manually downloaded a new lidarr version, ran it with both cores, and this problem (crashing after a seemingly normal error) does not occur [1].
I wanted to know if there are plans to change the core lidarr uses in Thoradia... I saw that it was already changed for Radarr at least
[1] I don't get why it doesn't occur when executing the downloaded version with the Mono core, but well... if it helps, here are a couple of pastebins with my crash issue: [1] [2]
Hello,
awiouy There seems to be an error with the plugin currently, Syncthing stopped running for me.
I tried to run the command found on the unit file ( orclex you can find it on /storage/.kodi/addons/service.system.syncthing/system.d/service.system.syncthing.service) but I get the following error:
syncthing: error: --no-default-folder: bool value must be true, 1, yes, false, 0 or no but got "y" (from envar STNODEFAULTFOLDER="y")Of course, changing the 'y' for a 1 in
/storage/.kodi/addons/service.system.syncthing/bin/syncthing-service works great, but just wanted to let you know .
Thank you both, I’ll take a look at the possibilities then :).
Hello everybody,
I am trying to set up wireguard on my libreelec@rpi4 but I am having troubles doing it as a "split tunnel". I only want the rpi to connect to my wireguard server so I can then access the rpi+library from the outside. Therefore, on the rpi config, I would like to set
WireGuard.AllowedIPs = 10.100.100.0/24Which is the subnet of the VPN. But when I do that, if I check the routing table of the rpi, it is:
default dev wg0 scope link
10.100.100.0/24 dev wg0 scope link src 10.100.100.5 Therefore, the wireguard interface is set as the default one, by connman I guess, and I cannot change it (I tried `ip route add default via 192.168.1.254 dev eth0` manually without success).
Does anybody have any pointers? Thanks!
fpcalc is part of the libchromaprint-tools package, which is not included in libreelec.
So audio recognition will not work until the executable is included in lidarr with a location fix.
A workaround is to mount / as writable and create a link in /bin to where you placed the fpcalc executable.
I am most surprised though that a Mono application is written to rely on a OS-specific package. How does Lidarr work in Windows then?
I would just leave it off. It's pretty resource intensive and practically useless, except for audio verification (and you can probably verify if a song is the wrong one, anyway)
Thanks for your answer!
Yeah, I don't need it, I just wanted the notifications (which I have connected for "healt_h issues" through Telegram) to stop.
Regarding your Windows comment, according to the wiki:
Lidarr can use chromaprint audio fingerprinting to identify tracks. This depends on an external binary, which is distributed with Lidarr for Windows and macOS but must be provided independently on Linux.
Hello,
Thank you for your work .
I am constantly getting the following error in Lidarr:
fpcalc could not be found. Audio fingerprinting disabled.
I already downloaded a fpcalc binary compiled for armh and put it on my LibreElec path, but it still doesn't find it. I ask here instead of creating an issue, because I don't know if this would belong to Lidarr, or to Thoradia...
Thanks!
