Nov 20, 2022 20:05:08.306 [0x7fb5dc2e1b38] ERROR - [Req#dc617a/Transcode/ep3v6sffxn5xtf1v74zyzvta/01a4e170-44dc-4530-baf1-4bdf798d4a21] Error while decoding stream #0:1: No space left on device
What “space” is it talking about here? I have monitored filesystems on both the server and client and nothing is running out of space.
Server Version#: 1.30.0.6406
Player Version#: 1.57.1.3358-5fd2a504
both of these are linux boxes, but have also duplicated the issue with Plex on roku 7.0 build 19. I have logs but only see the error with verbose logging turned on. An assistance would be greatly appreciated.
ChuckPa, I monitored the temp filesystem, as well as all others, and nothing approached being full. I am unfamiliar with inotify slots. Can you provide methodology to check max quantity and availability?
ChuckPa, that link pointed to an article focused on synology. I am running an Ubuntu instance, so after searching max watches inotify, I found the control file, /proc/sys/fs/inotify/max_user_watches, managed by sysctl. The quantity was already at 65536, and even though I only have 15105 directories, I tried doubling the quantity. This did not help. As it only occurs during a transcode, I changed my temp transcode directory to an area with 100’s of gigs of free space, still no joy. The film in question is ‘Blue Thunder’. The audio track is dolby truehd which does seem to fit your description. The easiest to reproduce spot is at 1:42:27. If I play the ac3 - 2 channel track, it plays fine, but the truehd track locks up at that point. Is there any other pointers/suggestions you could provide, or is there something more than verbose mode I could enable to help diagnose and correct this?
ChuckPa, was wondering if this is still being investigated. I noticed and installed another 1.30 release and tried it, but the problem still persists. Downgraded back to 1.29.2 for the moment, but was hoping to see a resolution on this issue.