Playback trouble since Kodi 19 update

Help and Support
1

Logs reproducing the error here: https://paste.osmc.tv/xasaqivale

The files are present on the server, and play fine with VLC.

Kodi reports that the file is either unplayable or unavailable, and asks to remove from library.

Doing an episode refresh makes it vanish from the library, then a rescan restores it. Then the file is playable.

I see “failed to mount NFS share” errors…but if I play a different file from the same TV show located on the same share in the same folder, it works.

Interestingly, the file I can now play was one of the ones I had trouble with previously.

For example, S05E07 gave me trouble. So I performed the above steps to “restore” it. While I was having trouble with S05E07, I launched S05E08. It played.

After watching S05E07, I went to watch S05E08, and it gave me the same error. I performed the steps and now it (and S05E09) are playable.

I bet after I watch S05E08, I will have trouble with S05E09… Which makes NO sense to me.

The Kodi database is a complete mess – I have run it both on MySQL (remote server) and local SQLite, and it seems that the database just plain gets corrupted a lot with a library as big as mine.

It’s been this way since it was still XBMC. Seems that there are no plans to make the database stop self-destructing. I have to completely delete and rebuild the database about every 6 months. And even though I do a full export to export watched state and I have advancedsettings.xml set to import watched state, it seems to pick and choose which episodes it will mark.

This is likely a Kodi (not OSMC) issue, but since I run a Vero4k, I thought I’d start here. Someone needs to completely redesign this database…

2

FYI, backend file server is TrueNAS Core 12

3

I suggest you check your wireless connection with iperf

4

I’ll check that, but these problems didn’t crop up until the update.

Unfortunately, going wired isn’t currently an option.

5 
Connecting to host san.jcdevs.com, port 5201
[  5] local 192.168.3.26 port 43784 connected to 192.168.3.21 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  13.1 MBytes   110 Mbits/sec    0    132 KBytes
[  5]   1.00-2.00   sec  13.4 MBytes   113 Mbits/sec    0    132 KBytes
[  5]   2.00-3.00   sec  13.3 MBytes   111 Mbits/sec    0    132 KBytes
[  5]   3.00-4.00   sec  13.3 MBytes   112 Mbits/sec    0    132 KBytes
[  5]   4.00-5.00   sec  12.2 MBytes   102 Mbits/sec    0    132 KBytes
[  5]   5.00-6.00   sec  13.3 MBytes   112 Mbits/sec    0    132 KBytes
[  5]   6.00-7.00   sec  13.5 MBytes   113 Mbits/sec    0    192 KBytes
[  5]   7.00-8.00   sec  13.7 MBytes   115 Mbits/sec    0    192 KBytes
[  5]   8.00-9.00   sec  13.8 MBytes   116 Mbits/sec    0    192 KBytes
[  5]   9.00-10.00  sec  13.5 MBytes   113 Mbits/sec    0    192 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   133 MBytes   112 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   133 MBytes   111 Mbits/sec                  receiver
6

That looks ok.
From your logs

2021-08-10 06:47:14.103 T:2832 INFO : WakeOnAccess [192.168.3.21] trigged by accessing : nfs://192.168.3.21:2049/mnt/Raid10/Files/Video/Movies/folder.jpg

And

2021-08-10 06:47:19.208 T:2832 ERROR : NFS: Failed to mount nfs share: /mnt/Raid10/Files/Video (mount_cb: command timed out)
2021-08-10 06:47:19.254 T:2776 DEBUG : NFS: Context for 192.168.3.21/mnt/Raid10/Files/Video not open - get a new context.
2021-08-10 06:47:24.270 T:2776 ERROR : NFS: Failed to mount nfs share: /mnt/Raid10/Files/Video (mount_cb: command timed out)

Could it be that your NAS is not waking up fast enough?

7

I see that in the power settings the wait time for network is turned off. Perhaps setting that to 30 seconds may help.

1 Like
8

NAS Doesn’t sleep. Ever. It also hosts VM block storage.

Again, this only cropped up after the KODI update, and all other machines can browse the NAS fine.

This may be my only machine that accesses those files over NFS, though… So I will make another NFS connection on another machine to see if there is some delay.

9

You have WOL enabled in your power settings

<setting id="powermanagement.wakeonaccess">true</setting>

so maybe try turning that off since your not using it and see if that makes a difference.