Plex Server not connectable after update to 1.40.2.8395

Plex Media Server NAS & Devices
1

Server Version#: 1.40.2.8395
Synology Model# DS1520+
Synology OS Version# DSM 7.2.1. 69057 (Update 3)

Just upgrade to the current version from 1.40.1.8227 and now I cannot connect. I tried rebooting the Synology but that did not help. I tried to downgrade by manually installing the previous version but it would not let me.

I use HyperBackup on the PlexMediaServer directory and wanted to see if anyoen knew if restoring the entire folder (my media is on a different share) would possibly resolve the issue?

Also, is anyone else having problems with this version?

UPDATE: The restore did not work, with the newer version so I tried to then downgrade by uninstalling (KEEP) and installing the older version. Not sure if the downgrade needed to be done first so tryiing the shared fodler restore again, then will reboot and see what happens


Any other advice is appreciated.

2

I updated to 8395 on 4/22/24 on my Synology NAS and now many of my .mp4 videos will not play. Plex just shows a spinning circle after pressing the play button. Re-encoding the files (I used Audials One 2024) to a different .mp4 compression allowed Plex to play the file, but I am not willing to re-encode the thousands of files that I have on my PMS
 I think the .mp4 decoder is broken in this version for some variations or compressions of files. I can’t tell as some files that won’t play are 720p HEVC Main 10 but others are 720p x 8 and they won’t play as well.

Unfortunately, Synology Package Center will not allow a roll-back to a previous version.

Server Version # 1.40.2.8395
Synology Model # DS1019+
Synology OS Version # DSM 7.2.1-69057 update 3

3

May we please have DEBUG log files (the ZIP file) which captures the failed playback attempt?

Your explanation of the problem implies the Codecs were unable to download.

ALSO:

  1. Uninstall the package – use the “Uninstall Only - KEEP” option
  2. Install lower version

(DSM does not allow downgrade. The packaging is written to support uninstall + reinstall and keeping your server data)

4

I am not having that issue. I cannot connect to my Plex library after the update, so not sure where to get any debug info from. I am trying the directory restore as that contains the all the relevant Plex files outside the media content (latest backup was at 3AM and Plex not used at all since then.) If that does not work I can try the uninstall - KEEP and then reinstall the previous version that was working. Am I missing anything in my gameplan?

5

@ssolomon

May I have the DEBUG Logs ZIP file so I can see what’s happening?

6

I have a qnap nas and the same problem. I installed the latest package last night and now my PMS is stuck on “running routine start up maintenace” and i my server is offline on all devices (tv, phone, tablet, web
)

Can i stop the service and reinstall the last pkg without damaging anything (luckily i save all install files
)

PMS version: 1.40.2.8395
QNAP Model TS873A-8G
QNAP OS Firmware QTS 5.1.5.2679

1 Like
7

Your choices are:

  1. LET IT RUN!
    – Every time you interrupt it, it starts over from the beginning.
    – if you are using Docker, there is a strong possibility it will never complete because certain Docker Images (health check) restart PMS before the Database schema upgrade completes.

  2. Install the previous (pre 1.40.x – recommend 1.32.8) ON TOP OF the existing version.
    – If you uninstall the package first, you’ll lose everything.

1 Like
8

It’s been running for about four hours now
 normally it starts up within about 20 minutes
 :confused:

I don’t think I have Docker installed
 I used PuTTY to log into it and tried “docker --version” and it returned “command not found”

I’ll give it another 24 hours then try rolling back. should I stop the service before manually installing the older package, or does it matter?

9

QNAP doesn’t have the docker command in the normal path.
Looking for “Container Station” in App Center will tell you if you have docker.

As for the startup time, I’ve seen large libraries need 3-4 hours.

I would use top / ps to watch for the pid (in case it changes)

10

I don’t have container station installed. I really haven’t messed with anything much, I bought the NAS specifically for my Plex server, so that’s pretty much all I have downloaded that’s not preinstalled


Are you talking about the PMS PID? will it change once the start up stuff is done? I’ve just been opening it to see if it loads


11

Which version of PMS did you have installed before this?

12

Most recent was 1.40.1.8227, and I started with 1.32.8.7639.

Prior to that I ran my server from an old Win10 Machine I wasn’t using for anything else.

13

If you were running 1.40.1 then there shouldn’t be such a huge delay in startup.
The heavy lifting of the schema changes is already done.

If you install the 1.40.1 which you have onhand ON TOP OF 1.40.2, does it startup ok?
This is effectively downgrading you to 1.40.1

14

downgraded to 1.40.1

it’s doing startup tasks, will report in if it finishes or tomorrow when i get home from work, whichever happens first


15

If it doesn’t finish,

  1. stop PMS
  2. Make a shared folder named PlexData
  3. Also make a folder somewhere to hold key files (for backup purposes)
  4. Filestation - Dive into PlexData → Plex Media Server
    – Copy the Preferences.xml (save it)
    – Dive further down and copy “Databases” (save it)

This way, if things go sideways, your server is still preserved

Then install 1.32.8

I don’t know how large or fragmented your DBs are but this shouldn’t take this long.
they will probably benefit from a good solid cleaning.

How skilled are you at the SSH command line?

16

It’s still doing startup maintenance, going on an hour now


I did have to back up all those files to preserve “watched” status and whatnot when I migrated from Win10 to the QNAP, pretty sure I did it through WinSCP because the QNAP GUI doesn’t access a lot of the root folders


After the migrating I did the database optimization and clean up


I’m not an expert with SSH by any means, but I do know how to log in through PuTTY and grew up with DOS 6.0, so i can follow directions at a terminal prompt
 haha

edit: just tried winscp
 I must have used putty to copy the database over to qnap, scp can’t see the hidden folders on qnap either

17

If, after a few hours, it doesn’t finish, we’ll abort it.

Plex on QNAP does respond to a “PlexData” shared folder
(it only needs 1 restart for it to find it)

Therefore, you’ll Stop, Start, Stop Plex.
You’ll see there is now the link “Plex Media Server” in the PlexData shared folder.

That’ll give you easy GUI access to all those buried files in Plex.

As for the shell work to do, Please consider,

  1. Plex stopped
  2. Download my tool from the link below,
  3. Put it in the “Public” shared folder
  4. Unzip it so you have “DBRepair.sh” there
  5. Control Panel - Telnet/SSH , enable it
  6. Using Putty, SSH into the QNAP
    – Your username & password (it won’t echo anything when entering password)
    – At the prompt: sudo bash and enter your password again
    – Now you’ll get the ‘#’ (root user) prompt.
  7. Now we run the DB tool (There are further instructions in the README)
  • /share/Public/DBRepair.sh
  1. The menu will pop up and identify itself as QNAP
  2. One at a time, STOP, AUTO, EXIT
    – “Auto” may take time. Don’t worry, It will not hang.
    – It’s very informative about what it’s doing
  3. Go back to App Center – Start plex

See if that helps.

Please don’t hesitate to ask questions.

18

I’ve started and stopped Plex a handful of times over the last 48 hours, but the only way I know to get to the database files is through SSH to get to the CACHEDEV folders
 I haven’t figured out how to locate them in the GUI
haven’t tried too hard, either but yeah


Grabbed your DBRepair files, got to step 7 above and I’m stuck. when I run ./DBRepair.sh I get :

line 7: syntax error near unexpected token “newline”
line 7: “<!doctype html>”

the quotations marks may be apostrophes on the front of those, my putty text is tiny at my current resolution


Also, I want to take a moment to apologize to the OP for completely threadjacking them


19

You downloaded the SH directly to Windows? (your browser gave you HTML and not the file downloaded)

The better action here is to download the ‘tar.gz’ file and put it in the Public shared folder

now, while still in the shell
cd /share/CACHEDEV*/Public

you can now list the files with the ls command. You’ll see the file.

Look at the README.md file. You’ll see the Installation examples I show about how to unpack the script from the tar.gz

20

I right click saved as and put it in /share/CACHEDEV1_DATA/Public

sudo bash
cd /share
chmod +x DBRepair.sh
./DBRepair.sh

Screenshot 2024-04-23 233131
Screenshot 2024-04-23 2331311031×666 34.7 KB