"This server cannot reach the Internet. Please verify Connectivity and try again."

I will give that a test this weekend - cheers!

I know I said I’d do this at the weekend, but I did it yesterday :slight_smile:

So here’s my logs after 1 day of DNS set to 8.8.8.8 / 8.8.4.4 - courtesy of your shiny new PlexData share - cheers for that! :slight_smile:

I did a quick search. There are a bunch of errors, but nothing returned when I specifically searched for getaddrinfo.

Plex Media Server.log (3.5 MB)

JC,
Most of that single log file is DVR.

Next time, would you Right-Click and create a ZIP of it like PMS does?

like this?
Plex Media Server Logs_2020-08-07_16-55-15.zip (5.8 MB)

Just like that :stuck_out_tongue: LOLOL

You should try making one from within FileStation now. I think you’ll like it
No need to upload it

Hello @Chucka.
I have a similar problem when scan music library…

@ciltocruz

There isn’t any “Premium Music” anymore per se. It’s all “music” now. That transition occurred several versions ago.

I will need to see DEBUG log files (the ZIP) which capture this.

Given music tends to consume all the notification slots on Linux systems easily, I very much would like to see PMS restarted in that log set. It will allow me to verify if this is simply a kernel table limit or not so we don’t waste efforts in the wrong area.

1 Like

Very well.
That’s how I’ll do it.

Do you want the zip records on this thread or in the theme that I opened a few days ago?

Thank you

@ChuckPa did my last logs show any improvement (with the google DNS)?

same problem here, but it seems that it happens with plex music scanner only! if you change library scanner to last.fm for example, it works normal.

Here are my logs.

If you want to dig deeper…

Plex Media Server.1.log:Aug 09, 2020 16:14:12.119

Plex Media Server Logs_2020-08-09_20-48-46.zip (6.1 MB)

@fractalizer

Can you please recreate that in a semi-fresh set of logs (PMS restarted in between tests)?

If you can easily recreate the failure and success, it would be ideal.

It would show Engineering a Before vs After example.

@ciltocruz

Thank you for the logs. Would you please turn the VERBOSE logging OFF?
Default setting is for it to be OFF. We rarely need Verbose. It wastes a great deal of space in the logs because the log buffers are fixed maximum size.

Is the system also doing a transcode (video playback) while it’s attempting t scan music? It appears to be given the remainder of the logs are filled with the logging of each datablock being sent (This is why we keep VERBOSE turned off).

What was the CPU loading? (The J1900 CPU isn’t very strong).

Perfect. Sorry to have the VERBOSE active. I’ve already removed it.

The problem is that I have followed what the colleague has commented here and now I am not able to reproduce the problem again…

If I succeed, I will write again.

If changing DNS to google, which seems to magically work for many, has resolved it, I’d let it go. It may sound strange to say that but Google DNS does seem to be the best solution for many – as weird as that may be.

it does seem to have worked, so thanks for that!

Any advice on the remaining errors?

Some ISPs modem/routers , of which BT is one, don’t allow for everything would like (the DNS Rebinding control being one).

If you aren’t having problems with anything, I would ignore them.
I would, however, make a note of them so we don’t get hung up on them in the future investigating anything which might come down the road.

OK, thanks!

so I cleaned, optimised, switched of debug level logging and restarted the server to get a simple picture of the outstanding errors (was going to leave it 24 hours and keep that log as a snapshot).

However, I just checked the log’s progression and have been inundated with errors ~500 in 10 mins.

They all seem to be (I think) related to intro detection (and some to do with my 3rd part EPG XML file which is down to me). Could you take a really quick look and confirm that for me and I will start another thread on it? …I appreciate I will need to switch debug back on to diagnose properly?
Plex Media Server.log (51.7 KB)

set debug. back on, restarted and waited 30 mins…
Plex Media Server.log (3.4 MB)

Separately, I was unable to copy the log via PlexData (worked fine with PMSLibShare’s Plex share) - I tried several times but always got this error: