Updated to latest server version of Plex and I suddenly cannot connect to Plex

Plex Media Server
1

Server Version#:1.40.3.8555-fef15d30c
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I just updated to version
1.40.3.8555-fef15d30c on my Ubuntu 24.04.4 server and now I cannot connect to the server from any device on my home network.

When I do a

service plexmediaserver status

command I get

× plexmediaserver.service - Plex Media Server
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-06-15 16:55:38 UTC; 15min ago
Process: 1526 ExecStartPre=/bin/sh -c /usr/bin/test -d “${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}” || /bin/mkdir -p “${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}” (code=exited, status=0/SUCCESS)
Process: 1528 ExecStart=/bin/sh -c export PLEX_MEDIA_SERVER_INFO_VENDOR=“$(grep ^NAME= /etc/os-release | awk -F= “{print $2}” | tr -d " )”; export PLEX_MEDIA_SERVER_INFO_MODEL=“$(uname -m)”; export PLEX_MEDIA_SERVER_INFO_PLATFORM_VERSION=“$(grep ^VERSION= /etc/os-release | awk -F= “{print $2}” | tr -d " )”; exec “/usr/lib/plexmediaserver/Plex Media Server” (code=exited, status=255/EXCEPTION)
Main PID: 1528 (code=exited, status=255/EXCEPTION)
CPU: 305ms

Jun 15 16:55:38 mediamagnate systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
Jun 15 16:55:38 mediamagnate systemd[1]: Stopped Plex Media Server.
Jun 15 16:55:38 mediamagnate systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Jun 15 16:55:38 mediamagnate systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Jun 15 16:55:38 mediamagnate systemd[1]: Failed to start Plex Media Server.

if I issue commands to stop and start PlexMediaServer and then do a status check I get

× plexmediaserver.service - Plex Media Server
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-06-15 17:12:50 UTC; 14s ago
Process: 1699 ExecStartPre=/bin/sh -c /usr/bin/test -d “${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}” || /bin/mkdir -p “${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}” (code=exited, status=0/SUCCESS)
Process: 1701 ExecStart=/bin/sh -c export PLEX_MEDIA_SERVER_INFO_VENDOR=“$(grep ^NAME= /etc/os-release | awk -F= “{print $2}” | tr -d " )”; export PLEX_MEDIA_SERVER_INFO_MODEL=“$(uname -m)”; export PLEX_MEDIA_SERVER_INFO_PLATFORM_VERSION=“$(grep ^VERSION= /etc/os-release | awk -F= “{print $2}” | tr -d " )”; exec “/usr/lib/plexmediaserver/Plex Media Server” (code=exited, status=255/EXCEPTION)
Main PID: 1701 (code=exited, status=255/EXCEPTION)
CPU: 302ms

Jun 15 17:12:50 mediamagnate systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
Jun 15 17:12:50 mediamagnate systemd[1]: Stopped Plex Media Server.
Jun 15 17:12:50 mediamagnate systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Jun 15 17:12:50 mediamagnate systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Jun 15 17:12:50 mediamagnate systemd[1]: Failed to start Plex Media Server.

If I do a

$sudo service plexmediaserver restart

command then run

$sudo service plexmediaserver status

I get

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.

I would be happy to revert to the previous version. It was running fine. Except I do not know how to do this.

2

Server logs might give you a hint what’s going on/wrong. Rolling back won’t help if e.g. your server‘s database is corrupted.

1 Like
3

do: tail -F -n 100 /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Logs/Plex\ Media\ Server.log

Then restart Plex; you’ll see why it’s crashing if you watch the logs. Systemd logs do a piss poor job of letting you know what’s wrong, read Plex logs instead.

4

Yes, well, wouldn’t that be swell. But I cannot connect to the PMS via a Web browser so I am stuck looking at log files via command line / PUTTY - here is a list 'Plex Crash Uploader.1.log' 'Plex Media Scanner.log''Plex C - Pastebin.com

Any of these in particular I should look at? Thanks

1 Like
5

Thank you. This command is running. I’ll get back to you.

6

The link above points to a support article on how to obtain your server logs… via the web app (requires the server to be running) or in your file system (works even if your server is down).

7

OK so here is the read out after running the tail command

Jun 15, 2024 18:07:16.529 [140627810941752] INFO - Plex Media Server v1.40.3.855 - Pastebin.com

Only problem I see is database corruption sqlite issue. “disk image is malformed”

Jun 15, 2024 18:07:16.529 [140627810941752] INFO - Plex Media Server v1.40.3.855 - Pastebin.com)

8

Yeah looks like db migrations was interrupted. You’re the second person I read today with exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed

Try Chuck’s DB Repair but from what I read DB Repair can’t fix that. You’ll have to restore from backup and make sure you read on what you need to do to restore a backup, important to pay attention to remove those -wal files.

Did you update plex recently? I’m guessing from plex 1.32 to 1.4? That was a couple of months ago but it borked a lot of databases because the DB migration took too long to complete and people kept interrupting it.

9

I’ve been reading but you know - this stuff is clear as mud.

I updated today - after getting the notice that a new version of PMS is available.

It’s funny - I was offered the chance to skip this upgrade. Something inside told me I should do that.

But, I usually upgrade to the latest version of things - except when running Fedora because I have had so many issues when upgrading early to a new version. Now I wait until the last two weeks before EOL.

Anyway, thanks for your help. Perhaps I should just delete the database and start over.

10

You have backups that are taken every 3 days. I would restore from backup.

Here follow this guide: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

Pay attention to this: Move the following files out of the directory and store them somewhere for backup, just in case. (The “-shm” and “-wal” are temporary files and may not be there.)

Make sure when you put your backup DB to replace the old broken DB that those -shm and -wal counterparts are not there.

11

Try the PlexDB Repair Utility and see if it can repair the database. Use the AUTO option.

As @ChristianKent mentions, the utility may not be able to repair things.

If that is the case, try the REPLACE option. It is basically the same as using the “Restore a database…” support article. However, it will check the backup versions before restoring one of them.

12

Just to follow up, I reinstalled the Plex server software on my Ubuntu 24.04.04 server and everything is back to working.

Thanks to everyone who helped.

13

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