Plex Server not connectable after update to 1.40.2.8395

[ChuckPa]

I see what happened.

1. cd /share/CACHEDEV*/Public
2. copy and paste this on the SSH command line

 wget https://github.com/ChuckPa/PlexDBRepair/archive/refs/tags/v1.05.02.tar.gz
 tar xvf v1.05.02.tar.gz
 cd PlexDBRepair-1.05.02

Now you’ll be able to run it

For reference, It’ll look like this:

[chuck@lizum tmp.2013]$ wget https://github.com/ChuckPa/PlexDBRepair/archive/refs/tags/v1.05.02.tar.gz
--2024-04-24 02:37:30--  https://github.com/ChuckPa/PlexDBRepair/archive/refs/tags/v1.05.02.tar.gz
Resolving github.com (github.com)... 140.82.112.3
Connecting to github.com (github.com)|140.82.112.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/ChuckPa/PlexDBRepair/tar.gz/refs/tags/v1.05.02 [following]
--2024-04-24 02:37:30--  https://codeload.github.com/ChuckPa/PlexDBRepair/tar.gz/refs/tags/v1.05.02
Resolving codeload.github.com (codeload.github.com)... 140.82.114.9
Connecting to codeload.github.com (codeload.github.com)|140.82.114.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘v1.05.02.tar.gz’

v1.05.02.tar.gz                     [ <=>                                                    ]  37.44K  --.-KB/s    in 0.03s   

2024-04-24 02:37:30 (1.22 MB/s) - ‘v1.05.02.tar.gz’ saved [38341]

[chuck@lizum tmp.2014]$ tar xvf v1.05.02.tar.gz 
PlexDBRepair-1.05.02/
PlexDBRepair-1.05.02/Contributing.md
PlexDBRepair-1.05.02/DBRepair-Windows.bat
PlexDBRepair-1.05.02/DBRepair-Windows.zip
PlexDBRepair-1.05.02/DBRepair.sh
PlexDBRepair-1.05.02/License.md
PlexDBRepair-1.05.02/README.md
PlexDBRepair-1.05.02/ReleaseNotes
[chuck@lizum tmp.2015]$ cd PlexDBRepair-1.05.02/
[chuck@lizum PlexDBRepair-1.05.02.2016]$ ls -la
total 160
drwxr-xr-x  2 chuck chuck   159 Mar 26 14:42 ./
drwxrwxrwt 23 root  root   4096 Apr 24 02:37 ../
-rw-r--r--  1 chuck chuck  1964 Mar 26 14:42 Contributing.md
-rwxr-xr-x  1 chuck chuck 65526 Mar 26 14:42 DBRepair.sh*
-rw-r--r--  1 chuck chuck  7095 Mar 26 14:42 DBRepair-Windows.bat
-rw-r--r--  1 chuck chuck  1767 Mar 26 14:42 DBRepair-Windows.zip
-rwxr-xr-x  1 chuck chuck   965 Mar 26 14:42 License.md*
-rw-r--r--  1 chuck chuck 37722 Mar 26 14:42 README.md
-rw-r--r--  1 chuck chuck 29764 Mar 26 14:42 ReleaseNotes
[chuck@lizum PlexDBRepair-1.05.02.2017]

[tattooed_pariah]

that did the trick!

I think part of my problem may have been PMS running when it shouldn’t have been… DBRepair wouldn’t work because the process was hung… I had to kill -9 it.

DBRepair is running an auto check now. Thank you so much for your time tonight! I’ll report back when it’s done, but I gotta get some sleep, it’s midnight now and my alarm goes off at 0355 for work…

[tattooed_pariah]

Just got home from work… here’s the current status:

Mobile APP on android phone: no longer connected to any servers
PlexDash App on android phone: “???” where server name used to be
Windows Chrome Web Browser: also disconnected from server like my phone
Clicking “Open” in QNAP AppCenter: IP refused to connect

PMS confirmed running in both QNAP App Center and DBRepair tools… It’s like the server doesn’t exist anymore…

edit: figured maybe the clients were looking for the upgraded server they may have seen briefly so I reinstalled 1.40.2. Now when load “IP.Address:32400/web” It shows the XML screen with “Plex Media Server is currently running database migrations.”

I’ll let it run it’s course with that… hopefully I don’t have to wait 24+ hours for a result… lol

edit the edit:

I’m back in business! Thanks again @ChuckPa for all your patience and help! For some reason it’s not scraping Movie posters and threw in a lot of old movies as “recently added” but i’ll take it!

[ChuckPa]

The jump to 1.40.2 at this point was risky but guess it paid off.

The apps don’t care which version of the server they find.
They’re only looking for the server by its ID numbers (what you find in Preferences.xml)

I recommend, after everything is finished, run ANOTHER DBRepair.sh ‘auto’ pass.
The schema updates are a ‘heavy lift’ .

One thing you should be able to see:

1. Searches are much quicker
2. Library sections will load faster
3. Playbacks usually start faster

[EikeW]

Hi ChunkPa,
I had the Same issue with my Linux VM Ubuntu.
Everything Runs Fine and out of nowhere After the update to the latest Version i can‘t Connect to Plex anymore. Thank god i had an Backup so i Runs that and everything it good.
But the error was something Like could Not start up Blabla because something was too fast.

Maybe i will make a copy of the Server to another VM and reproduce the error but is guess ist all the same here.

[ChuckPa]

@EikeW

But the error was something Like could Not start up Blabla because something was too fast.

Can you make a tar.gz of the Logs for me so I can see the error before it gets lost?

[EikeW]

root@Plex-Server:/home/eike# service plexmediaserver start
Job for plexmediaserver.service failed because the control process exited with error code.
See “systemctl status plexmediaserver.service” and “journalctl -xeu plexmediaserver.service” for details.
root@Plex-Server:/home/eike# journalctl -xeu plexmediaserver.service
░░ The job identifier is 1210 and the job result is done.
Apr 26 07:39:15 Plex-Server systemd[1]: Starting Plex Media Server…
░░ Subject: A start job for unit plexmediaserver.service has begun execution
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has begun execution.
░░
░░ The job identifier is 1210.
Apr 26 07:39:15 Plex-Server Plex Media Server[1679]: /bin/mkdir: das Verzeichnis »/datastore/Application Support“ kann nicht angelegt werden: Keine Berechtigung
Apr 26 07:39:15 Plex-Server systemd[1]: plexmediaserver.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ An ExecStartPre= process belonging to unit plexmediaserver.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 1.
Apr 26 07:39:15 Plex-Server systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit plexmediaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Apr 26 07:39:15 Plex-Server systemd[1]: Failed to start Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished with a failure.
░░
░░ The job identifier is 1210 and the job result is failed.
Apr 26 07:39:20 Plex-Server systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ Automatic restarting of the unit plexmediaserver.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 26 07:39:20 Plex-Server systemd[1]: Stopped Plex Media Server.
░░ Subject: A stop job for unit plexmediaserver.service has finished
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A stop job for unit plexmediaserver.service has finished.
░░
░░ The job identifier is 1292 and the job result is done.
Apr 26 07:39:20 Plex-Server systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Apr 26 07:39:20 Plex-Server systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit plexmediaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Apr 26 07:39:20 Plex-Server systemd[1]: Failed to start Plex Media Server.
░░ Subject: A start job for unit plexmediaserver.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit plexmediaserver.service has finished with a failure.
░░
░░ The job identifier is 1292 and the job result is failed.

[ChuckPa]

@EikeW

1. Given /datastore is not the default location on Synology OR linux, where should this post be located?

2. Can you provide the actual, manually created, server logs (from the Logs directory) in either tar.gz or ZIP form ?

What you provided above doesn’t tell us anything except it looks like Ubuntu

[EikeW]

Yeah /datastore is my second ssd Witch is only the temp folder for transcoding.
I will do as soon as i have the Time today

[EikeW]

The Folder is empty

[EikeW]

Apr 26, 2024 10:35:33.313 [140523097832248] INFO - Plex Media Server v1.32.8.7639-fb6452ebf - Ubuntu PC x86_64 - build: linux-x86_64 debian - GMT 02:00
Apr 26, 2024 10:35:33.314 [140523097832248] INFO - Linux version: 22.04.4 LTS (Jammy Jellyfish), language: en-US
Apr 26, 2024 10:35:33.314 [140523097832248] INFO - Processor: 8-core Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Apr 26, 2024 10:35:33.314 [140523097832248] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Apr 26, 2024 10:35:33.314 [140523097832248] INFO - /usr/lib/plexmediaserver/Plex Media Server
Apr 26, 2024 10:35:33.315 [140523100367504] DEBUG - BPQ: [Idle] → [Starting]
Apr 26, 2024 10:35:33.316 [140523100367504] ERROR - FATAL ERROR: Codecs: Initialize: ‘boost::filesystem::temp_directory_path: Not a directory [system:20]: “/datastore/tmp”’
Apr 26, 2024 10:35:33.470 [140523100367504] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader “–directory=/datastore/Application Support/Plex Media Server/Crash Reports/1.32.8.7639-fb6452ebf” --version=1.32.8.7639>
Apr 26, 2024 10:35:33.470 [140523100367504] DEBUG - [JobRunner] Jobs: Starting child process with pid 1550

[EikeW]

i created the tmp folder now i see this on the website:

[EikeW]

bahhhhhh it looks like the server ist empty…that i crap
i have to reinstall everything…how can i safe my files …the server is almost 10 years old and i don’t want to loose every single install i made

[ChuckPa]

Have asked twice for logs.

Cannot help without them.

[ED-HEAD]

Hi. I’m running PMS on a QNAP NAS as well, and yesterday upgraded to 1.40.2.8395. It seemed to install ok, but ever since has been giving the message “Plex Media Server is currently running database migrations”. As of this moment, its been about 13hrs. I did reboot the NAS early this morning, about 5hrs ago to see if perhaps the process was hung and that would clear the message. No sir - still same message. Is there a way to see if this process is actually running and progressing? At what point should I give up and run the DBRepair process? I just don’t want to rush it, but at this point I’m concerned that its not actually running.

Thanks.