This has been getting slowly worse with each update to the plex app but now it’s completely inoperable.
the plex app will not find any files while scanning the library even though the plex user has read/write.
I’ve followed the corrupted database guide, I’ve followed the clean reinstall guide, SSH’d in, deleted all database files and metadata to start with a clean slate. New install still doesn’t find any files when scanning.
have confirmed through command line and webGUI that the plex user has read/write access to the folders needed.
So I’m out of ideas. It looks like a permissions issue, except there is no visible/provable permissions issue. Which means there’s no way to fix it.
running top over ssh seems to confirm that Plex Media Server and the scanning agents are running as the plex user. There’s nothing in the release notes for the new 1.12 that would imply it has been patched.
happy to include any details I might have left out if anyone has an idea.
Start a scan, wait 30 seconds then capture Log files please?
Thanks for replying @ChuckPA . I went to go do this, and low and behold, it started finding some content… without me having changed anything at all in the interim. Unfortunately the app still barely works. Trying to play a movie on the media center pc client stalls, or jumps to can’t connect to plex server, or says there was an unexpected error, or plays for a few minutes, or says unexpected error, or says unexpected error.
plex media server log has a bunch of errors like:
Mar 09, 2018 16:36:03.509 [] ERROR - Error issuing curl_easy_perform(handle): 56
Mar 09, 2018 16:36:03.509 [] WARN - HTTP error requesting GET http://127.0.0.1:39016/system/agents/search?
plex media scanner.log has a bunch of errors like:
Mar 09, 2018 16:34:10.968 [] ERROR - Error issuing curl_easy_perform(handle): 28
Mar 09, 2018 16:34:10.969 [] ERROR - Error parsing content.
Mar 09, 2018 16:34:10.969 [] ERROR - Error parsing XML response for update.
Mar 09, 2018 16:36:03.512 [ ERROR - Error parsing content.
Mar 09, 2018 16:36:03.512 [] ERROR - Exception caught while attempting to match metadata on item 2206: Error parsing file
it has the feeling now of something that’s bottle-necked, but the synology isn’t maxing ram or CPU. Is there anything in particular you want me to search for? It’s 100MB of logs already, having only been running for a day or two.
I will need to see the complete log set (settings - server - help - download logs - attach the ZIP file), captured 30 second after you attempt the playback then terminate it, to know what’s really happening.
If you’ve just added a bunch of files all at once, a common problem is PMS’s database needs optimizing (compacting). The Synology processors , because they aren’t big intel cpus, suffer from this sooner than others.
The symptoms you see are:
- Slow dashboard responses
- Slow to load metadata
- Slow to start playback
- Stuttering during playback.
Sound familiar?
