An Internet connection is required to scan library files. Music only is broken

Server Version#: 1.21.4.4079
Player Version#: 4.52.1

This issue has been reported for months but it continues to be a broken part of the music library scans in Plex. Each time I add a new album or track to my music library it does not automatically scan and find the files. If I attempt to scan the library I get a message saying “An internet connection is required to scan library files.” I have to either reboot my qnap NAS, or stop and restart the Plex server to get the files so they will scan once again. When there is a restart it seems to works for awhile. But, if I add files again the next day it is again broken. This is clearly a bug somewhere in Plex that has existed for so long it shocks me there has not been a fix.image

Would you please provide the DEBUG logs ZIP from PMs so we can look and see what triggered it?

I am not sure what that means or how to do it. Can you be more specific? Do you mean the logs when I enable debugging in Plex?

My apologies. Settings - Server (Upper right) - Troubleshooting (left side) - Download Logs.

Attach the ZIP file (drag and drop into the reply window, let it upload until the URL is shown), then click “Reply”.

I hope this is the right zip file. I had some trouble finding the troubleshooting menu, but here goes.Plex Media Server Logs_2021-02-24_14-52-05.zip (3.7 MB)

That’s exactly what I needed. Thank you!

This is really strange.

It used to happen a long time ago and then was solved.

If something is regressing, I’d love to figure it out.

BUT

in your case,

It’s matching anyway!

Feb 24, 2021 10:29:08.615 [0x7fe021c03780] DEBUG - Match: Fingerprinting rest of tracks in 4.4 sec.
Feb 24, 2021 10:29:08.615 [0x7fe021c03780] DEBUG - Match: Finding matches for barbara bonney, mary phillips, atlanta symphony orchestra, yoel levi - mahler: symphony no. 2; adagio from symphony no. 10
Feb 24, 2021 10:29:08.615 [0x7fe021c03780] DEBUG - Match: Album might be Various Artists: 0
Feb 24, 2021 10:29:08.617 [0x7fe021c03780] DEBUG - Match: Considering 1 releases from fingerprinting.
Feb 24, 2021 10:29:08.617 [0x7fe021c03780] DEBUG - Match: Ended up with 1 releases from fingerprinting.
Feb 24, 2021 10:29:08.617 [0x7fe021c03780] DEBUG - Match: Cache hit on 9cc4bfe6-5ded-41ce-8bf4-5909e24c38b6
Feb 24, 2021 10:29:08.617 [0x7fe021c03780] DEBUG - Match: We found 1 worthy releases and got back 1 album details.
Feb 24, 2021 10:29:08.617 [0x7fe021c03780] DEBUG - Match: Candidate: Gustav Mahler - Symphony no. 2 “Resurrection” (9cc4bfe6-5ded-41ce-8bf4-5909e24c38b6)
Feb 24, 2021 10:29:08.624 [0x7fe021c03780] DEBUG - Match: Computing track assignment (6 x 6)
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 01 / 01 - '1. Allegro Maestoso. Mit durchaus ernstem und feierlichae Aus druck' and 01 / 01 - 'Symphony no. 2: I. Allegro maestoso. Mit durchaus ernstem und feierlichem Ausdruck' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 02 / 01 - 'III. In ruhig fliessender Bewegung' and 02 / 01 - 'Symphony no. 2: III. In ruhig fliessender Bewegung' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 01 / 02 - '2. Andante Moderato. Sehr grmachlick. Nie eilen' and 01 / 02 - 'Symphony no. 2: II. Andante moderato. Sehr gemächlich. Nie Eilen' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 02 / 02 - 'IV. "Ullricht" Sehr feierlich aber schlicht' and 02 / 02 - 'Symphony no. 2: IV. “Urlicht”: Sehr feierlich, aber schlicht.' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 02 / 03 - 'V. Im Tempo des Scherozs. Wild herausfahrend' and 02 / 03 - 'Symphony no. 2: V. Im Tempo des Scherzos. Wild herausfahrend' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Distance between 02 / 04 - 'Symphony 10: 1. Adagio' and 02 / 04 - 'Symphony no. 10: I. Adagio' (Gustav Mahler) is 0.000000 ({'track_id': [0.00000], 'track_index': [0.00000], 'track_length': [0.00000]})
Feb 24, 2021 10:29:08.625 [0x7fe021c03780] DEBUG - Match: Album distance 0.000 — {'album': [0.00000], 'artist': [0.00000], 'tracks': [0.00000, 0.00000, 0.00000, 0.00000, 0.00000, 0.00000], 'year': [0.00000]}

(Distance = 0.0 is a perfect match)

Have you been able to figure out which album(s) it might be related to?

It does not seem to matter what I add to the music library, it always happens and has since at least December, may a bit sooner I don’t remember for sure. Today I loaded tracks and they did not automatically scan as they normally do. When I attempted to manually scan the music library I got the no internet error message. I stopped and restarted Plex and then I could manually scan the library for the music I had added. I assume that if I try it tomorrow it will happen again. This has been the pattern I have seen in any case.

Also, today after I restarted Plex and got the first files scanned I added a second set of files and they scanned automatically as always in the past. But, I suspect if I do the same tomorrow it will not work without a restart of Plex.

Is there anything obvious I should be doing differently?

There’s nothing obvious — yet :smiling_imp:

Let’s do a test so I can see what PMS does when it starts up.
This issue might be starting right at startup.

What’s prompting this is your comment about it no longer automatically scanning.
That is an indication unto itself (music libraries and photo libraries tend to cause it more often)

The strange errors after that now start to make sense.

Please do the following:

  1. Restart Plex
  2. Let it sit completely idle for the first 3-4 minutes (give it time to really settle)
  3. Download the logs again
  4. Attach them.

What I’m hoping to catch (which this sequence will) is what happens at startup.

Here you go.
Plex Media Server Logs_2021-02-24_16-38-15.zip (2.9 MB)

Thank you for that.

Your logs don’t show an indication of what I was first expecting but you are getting close to it. When you get another 3000-ish folders monitored by PMS, it will become apparent and we can address it then.

I did some digging.

Have you had this library in existence since it was called “Premium Music” ?

If so, then you are indeed seeing the old , now discontinued, “Gracenote” service.

That service, if PMS tries to talk to it, will get a sign-in authorization error and report exactly what you’re seeing.

The solution to this is:

  1. Check your music library to verify:
    a. Plex Music scanner (It cannot say “Premium”)
    b. Plex Music or Musicbrainz agent ( it cannot say “Premium”)

  2. Change as required.

  3. When done, “Refresh All Metadata” for the library section and make it rematch everything. Those things already matched to the new service will be ok. Anything not transitioned will be rematched.

  4. This might take a bit of time depending on how many tracks you have indexed.

I did not have Premium selected, but I likely did early on. The files go back as far as 2015 on my system. So, I adjusted the settings to Plex Music and let Refresh All Metadata run all night. Then this morning I selected Scan Music a couple of times again and got the same error message. Here are a fresh version of the logs from this morning.
Plex Media Server Logs_2021-02-25_06-51-45.zip (7.4 MB)

THank you for the updated logs.

This does confirm you still have something in there stuck in “Premium Music”.

( Please observe the Gracenote references )

mediaType=8&force=1&periodic=1&respectTags=1&guid=com%2Eplexapp%2Eagents%2Eplexmusic%3A%2F%2Fgracenote%2Fartist%2F052FE62E191F9FC5%3Flang%3Den&id=47605 (3 live) GZIP 9ms 752 bytes
Feb 25, 2021 03:52:06.617 [0x7fa97e970700] DEBUG - HTTP 200 response from GET http://127.0.0.1:32400/system/agents/update?mediaType=8&force=1&periodic=1&respectTags=1&guid=com%2Eplexapp%2Eagents%2Eplexmusic%3A%2F%2Fgracenote%2Fartist%2F052FE62E191F9FC5%3Flang%3Den&id=47605
Feb 25, 2021 03:52:06.617 [0x7fa97e970700] ERROR - Error response for update: 5 (Unhandled exception).
Feb 25, 2021 03:52:06.618 [0x7fa97e970700] DEBUG - Refreshing GUID: 'com.plexapp.agents.plexmusic://gracenote/artist/05C30844042782EB?lang=en'
Feb 25, 2021 03:52:06.619 [0x7fa97e970700] DEBUG - HTTP requesting GET http://127.0.0.1:32400/system/agents/update?mediaType=8&force=1&periodic=1&respectTags=1&guid=com%2Eplexapp%2Eagents%2Eplexmusic%3A%2F%2Fgracenote%2Fartist%2F05C30844042782EB%3Flang%3Den&id=77414
Feb 25, 2021 03:52:06.619 [0x7fa92c855700] DEBUG - Request: [127.0.0.1:52274 (Loopback)] GET /system/agents/update

One thing you can do to forcibly flip things around

  1. Edit the library settings
  2. Advanced tab.
  3. Plex Music Scanner and Last.fm agent
  4. Now force Refresh all metadata again.

If this doesn’t clear it, we may be stuck in a situation where a rebuild is required
( I will ask engineering about how to avoid this while you’re performing the Refresh )

I did get it cleared up, but the Refresh of Metadata caused me hours of issues with artists names. I have lots of classical albums, some rather obscure. It seemed that something must have occurred while refreshing where things got confused. I found up to about 10 recordings or so with the same repeated artist list which was always wrong. Most files were fine. But, I will likely be finding the messed up artist text for months to come. If I put at least part of the correct artist in and refreshed the metadata individually it fixed most of them. But, that was unfortunate. I am glad I can again scan as I add music files though.

Thanks for all your help.

I still have to stop and restart Plex after it has sat overnight. So, nothing you had me do accomplished anything other than to break my metadata. I have no interest in continuing to debug your broken code. So, I will wait for an update to come along that makes something that worked for years work again.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.