Server Version#: 1.18.8.2468
Player Version#: 4.22.2
I ripped a couple of CDs and put them on my Plex server the other day. I have two music libraries, a “staging” one where I just check to make sure that everything looks good, and then a main one with all of my music. Everything looked good in staging, so I moved them over to the main library.
A day or two later, I noticed that they weren’t listed in the main library. I clicked Scan Library Files and got the error message:
An internet connection is required to scan library files. Please check this server’s connection and try again.
But my server is connected to the internet. Remote Access has a green check mark, the TV library can pull down episode data, etc.
It works fine on the staging library, just the main one gets that error. I did notice that the staging library has a “Upgrade to Plex Music” option, although I’m not sure what that means since they both use the Plex Music scanner.
I wonder – as you are moving stuff from one library to another have you tried optimise database and empty trash so that deleted items (moved) are purged from the library they no longer exist in.
Also, if you goto settings -> manage -> libraries and do a full scan library files across all libraries does that help at all ?
Full logs also might be worth posting so folks can take a peek. That error might be a red herring and not the real cause of the problem but a symptom of some earlier failure.
I saw where you started to shutdown the server before it was finished initializing.
I need caution you on this. Your /data/pictures/from e drive/iPhoto./..........
seems to be keeping versions.
All those subdirectories will QUICKLY exhaust the default 8192 provided by the kernel.
Should you find PMS not automatically detecting new media, that’s why.
Mar 05, 2020 19:44:34.489 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102432/2XVo5ZLBRlGonaE1j%zbfg"
Mar 05, 2020 19:44:34.491 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102432/eROnuvZmTFOVn6aA9QIw%A"
Mar 05, 2020 19:44:34.494 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102432/p5EjI090QEqSzTDiddIfog"
Mar 05, 2020 19:44:34.496 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102655"
Mar 05, 2020 19:44:34.497 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102655/lItLKzCnRgyaA4Gm5EwPQA"
Mar 05, 2020 19:44:34.501 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102655/lWTmj5%wROav+tRNJ8dpDQ"
Mar 05, 2020 19:44:34.503 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102704"
Mar 05, 2020 19:44:34.504 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102704/CQoKiWR4R9uocpa4NvMsPg"
Mar 05, 2020 19:44:34.507 [0x148964ef9700] DEBUG - [Notify] Now watching "/data/pictures/from e drive/iPhoto Library.photolibrary/Database/Versions/2015/02/27/20150227-102704/G1nKGUDdSL6u30NIQlybZw"
Mar 05, 2020 19:44:34.508 [0x14896f2e2700] DEBUG - Shutting down with signal 15 (Terminated)
Mar 05, 2020 19:44:34.508 [0x14896f2e2700] DEBUG - Ordered to stop server.
Mar 05, 2020 19:44:34.508 [0x14896f2e2700] WARN - Timed out waiting for server to finish.
Mar 05, 2020 19:44:34.508 [0x148978d82b80] DEBUG - Stopping server...
Mar 05, 2020 19:44:34.508 [0x148978d82b80] DEBUG - HttpServer: Stopping server.
Mar 05, 2020 19:44:34.508 [0x148933dfe700] DEBUG - TranscodeJobManager: [Runnin```
Oh, thanks! I didn’t realize that iPhoto library was in there.
As for the second shutdown, I had hit restart (in unraids docker UI), but I wasn’t sure if it actually did anything, the server never seemed to go offline. I guess it was just faster than I expected. The second time I did a shutdown, waited a minute and then started it.
Has this same problem and didn’t know whether it was my NAS or Plex. This thread sent me in the right direction and I’m all good now. Just wanted to say thanks!
I have separate music libraries: 1 for Music and 1 for Video Game Soundtracks.
I randomly started receiving the “needs internet connection” error message when I tried to scan the Video Game Soundtracks library while the other Music library and all video libraries scanned without any issues (and added any new content to the home screen).
I was about to go the log route and continue the thread here, but it seems as though Plex has fixed itself with a server side restart of Plex Media Server.
Hopefully that helps out anyone else experiencing this recent glitch.
I started having this issue only on the MUSIC library immediately after the Plex issue last week with their servers. Now I cannot refresh my MUSIC library. Everything else works!
I’m not sure this will help anyone. I had this issue recently and I think i fixed with the steps below from memory.
It was on a remote server that has what I believe is Merger FS.
So my library points to
/home/gdrive-plex/Music
I added the local physical location as an additional folder to the above
/home/user/files/Plex/Music
Scanned my library.
I cant recall if this worked (You may wish to turn off “Empty trash automatically after every scan”
I then removed the Merger location. Maybe scanned again?
Then added it back Maybe scanned again?
Then removed the physical location and scanned and at this point it was definitely working.
I suspect IF this is what fixed it maybe someone can test by…
Turning off “Empty trash automatically after every scan”
Remove any library folders listed.
Add any empty folder.
Scan library
Switch back and scan again.
Turn “Empty trash automatically after every scan” back on.
If someone does the above test it would be wise to grab logs for the plex devs.
Restart plex, let settles for 2 mins or so as per their instructions, scan library and produce the error first before doing the above.
I’d like some clarification on the accepted answer in this thread, if possible. @ChuckPa wrote, “All those subdirectories will QUICKLY exhaust the default 8192 provided by the kernel.” I immediately had several questions:
Will exhaust 8192 … what, exactly? Directory handles? Thingamabobs? I tried googling “8192 subdirectory limit” and could not find an explanation.
“provided by the kernel” - what kernel? When people say “kernel”, I usually think “operating system”. But nfriedly never mentioned their OS. Is the referenced default something particular to Plex, or to an assumed OS, or is it common default across all OSes?
(I came across this thread because, like others, I’m having the same error message when asking Plex to “Scan Library Files” on my Music library which is quite large. I’m trying to scan files because some albums aren’t showing up, but the scan refuses to happen. The error message is clearly wrong because the server has internet access. Server is on MacOS Catalina running Plex Server Version 1.19.4.2935.)
When Plex watches a library for changes, what it really does, at least on Linux (my server runs Linux), is ask the operating system to notify it of any changes that occur in the top-level directory and every subdirectory. The Linux kernel has a default limit of 8192 directories that it can watch for changes. Every subdirectory counts against that 8,192 limit. There were more than that many subdirectories that my Plex instance was supposed to be watching, so it hit problems.
I don’t know this for a fact, but I expect that Mac OS has a somewhat similar limitation.
Thanks nfriedly. That is awesomely helpful. One of the perks of Linux, I guess - you know what the limits are. I can’t find any explanation of what the folder limit in APFS (filesystem) and/or MacOS might be… guess I gotta hope it’s high enough I never run into it.
Also, my problem mysteriously resolved itself. I just tried “Scan Library Files” again without having done anything since I last tried (when it didn’t work), and it worked. I am guessing something that Plex wanted to talk to (something MusicBrainz-related, maybe?) was temporarily offline or unavailable. And the error message is poorly written in a way that accuses me of it being my problem or fault, not Plex’s, which is too bad.
I had the same problem today with my Music library, with latest Plex server on QNAP NAS. Restarted the Plex server and the problem resolved.
But annoying, I tried to initiate the scan from the androids apps (both the Plex app and the Plex Dash app) yesterday, neither gave any feedback that there was a problem - so initially thought it must be some issue with the CD rips I added yesterday.
Thanks for that clarification. Sorry to bug you with another question. When you say that this limitation is for “When Plex watches a library for changes”, I understood that this limitation only exists when automatic scanning is activated. My question is whether the 8190 limitation also present for manual scans?
