Hi, Since a couple of years I have a Hardkernel N2, running (actually booting) a Kodi implementation called CoreElec. That CoreElec is based on Ubuntu (I tried to run OpenSuse on the N2-box, but gave up in the end). All the media CoreElec should present are on an OpenSuse box, running TW. It nfs-mounts a few dir's on that TW box containing audio, video and pictures. That has worked years without problems. But since a few months, I can mount the nfs dirs, grab some content, and then transferring stops. Even worse, from that point on all other OpenSuse boxes with nfs-mount to that server lose their nfs-connections too. That I can only repair by rebooting the server. Systemd commands to restart the nfs deamon on the server hang endlessly, so that is no solution it seems. I've done some googling for finding log files for nfs, but found no answers so far. Any ideas here? Would be much appreciate (as always....) regards, Jogchum Reitsma
Moin, On Sat, 08 Apr 2023, 11:03:30 +0200, Jogchum Reitsma wrote:
Hi,
Since a couple of years I have a Hardkernel N2, running (actually booting) a Kodi implementation called CoreElec. That CoreElec is based on Ubuntu (I tried to run OpenSuse on the N2-box, but gave up in the end).
All the media CoreElec should present are on an OpenSuse box, running TW. It nfs-mounts a few dir's on that TW box containing audio, video and pictures.
That has worked years without problems. But since a few months, I can mount the nfs dirs, grab some content, and then transferring stops. Even worse, from that point on all other OpenSuse boxes with nfs-mount to that server lose their nfs-connections too. That I can only repair by rebooting the server. Systemd commands to restart the nfs deamon on the server hang endlessly, so that is no solution it seems.
I've done some googling for finding log files for nfs, but found no answers so far.
Any ideas here? Would be much appreciate (as always....)
I guess you are using the built-in NFS client in Kodi, aren't you? To be honest I found that quite unreliable and therefore use a different setup on my HTPC (I do all this on openSUSE Tumbleweed and/or Leap 15.4): 1. Install autofs as an automounter 2. Activate the /net map: /net -hosts 3. Create some links to the media files from your server in your $HOME directory; this is what I have here: Music -> /net/server/path/to/Music/files Pictures -> /net/server/path/to/Pictures/files Video -> /net/server/path/to/Video/files 4. Remove all your current entries in Kodi's database and replace them with normal directory entries As a result, Kodi will use autofs to automount the NFS implementation of the underlying OS and access the files as if they were local. Another thing you might want to check is, if CoreElec is current or not; some months ago openSUSE removed support for NFSv2 and I'm not sure if NFSv3 is still supported. Make sure that your server exports the files using NFSv4!
regards, Jogchum Reitsma
HTH, cheers. l8er manfred
Goejûn (Frisian for good evening...), CoreElec does not allow installing additional software, though I suppose it could be hacked one way or the other. apt-get (CoreElec is built upon Ubuntu) is not present. This is CoreElec's reaction when issues apt-get from a ssh shell: libuv.so.1.0.0 apt-get There is no working 'apt-get'. 'apt-get' is a command to install, update and remove software which is stored in a non local repo. 'apt-get' does nothing then connecting to such repo, downloads the software, unpacks the software, updates a big local database with all filepaths and other informations about the installed software or removes or updates installed Software. With LibreELEC it is not possible to change the system for security and stability reasons so even 'apt-get' would not be able to do this. We also dont have and want to maintain such a repo for various other great reasons. Also Ubuntu or Debian packages are often outdated and not compatible with LibreELEC TIP: use Kodi's addon browser to enhance your LibreELEC system On the TW side, NFSV4 is activated (in Yast), but is that enough to be sure that it is used exporting files? CoreElec get updates very seldom, while TW of course is updated almost daily - well, about weekly, in my case. If behaviour changes suddenly, one tends to think the cause is more on the side where the most changes take place. I made a fresh install of CoreElec, but the behaviour stays the same. It should support NFS4, though. I have no idea if it has anything to do with this problem, but dmesg shows lots of messages like [zo apr 9 20:34:36 2023] netdata[7630]: segfault at 200 ip 00007fc6a9649aa7 sp 00007ffcf5a08250 error 4 in libuv.so.1.0.0[7fc6a9643000+1e000] likely on CPU 14 (core 2, socket 0) [zo apr 9 20:34:36 2023] Code: b1 57 78 85 c0 74 0c 5b 31 c0 5d 41 5c 41 5d 41 5e c3 90 48 8b 47 08 41 bd 01 00 00 00 41 be 01 00 00 00 4c 8d 25 73 80 01 00 <8b> a8 00 02 00 00 83 fd ff 75 28 8b a8 f8 01 00 00 41 bd 08 00 00 Always the same Code:, and it occurs also after a fresh reboot. regards, Jogchum Op 08-04-2023 om 12:08 schreef Manfred Hollstein:
Moin,
On Sat, 08 Apr 2023, 11:03:30 +0200, Jogchum Reitsma wrote:
Hi,
Since a couple of years I have a Hardkernel N2, running (actually booting) a Kodi implementation called CoreElec. That CoreElec is based on Ubuntu (I tried to run OpenSuse on the N2-box, but gave up in the end).
All the media CoreElec should present are on an OpenSuse box, running TW. It nfs-mounts a few dir's on that TW box containing audio, video and pictures.
That has worked years without problems. But since a few months, I can mount the nfs dirs, grab some content, and then transferring stops. Even worse, from that point on all other OpenSuse boxes with nfs-mount to that server lose their nfs-connections too. That I can only repair by rebooting the server. Systemd commands to restart the nfs deamon on the server hang endlessly, so that is no solution it seems.
I've done some googling for finding log files for nfs, but found no answers so far.
Any ideas here? Would be much appreciate (as always....) I guess you are using the built-in NFS client in Kodi, aren't you? To be honest I found that quite unreliable and therefore use a different setup on my HTPC (I do all this on openSUSE Tumbleweed and/or Leap 15.4):
1. Install autofs as an automounter 2. Activate the /net map: /net -hosts 3. Create some links to the media files from your server in your $HOME directory; this is what I have here: Music -> /net/server/path/to/Music/files Pictures -> /net/server/path/to/Pictures/files Video -> /net/server/path/to/Video/files 4. Remove all your current entries in Kodi's database and replace them with normal directory entries
As a result, Kodi will use autofs to automount the NFS implementation of the underlying OS and access the files as if they were local.
Another thing you might want to check is, if CoreElec is current or not; some months ago openSUSE removed support for NFSv2 and I'm not sure if NFSv3 is still supported. Make sure that your server exports the files using NFSv4!
regards, Jogchum Reitsma HTH, cheers.
l8er manfred
On Sun, 09 Apr 2023, 20:52:39 +0200, Jogchum Reitsma wrote:
Goejûn (Frisian for good evening...),
CoreElec does not allow installing additional software, though I suppose it could be hacked one way or the other. apt-get (CoreElec is built upon Ubuntu) is not present. This is CoreElec's reaction when issues apt-get from a ssh shell:
libuv.so.1.0.0 apt-get
There is no working 'apt-get'. 'apt-get' is a command to install, update and remove software which is stored in a non local repo. 'apt-get' does nothing then connecting to such repo, downloads the software, unpacks the software, updates a big local database with all filepaths and other informations about the installed software or removes or updates installed Software. With LibreELEC it is not possible to change the system for security and stability reasons so even 'apt-get' would not be able to do this. We also dont have and want to maintain such a repo for various other great reasons. Also Ubuntu or Debian packages are often outdated and not compatible with LibreELEC TIP: use Kodi's addon browser to enhance your LibreELEC system
On the TW side, NFSV4 is activated (in Yast), but is that enough to be sure that it is used exporting files?
CoreElec get updates very seldom, while TW of course is updated almost daily - well, about weekly, in my case. If behaviour changes suddenly, one tends to think the cause is more on the side where the most changes take place.
I made a fresh install of CoreElec, but the behaviour stays the same. It should support NFS4, though.
I have no idea if it has anything to do with this problem, but dmesg shows lots of messages like
[zo apr 9 20:34:36 2023] netdata[7630]: segfault at 200 ip 00007fc6a9649aa7 sp 00007ffcf5a08250 error 4 in libuv.so.1.0.0[7fc6a9643000+1e000] likely on CPU 14 (core 2, socket 0) [zo apr 9 20:34:36 2023] Code: b1 57 78 85 c0 74 0c 5b 31 c0 5d 41 5c 41 5d 41 5e c3 90 48 8b 47 08 41 bd 01 00 00 00 41 be 01 00 00 00 4c 8d 25 73 80 01 00 <8b> a8 00 02 00 00 83 fd ff 75 28 8b a8 f8 01 00 00 41 bd 08 00 00
Always the same Code:, and it occurs also after a fresh reboot.
What's the kernel version on that system? CPU 14 sounds to me like a system that should be capable to run openSUSE. I tried to stick with one of the various prebuilt Kodi images, but in the end I decided it's much better and easier to set it up. Perhaps that's still an option for you.
regards, Jogchum
Cheers. l8er manfred
<...>
[zo apr 9 20:34:36 2023] netdata[7630]: segfault at 200 ip 00007fc6a9649aa7 sp 00007ffcf5a08250 error 4 in libuv.so.1.0.0[7fc6a9643000+1e000] likely on CPU 14 (core 2, socket 0) [zo apr 9 20:34:36 2023] Code: b1 57 78 85 c0 74 0c 5b 31 c0 5d 41 5c 41 5d 41 5e c3 90 48 8b 47 08 41 bd 01 00 00 00 41 be 01 00 00 00 4c 8d 25 73 80 01 00 <8b> a8 00 02 00 00 83 fd ff 75 28 8b a8 f8 01 00 00 41 bd 08 00 00
Always the same Code:, and it occurs also after a fresh reboot. What's the kernel version on that system? CPU 14 sounds to me like a system that should be capable to run openSUSE. I tried to stick with one of the various prebuilt Kodi images, but in the end I decided it's much better and easier to set it up. Perhaps that's still an option for you.
Oops - rereading my last post I see that I didn't express myself clearly enough: the dmesg messages are on the Tumbleweed system, not on the CoreElec... uname -a on the TW-box: Linux linux-mkay 6.2.8-1-default #1 SMP PREEMPT_DYNAMIC Wed Mar 22 18:56:06 UTC 2023 (221c28f) x86_64 x86_64 x86_64 GNU/Linux Sorry for the misunderstanding! regards, Jogchum
participants (2)
-
Jogchum Reitsma
-
Manfred Hollstein