[SOLVED] No PMS connection since last night's update

Server Version#: QTS 4.3.6.2232
Player Version#: Web

I updated my PMS to version 1.30.2.6563-3d4dc0cce this morning and since then, when I start the Web App, I receive the following error:

Response code=“503” title=“Maintenance” status=“Plex Media Server is currently running startup maintenance tasks.”

I have rebooted my QNAP server, and stopped and started the PMS with no success.

Please assist,

Scott

Please let it run for at least 2 hours…

It’s updating the database

Thanks for your quick response. This started 7 hours ago and the same message continues to be displayed.

Any ideas?

Scott

If so, PMS logs might show a broken database.
Search for the word Malformed

Also tech articles below might come handy
https://support.plex.tv/articles/repair-a-corrupted-database/
https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

Here is my log file
[/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Logs] # more Plex\ Media\ Server.log
Jan 11, 2023 12:04:13.191 [0x7f7b88e1db38] INFO - Plex Media Server v1.30.2.6563-3d4dc0cce - QNAP HS-251 x86_64 - build: linux-x86_64 qnap - GMT -05:00
Jan 11, 2023 12:04:13.192 [0x7f7b88e1db38] INFO - Linux version: QTS 4.3.6.2232, language: en-US
Jan 11, 2023 12:04:13.192 [0x7f7b88e1db38] INFO - Processor: 2-core Intel(R) Celeron(R) CPU J1800 @ 2.41GHz
Jan 11, 2023 12:04:13.192 [0x7f7b88e1db38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Jan 11, 2023 12:04:13.192 [0x7f7b88e1db38] INFO - ./Plex Media Server
Jan 11, 2023 12:04:13.174 [0x7f7b890a8aa0] DEBUG - BPQ: [Idle] → [Starting]
Jan 11, 2023 12:04:13.243 [0x7f7b890a8aa0] DEBUG - FeatureManager: Using cached data for features list
Jan 11, 2023 12:04:13.443 [0x7f7b890a8aa0] DEBUG - [CERT] Subject name is /CN=*.bd7ab418f2ab4c58800a3f8eba2c0030.plex.direct
Jan 11, 2023 12:04:13.443 [0x7f7b890a8aa0] DEBUG - [CERT] Installed certificate with fingerprint ff:52:f6:c4:f4:fb:52:be:d0:f0:83:ef:b4:a6:f1:ee:32:7f:3e:52.
Jan 11, 2023 12:04:13.443 [0x7f7b890a8aa0] DEBUG - [CERT/OCSP] Stapling requests will be made to ‘http://r3.o.lencr.org/’.
Jan 11, 2023 12:04:13.507 [0x7f7b890a8aa0] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Jan 11, 2023 12:04:13.507 [0x7f7b890a8aa0] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Jan 11, 2023 12:04:13.507 [0x7f7b890a8aa0] ERROR - HttpServer: Error binding acceptor: Address in use
Jan 11, 2023 12:04:13.507 [0x7f7b890a8aa0] ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address in use
Jan 11, 2023 12:04:13.507 [0x7f7b890a8aa0] ERROR - HttpServer: Error binding acceptor: Address in use
Jan 11, 2023 12:04:13.698 [0x7f7b890a8aa0] DEBUG - [JobRunner] Job running: /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/CrashUploader “–directory=/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Crash Reports/1.30.2.6563-3d4dc0cce” --version=1.30.2.6563-3d4dc0cce --platform=Linux “–platformVersion=QTS 4.3.6.2232” --serverUuid=a94388103a5ad340dbf1c7642fea5a66fdbf4ee6 --userId=firefighter415@gmail.com --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/minidump/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=QNAP --model=x86_64 --device=HS-251
Jan 11, 2023 12:04:13.698 [0x7f7b890a8aa0] DEBUG - [JobRunner] Jobs: Starting child process with pid 29113

  • I tried the database repair using Plex SQLite, came back ok
  • tried restoring database backup, still cannot connect,

Any other ideas?

Thanks,

Scott

We need the whole zip of log files, not just a snip

And found it :smiley:

Restart your QNAP

I had rebooted the QNAP server this morning and once again, so far no change. I guess I will leave it for the rest of the day and overnight to see if it comes back.

Not looking good :frowning:

So, I got it working. For some reason, my 127.0.0.1 entry in my routing table was gone. Put it in and voila… working great.

Thanks, everyone.

1 Like

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