Server crashing on version 1.40.1.8227-7000

Plex Media Server
1

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

Good morning,

Wondering if anyone has had similar crashing in version 1.40.1.8227-7000? The Plex Media Server application has hung itself twice in the last two (2) weeks. To resolve, I have had to login to Synology Package Center → ‘Stop’ → ‘Start’ the application. Not sure why the server keeps hanging itself…

Thank you,

Andrew Blackwell
Eden, UT

2

Yes, I have this problem on my Ubuntu 18.04 box running Version 1.40.1.8227. I’ve just started looking into it. I have now have two servers with the same name, one is unavailable and the other had no content. I reorged the database on the available server and that retrieved all of my media info and content.
This still leaves me with an identically named unavailable server in the list which I am try to figure out how to remove.
Whatever the bug is/was that caused this, my Ubuntu box would become unresponsive and would need to be hard reset.

After restarting the box I got the following in terminal:

garage@xantrex:~$ sudo service plexmediaserver status
[sudo] password for garage:
● plexmediaserver.service - Plex Media Server
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Thu 2024-04-04 10:16:00 AEST; 51min ago
Process: 3234 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="$(un
Process: 3232 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, statu
Main PID: 3234 (code=dumped, signal=ABRT)

Apr 04 10:16:00 xantrex systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Apr 04 10:16:00 xantrex systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
Apr 04 10:16:00 xantrex systemd[1]: Stopped Plex Media Server.
Apr 04 10:16:00 xantrex systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Apr 04 10:16:00 xantrex systemd[1]: plexmediaserver.service: Failed with result ‘core-dump’.
Apr 04 10:16:00 xantrex systemd[1]: Failed to start Plex Media Server.

I’m still looking for an answer…

3

can you please make a tar.gz of the Logs directory under Plex Media Server and attach it ?

5

Logs.tar.gz (5.4 MB)

6

@av_andrew

I’m not seeing a crash but there is little I can see with DEBUG logging turned off.

All I can see of significance is this as the server completes shutdown:

Apr 02, 2024 02:20:46.440 [546888741088] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 03:20:46.495 [546882412768] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 04:20:46.507 [546871865568] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 05:20:46.560 [546873975008] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 06:20:46.636 [546869756128] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 07:20:46.688 [546878193888] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 08:20:46.748 [546878193888] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 09:20:46.858 [546867646688] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 10:20:46.828 [546878193888] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 11:20:51.826 [546865537248] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 12:20:51.878 [546865537248] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 13:20:51.959 [546863427808] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 14:20:51.959 [546865537248] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 15:20:52.004 [546861318368] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 15:21:02.146 [546857099488] WARN - [EventSourceClient/pubsub/45.56.91.121:443] PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 16:20:04.578 [546854990048] INFO - [CERT/OCSP] Successfully retrieved response.
Apr 02, 2024 16:20:52.172 [546852880608] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 02, 2024 17:20:52.138 [546852880608] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 03, 2024 10:29:00.911 [547732238368] WARN - Timed out waiting for server to finish.

Then, in the log file after restarting, I see it again.

Apr 03, 2024 10:31:25.453 [548149965024] INFO - Completed: [192.168.1.54:59435] 200 PUT /:/prefs?PublishServerOnPlexOnlineKey=true (6 live) #247 TLS GZIP 4ms 328 bytes (pipelined: 11)
Apr 03, 2024 10:31:29.263 [548113481952] WARN - [Req#247] PublicAddressManager: WAN IP on router does not match public IP from plex.tv
Apr 03, 2024 10:31:50.646 [548098855136] WARN - [Req#2a8] QueryParser: Invalid field 'having' found, ignoring.
Apr 03, 2024 10:31:51.170 [548064927968] WARN - [Req#2d3] QueryParser: Invalid field 'having' found, ignoring.
Apr 03, 2024 10:31:51.197 [548124455136] WARN - [HttpClient/HCl#4c] HTTP error requesting GET  (3, URL using bad/illegal format or missing URL) (URL rejected: Malformed input to a URL function)
Apr 03, 2024 10:31:51.722 [548069339360] WARN - [Req#2db] QueryParser: Invalid field 'having' found, ignoring.

Is Plex crashing or has the network changed?

7

@ChuckPa - DEBUG logging is now enabled. I will upload logs after Plex crashes.

  1. WAN IP on router does not match public IP from plex.tv - I am double-NAT (NAT 1 is the ISP, NAT 2 is my local Wi-Fi router) (currently no Public Static IP from the ISP). Plex is detecting WAN IP 38.46.209.250 - whatismyip.com is detecting WAN IP 38.109.171.11. I suspect something funky upstream. The local ISP does some strange routing.

  2. However, network has not changed. Plex is crashing since latest update. Maybe I can rollback Plex server version or DEBUG logging will help us determine the issue for Plex software patch?

8

Depending on what we find, rolling back might be the best step.
Engineering did find a few issues and has addressed them but keeping you running without failure is best action until those fixes are released.

9

What code do you recommend rolling back to?

10

Because of the schema changes in 1.40.x, the first step is to roll back to the last pre-40 version you had. After that, we can go anywhere

11

Thanks, @ChuckPa! Not a clue what version I had prior to 1.40.x. Looking through file archives, it appears I had the following version installed; PlexMediaServer-1.32.8.7639-fb6452ebf-aarch64_DSM7

Will this version cause destruction? Obviously, a backup prior to anything dangerous is a good idea.

12

@av_andrew

The “Easy Backup” — Make a backup of the “Databases” folder down under “PlexMediaServer”

If you have HyperBackup installed and want to make a full backup you’ll also have that too but the Databases and Preferences.xml are all we would need to fully rebuild the server instance from “cold” in a worst-case scenario.

If you have 1.32.8.7639-7000 SPK there,

  • Uninstall (Uninstall Only ; KEEP option)
  • Manual Install the lower SPK
  • **Give it a bit extra time to resettle the databases (watch the CPU monitor)
13

Downgrade to 1.32.8.7639 seems to have gone smoothly. Thank you for the incredibly helpful guidance. I have gone ahead and turned off debug logging. Please let me know when it is safe to update beyond 1.40.x.

14

Turn it back on. No point in having it off and when you run into an issue you will have the correct logs necessary to diagnose.