Optimizer broken? or my Server?

Plex Media Server NAS & Devices
,
1

Server Version#: 1.32.2.7100-7000
Player Version#: Synology Nas 7 - I have no clue what this means.

About 2 weeks ago Plex started to slow and was almost unusable. I re-installed Plex onto a new volume on my Nas. I swapped the database files and it seemed to be working but slow still. I went to optimize the database and it breaks Plex! My server becomes unavailable. I let it run until the next morning and it never works.

Each morning - My Nas has kicked me out and the Plex server still sucks. Is there anyone else experiencing this?

It’s making calls to everything on my network (Xbox, sonos, alexa, ect)

[NSB/SSDP] Parsing SSDP schema for http://192.168.1.43:9080 - is the only line i could get before my server went unavailable this morning. I can stop the server but it just starts the process over. Eventually I can get back in but it’s not usable really.

Any help would be so appreciated.

<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Plex Media Server Logs_2023-05-19_10-28-05.zip (4.8 MB)

2

Same here. It seems that it only breaks when the server is doing also something else. So when all scheduled tasks start. When doing a manual optimization I got it to work when the server was not doing anything. Looking at the logs it seems more and more threads lockup when the server is doing something else while optimizing. Maybe the database is unavailabe during optimization and when other things try to use it they get stuck and the optimization also gets stuck?

3

So I’m not insane! I can usually figure out where I made the mistake. This has been bad.

I agree with the scanning and other tasks. It’s swapping metadata because “something has changed”.

I stopped the server and restarted. Here are the logs for anyone that can help -
Plex Media Server Logs_2023-05-19_10-28-05.zip (4.8 MB)

I tried to get the Database files and they won’t download. I can get them from the folder but I don’t know if that is the same from the application.

I have some large playlists. I would like to keep them!

Looking through other posts - There is something bigger going on. I have many of the problems in the other posts as well.

4

Does not seem that the threads are locking in a similar way in you case. Could probably also be just something wrong in the database.

5

It freaks out when i hit that download button. The webpage starts to lose connectivity.

I’m frustrated!

Do you by chance know what -SSDP departed after not being seen for 26.761483 seconds: 192.168.1.60 (XBOX)

I get that Plex can ID stuff on my network. But what does that have to do with optimizing my database?

Plugin’s are not enabled nor do I have any. I understand the protocol. I just don’t understand why it keeps checking that. Or, why its involved.

6

@ChuckPa will probably have to help you guys. If your database is damaged, he has a repair tool which can help

You could also have some kind of network connectivity issue as @olazapa pointed out

There are all kinds of benign errors in logs that are very misleading to a user. It may be your exact problem, some other kind of problem, or not a problem at all

You can very easily end up down a 4 hour Google rabbit hole that leads you nowhere

I would wait for Chuck to look over your logs before I did anything but you can give the tool a shot if you feel comfortable trying it

7

OMG! thank you. I hit optimize again and for some reason I was able to stay on the console longer. It went further this time but still lost server connectivity (it does go further each time which is why I keep at it!). I saw it verifying my IP address. It shouldn’t matter but would installing the server with the VPN on matter? The VPN only covers my Mac and not my NAS. The web console would be on VPN but on network. I will wait for @ChuckPa to look.

8

This kind of stuff? :slight_smile:

May 19, 2023 04:42:36.066 [547454619872] DEBUG - Updating part with ID=247306 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E1.mp4]
May 19, 2023 04:42:36.168 [547454619872] DEBUG - Doing expensive tags write for 'Join or Die' because something changed.
May 19, 2023 04:42:37.698 [547454619872] DEBUG - Updating part with ID=247307 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E2.mp4]
May 19, 2023 04:42:37.773 [547454619872] DEBUG - Doing expensive tags write for 'Independence' because something changed.
May 19, 2023 04:42:38.661 [547454619872] DEBUG - Updating part with ID=247308 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E3.mp4]
May 19, 2023 04:42:38.736 [547454619872] DEBUG - Doing expensive tags write for 'Don't Tread on Me' because something changed.
May 19, 2023 04:42:39.022 [547454619872] DEBUG - Updating part with ID=247309 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E4.mp4]
May 19, 2023 04:42:39.046 [547454619872] DEBUG - Doing expensive tags write for 'Reunion' because something changed.
May 19, 2023 04:42:39.061 [547488370912] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.1.43:9080
May 19, 2023 04:42:39.156 [547527606496] DEBUG - [HttpClient/HCl#126] HTTP/1.1 (0.1s) 200 response from GET http://192.168.1.43:9080 (reused)
May 19, 2023 04:42:39.516 [547454619872] DEBUG - Updating part with ID=247310 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E5.mp4]
May 19, 2023 04:42:39.545 [547454619872] DEBUG - Doing expensive tags write for 'Unite or Die' because something changed.
May 19, 2023 04:42:39.778 [547454619872] DEBUG - Updating part with ID=247311 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E6.mp4]
May 19, 2023 04:42:39.806 [547454619872] DEBUG - Doing expensive tags write for 'Unnecessary War' because something changed.
May 19, 2023 04:42:39.992 [547454619872] DEBUG - Updating part with ID=247312 [/volume2/Plex 2/TV Shows/John Adams/JOHN_ADAMS_S1_E7.mp4]
May 19, 2023 04:42:40.006 [547454619872] DEBUG - Doing expensive tags write for 'Peacefield' because something changed.

Possible causes:

  1. A shell script running in the background which is forcibly setting permissions on the Synology (this is bad as of 1.32.0). There is a smarter way of doing it.

  2. Other programs modifying anything with date/time of the file.

  3. The file contents itself still in flux (like downloading directly into the area PMS monitors for media. — ALL download programs should only give PMS complete files.

I can’t help but comment on that terrible naming scheme.

JOHN_ADAMS_S1_E7.mp4 → JOHN ADAMS - S01E07.mp4

FileBot and the other media managers are
a) cheap
b) automatically make it perfect.
c) A win for everyone :sunglasses:

I use FileBot:

/volume1/media/tv/{n}/Season {s.pad(2)}/{n} - {s00e00} - {t}
-or-
/syno//media/tv/{n}/Season {s.pad(2)}/{n} - {s00e00} - {t} (from my workstation)

You can even add Genre into the mix if you want further refinement.

9

That was the first DVD I ripped! I am better now. I didn’t know there was such a thing as FileBot!!! Would have saved me a ton of time. lol. I am a little better now.

Some of the messaging in the console cracks me up.

How do i fix this? Why does it only happen when I optimize? I don’t copy straight into PMS. I wouldn’t be able to put together a shell script. I turned off every other server in my nas for 2 weeks while i tried to troubleshoot what went wrong. When I copied in the db from the folders, I stopped the PMS. I didn’t view the full file before putting it into Plex. I check a few spots i n the video.

I use norton (elicit’s laughs) to check the files but maybe something was on a file? My PMS is working but super slow as it is creating thumbnails.

Would moving media from one folder to another do it? I hit scan after moving some files and it hasn’t been even close to the server it was beforehand.

I am always learning. Thank you for the tip.

10

Upon re-read.

Am I looking at the files or the network?

(sorry, long week here)

11

You are looking at the files from the web UI, troubleshooting area, download logs.

It doesn’t like when i try to download the database I can upload the db May 5th backup (NAS file folder). The one i renamed with the blobs.db. I have no clue if they are the same. It’s all kind of jibberish to me

12

And no worries! Thank you so much for the help! If it’s Monday or later, I’ll live.

13

NO NO NO.

You can’t just move that around.

The Blobs DB is mated to the Library DB.

They contain ID numbers which must match

There is an option here… Slow to implement but will work.

  1. STOP PMS
  2. Abandon the existing server data (we rename)
  3. We create a fresh server instance (a new AppData)
  4. Stand up a fresh server
  5. Either from Plex history download -or- from the tool I have, restore the history.

Results:

  1. Clean DBs

Apologies if I sound terse. (Iate hour here and tired)

I’ll provide further instructions if desired.

14

I followed the instructions on the website. I stopped the server. I went to the folder - PlexMediaServer - app data- login support - databases. I moved the files out. I renamed my backup db files both library and blobs to end in .db. I then restarted the system. The problems existed before then.

This worked a while ago. My server worked incredibly well until 2 weeks ago. I don’t think it has anything to do with my issues. My apologies for not explaining better above

15

I would try installing from an older db if i were to try again!

16

Is there a way to export playlists and collections? (I have access to them). I would totally start over without putting in a backup db if I could upload them in.

Thanks again! The help is much appreciated.

18

im not smart

19

I reinstalled from an older database and selected beta over public. That seems to have fixed 99% of the issues. I still am seeing PMS get stuck on this - CERT: incomplete TLS handshake from [::ffff:192.168.1.6]:63398: sslv3 alert certificate unknown (SSL routines)

Is there anything i can do to get past it?

20

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