Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libfuse3.so.3 missing in LE11 #7589

Closed
chris42 opened this issue Mar 11, 2023 · 10 comments
Closed

libfuse3.so.3 missing in LE11 #7589

chris42 opened this issue Mar 11, 2023 · 10 comments

Comments

@chris42
Copy link

chris42 commented Mar 11, 2023

Just updated on LE11, now my sshfs mounts are gone. Searched the logs and found:

Mar 11 09:11:49 mymc systemd[1]: Starting sshfs.nas.service...
Mar 11 09:11:49 mymc sshfs[781]: /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 11 09:11:49 mymc systemd[1]: sshfs.nas.service: Control process exited, code=exited, status=127/n/a
Mar 11 09:11:49 mymc systemd[1]: sshfs.nas.service: Failed with result 'exit-code'.
Mar 11 09:11:49 mymc systemd[1]: Failed to start sshfs.nas.service.

I have system-tools and network-tools installed (also reinstalled them already, no change). Would have expected a "libfuse3.so.3" library in /usr/lib, however there is nothing to be found regarding fuse.
The sshfs command I am doing is:

/storage/.kodi/addons/virtual.network-tools/bin/sshfs -o ro,reconnect,ServerAliveInterval=5,ServerAliveCountMax=3,IdentityFile=/storage/.ssh/id_ed25519_nas,port=22 mymc@nas:/ /storage/nas

Something might be misconfigured in the addon package or install?

@heitbaum
Copy link
Contributor

/storage/.kodi/addons/virtual.network-tools/

Have you restarted since adding the addon? I’m pretty sure the libraries should be there, but are not activated until LibreELEC is restarted.

# find /storage/.kodi/addons/virtual.network-tools/ | grep libfuse
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so.2
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so.3.12.0
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so.2.9.9
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so.3

@chris42
Copy link
Author

chris42 commented Mar 12, 2023

I am pretty sure I rebooted in between, as I saw the error for the nas service on the boot screen. Will have time later today, then uninstall network tools, reboot, install, reboot, report back.

@chris42
Copy link
Author

chris42 commented Mar 12, 2023

So tested this quickly, but still getting the error, that the libraries cannot be found. The libraries are on the system, however they are not being used/found by sshfs.

# find /storage/.kodi/addons/virtual.network-tools/ | grep libfuse
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so.3.12.0
/storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so.3
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so.2.9.9
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so
/storage/.kodi/addons/virtual.network-tools/lib/libfuse.so.2

Maybe sshfs needs additional library paths or linking to /usr/lib is needed?

@heitbaum
Copy link
Contributor

LibreELEC:~ # sshfs
missing host
see `sshfs -h' for usage
LibreELEC:~ # ldd /storage/.kodi/addons/virtual.network-tools/bin/sshfs
/usr/lib/libarmmem-v7l.so (0xf7eb0000)
libfuse3.so.3 => /storage/.kodi/addons/virtual.network-tools/lib/libfuse3.so.3 (0xf7e86000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf7d13000)
libc.so.6 => /usr/lib/libc.so.6 (0xf7ba0000)
/lib/ld-linux-armhf.so.3 => /usr/lib/ld-linux-armhf.so.3 (0xf7eda000)

@chewitt
Copy link
Member

chewitt commented Mar 12, 2023

Make sure you delete the cached packages in /storage/.kodi/addons/packages else Kodi will reinstall from the cache and not from the online version (in case that's an issue).

@heitbaum
Copy link
Contributor

@chris42 - just tested here and I have it “not erroring” - maybe via the systemd script it is… but from the prompt it seems to find the libraries.

@mglae
Copy link
Contributor

mglae commented Mar 12, 2023

LE10 is including libfuse in /usr/lib of the image because of ntfs-3g. It can ever be found in the default lib path.

LE11 dropped ntfs-3g and libfuse from the image. The library path to the addon has to be added to environment before used.

@chris42 The usual work around is using the profile to update the paths:

ExecStart=/bin/sh -c ". /etc/profile;exec sshfs -o ro,reconnect,ServerAliveInterval=5,ServerAliveCountMax=3,IdentityFile=/storage/.ssh/id_ed25519_nas,port=22 mymc@nas:/ /storage/nas"

@chris42
Copy link
Author

chris42 commented Mar 12, 2023

Yepp, using the profile does work. Thanks for the hint and sorry for the confusion.

@chris42 chris42 closed this as completed Mar 12, 2023
@reitzig
Copy link

reitzig commented Jul 27, 2023

I've been using a .mount file with

[Mount]
What=/storage/.kodi/addons/virtual.network-tools/bin/sshfs#user@host:/some/dir
Type=fuse.sshfs
Where=/var/media/host/dir
Options=ro,allow_other,reconnect,ServerAliveInterval=15,IdentityFile=/storage/.ssh/id_rsa

This broke after upgrading von LE9 (I know) to LE11 with a similar error:

/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

However, just running

/storage/.kodi/addons/virtual.network-tools/bin/sshfs -o ro,allow_other,reconnect,ServerAliveInterval=15,IdentityFile=/storage/.ssh/id_rsa user@host:/some/dir /var/media/host/dir

in an SSH shell works.
I think that's the same issue as above, and I can confirm that renaming the file to .service and replacing the [Mount] section with

[Service]
Type=forking
ExecStart=/bin/bash -c ". /etc/profile;exec /storage/.kodi/addons/virtual.network-tools/bin/sshfs -o ro,allow_other,reconnect,ServerAliveInterval=15,IdentityFile=/storage/.ssh/id_rsa user@host:/some/dir /var/media/host/dir"

works. Thanks for the hints!

Looking forward to a fix that allows me to switch back to .mount, which seems cleaner!

@heitbaum
Copy link
Contributor

@reitzig The permanent fix will come along with #7602

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants