Since the August update I’ve been experiencing what appear to be ever worsening problems accessing media on a Synology NAS source via NFS.
At first it started taking a long time to open the source to browse the files. Then longer, and longer, now over a minute. Then files would play but only after Wake On LAN got invoked a couple times, sometimes canceling that.
Last night for the first time, playing any media file resulted in blue circle of death. I rebooted OSMC a couple times, and the NAS too, with the same result.
Notable errors in log are:
2024-09-21 23:33:10.896 T:3753 debug <general>: CVideoPlayerVideo - video decoder returned error
2024-09-21 23:33:10.897 T:3753 debug <general>: ERROR check in pts error!
2024-09-21 23:33:10.897 T:3753 debug <general>: check in pts failed
This message repeated hundreds of times after hitting play.
Here’s the log – too long for paste.bin even tho i tried to cut it down.
Please upload the log via OSMC. This is only a Kodi log and is 100KB. The maximum upload via My OSMC is 10M currently so it should be possible to upload a full logs via this service
1 Like
is there a way to do that with this file? or are you suggesting i reproduce the issue(s) again? prefer to upload this file to somewhere you can access if that’s at all workable. thanks.
Thanks, Sam.
I went ahead and ran thru everything again, cleaner that way. Here’s the log. Here’s roughly what I did > with results:
- debug log on & reboot
- cold play a video from library (recently added tv, S02E01) > invoke wake on LAN, after 100%, timeout, the video not available error message, choice to remove from library, no.
- play same file again > plays fine
- play other episodes in same series > all play fine
- change profiles
- play a thought-to-be OK video(test_movie_ok.mp4) > another wake on LAN, stop WOL
- play same video > plays at first with only audio on green screen, stop
- play same video > plays OK audio & video, stop
- play problem video (test_movie_bad.avi) > blue ring of death forever, stop
- play test_movie_ok > blue ring of death forever, stop
- switch profiles to original / main
- play initial S02E01 video > blue ring of death forever, stop
- turn off debug logging and upload full logs (msg me if needed)
- save kodi.log and edit because it contains plain text password from a plugin
- upload so edited log, link above
note that the basic problems tested for here did not typically occur before last update and now are reproducible. namely:
- videos played with Synology NAS source over wifi at first invoke WOL, even after NAS has just been accessed, say with watching a prior movie and playing a new one
- WOL never finishes, but canceling the WOL after a few seconds usually results in being able to play video normally
- if you let WOL finish, it always returns error that file is no longer available and should remove?
- playing this certain “bad” .avi (*) results in blue ring of death and never plays, but doesn’t hang Kodi, can be stopped
- playing any vdeo thereafter, until kodi reboot, results in blue ring of death.
This “bad” avi plays OK in VLC on Mac.
Unfortunately these aren’t full logs so hard to tell, but if only one file is causing a problem then it may be problematic. You could disable hardware acceleration which might make it possible to watch it.
full logs sent by PM. thx.
Haven’t received anything, but it’s usually best to post full logs here so they can get an extra pair of eyes.
Can you also confirm if it’s just the one file causing an issue?
Understood. I wish there were a way to edit the ones uploaded through OSMC, cuz they may contain passwords and other info that shouldn’t be public. Or maybe / probably (for next time) there’s a way to get the “full logs” to edit locally first?
Just the (edited) kodi.log is linked above in the post with the enumerated list.
The one file is causing the biggest issue, but there are others described in detail above.
Circling back here, too. I believe the remaining problem is related to Wake On LAN. I disabled the feature to “try to wake up remote servers on access”, and now browsing and accessing files on the source (a Synology NAS) is as quick as expected, and as quick as before. That setting had always been on, so not sure what changed. Still I think the problem started with August update
Here’s some log snippets in debug mode when trying to access the source (192.168.0.101) from two different profiles.
PROFILE 1
2024-10-25 15:14:42.227 T:19453 info <general>: WakeOnAccess [192.168.0.101] triggered by accessing : nfs://192.168.0.101/volume1/kucing/
2024-10-25 15:14:42.228 T:19453 error <general>: socket failed: Permission denied (13)
2024-10-25 15:14:42.228 T:19453 info <general>: WakeOnLan - Magic packet send to '90:09:D0:58:8B:4F'
2024-10-25 15:14:42.228 T:19453 error <general>: socket failed: Permission denied (13)
2024-10-25 15:14:44.467 T:19425 info <general>: Skipped 11 duplicate messages..
PROFILE 2
2024-10-25 15:26:56.765 T:19590 info <general>: WakeOnAccess timeout/cancel while waiting for response
2024-10-25 15:26:56.765 T:19590 warning <general>: WakeOnAccess failed to bring up [192.168.0.101] - there may be trouble ahead !
2024-10-25 15:26:56.765 T:19590 debug <general>: Thread waiting 3458191616 terminating
2024-10-25 15:26:56.769 T:19197 debug <general>: ------ Window Deinit (DialogBusy.xml) ------
2024-10-25 15:26:56.770 T:19646 debug <general>: Thread waiting start, auto delete: false
2024-10-25 15:26:56.780 T:19646 debug <general>: NFS: Context for 192.168.0.101/volume1/olam not open - get a new context.
2024-10-25 15:26:56.780 T:19646 debug <general>: NFS: version: 3
2024-10-25 15:26:56.794 T:19646 debug <general>: NFS: Connected to server 192.168.0.101 and export /volume1/olam
2024-10-25 15:26:56.794 T:19646 debug <general>: NFS: chunks: r/w 131072/131072
2024-10-25 15:26:56.798 T:19646 debug <general>: Thread waiting 3458191616 terminating
2024-10-25 15:26:56.799 T:19197 debug <general>: Saving fileitems [nfs://192.168.0.101/volume1/olam/]