oh I’m done with all the scanning, I was just wondering if that was a good way to get automatic updates on folders with a larger number of subfolders
How many folders? In total, including nested, is it > 8192 ?
almost 30k.
And weirdly, now that all my plex files are in the same shared folder, it doesn’t seem that automatic library update are triggering for any libraries.
Is that related to the new folder structure ?
100% related.
The default Linux limit is 8192. You have exceeded the default.
It’s not a big deal. This value is easily increased. It’s a run-time tunable kernel parameter.
A. SSH into the box.
B. Increase the default table size
sudo -su root
echo fs.inotify.max_user_watches=65536 >> /etc/sysctl.conf
sysctl -p
C. Restart PMS
Should you ever reinstall DSM, or it stop working after a DSM update/upgrade, you will need put this again.
that solved it !
again thanks for everything !
Add another crash during the night, otherwise everything was running much smoother, any ideas ?
Just an observation - why do you run with debug logging disabled if you are having issues you need investigating ?
A crash report without the debug logging for activity up to the time of a crash is often insufficient to identify the problem
Well I thought I was done with crashing issues
@Hamilcar said:
Well I thought I was done with crashing issues
if you have disabled debug logging then debug logging is off and when we crash we cannot retrospectively go back in time and enable debug logging !
I get that, I thought there was enough information without it.
@Hamilcar said:
I get that, I thought there was enough information without it.
Not what was happening that led to the crash. All there would be is the crashing thread backtrace - sometimes this is enough. A lot of times one would need to see what that thread was doing beforehand and that would be through debug logging
Anyway - if logs are provided they should always have debug logging and for it ideally to have been enabled before the last launch of Plex Media Server rather than in-flight
Thanks, I’ll see if it happens again
I will still follow up what is in the crash report but a crash dump only identifies where we crashed - the logs add the context
I have what I think is a known bug where every music library scan triggers a refresh of metadata, do you think that’s related ?
I’m on latest stable PMS version by the way.
@Hamilcar said:
I have what I think is a known bug where every music library scan triggers a refresh of metadata, do you think that’s related ?I’m on latest stable PMS version by the way.
I know it is related to scanning jobs
Do you use command line for scanning job or are all invoked by Plex Media Server automatic action / Plex Web user invoked scans ?
Looked at the dump - now need the context.
So will have to get the next crash logs to see what scanner job was running and what parameters it had and if the issue is relating to the job in general or specific media
Automatic action or plex web.
Thanks - will have to wait for next crash and with debug logging enabled beforehand
Well, since my last reply, everything has been running really smoothly.
Thanks again to everyone for all your suggestions.