Server Version#: 1.42.2.10156
Player Version#: N/A
My PMS logs are filled with that error. What causes it and how to fix it? My transcoding device has a TB of free space.
I don’t think it’s an inotify problem:
root@server-pc:~# sysctl fs.inotify.max_user_watches
fs.inotify.max_user_watches = 124764root@server-pc:~# find /proc/*/fd -user plex -lname anon_inode:inotify
-printf ‘%hinfo/%f\n’ 2>/dev/null | xargs cat | grep -c ‘^inotify’
7967root@server-pc:~# find /mnt/md0/4K /mnt/md0/Movies /mnt/md0/Friends /mnt/md0/TV\ Shows/ /mnt/md0/Movie\ requests /mnt/md0/Home\ Movies -type d -print | wc -l
7958
The client app playback is most likely paused and sending websocket keepalive.
The Plex apps stopped doing this some time ago (a few years) so shouldn’t be happening with any of the current apps.
When does it occur ? Which player ?
I think my friend was streaming from his Samsung TV (not 100% sure, I’ll ask him tonight). He was watching a show and got about 30 minutes in and his Plex client threw a “an unexpected playback problem occurred” error. He hit OK and was able to get right back in and continue watching.
Since I wasn’t sure if it was just a random fluke or something with Plex, I started looking through the logs and saw TONS of ‘no space left on device’ errors filling up the log files so I thought I’d post here to try and find out why the log files were polluted with that error. He said he had it paused for about 10 minutes in total.
The clients throwing this event is harmless.
It is just messy in the logs.
The “No space left on device” error is a problem which I will setup a VM for and see if I can recreate it.
I have more than enough media (thanks for your folder counts) to replicate.
Gut-feel is that it’s a Debian 13 issue as it doesn’t occur on other distros. I presume you’re fully up to date with updates ?
Yep, Debian 13 is fully up to date.
Good to know that the messy logs is nothing to worry about.
I’m going to have him do some more testing tonight. I’m hoping it was just a random error but I’ll let you know.
Good news… my friend watched another episode last night and didn’t encounter the error so I guess (hope) it was just a fluke.
I setup a new Debian 13 VM last yesterday (two attempts)
It blew up in my face – total failure.
If you have any suggestions, I’m willing.
