Server Version#:1.32.0.6918
Player Version#:4.100.1
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
This issue started today with this version. While direct playing a 4K movie I noticed that my family was losing access to the server/stop streaming due to it not being available. I restarted the modem/routers/switch and restarted the server and it fixed itself temporarily.
The issues persisted since 8 pm tonight 4/11/23 and it happened again at 11:40 pm.
I want to say I fixed the issue, but what I did was REVERT from the newest update to the 1.31.1.6716 version and everything went back to normal. The access to the server was not trumped and I even went to the other rooms to put 2 additional 4k movies and 3 1080p’s running simultaneously. Has anyone had this issue where it just stopped?
The update was done on the 7th of April. Not sure this was happening randomly to others as well. FYI, EMBY was running on the same machine and the access through it was not giving issues. Any help would be greatly appreciated.
Running LINUX Server 21.10 64gbram AMD 3900x
Additional date: PLEX DASH Was not showing usage until I reverted it.
Chuck, good evening, and my apologies for the delay. I was away. The issue persisted when I downgraded as stated on my previous message, and now i am running the updated Version 1.32.1.6999.
This time after the upgrade a few hours later i experienced that the server was unavailable or not found.
I used the sudo service plexmediaserver start and the server was again visible and accessible Locally and remote.
There hasn’t been any updates as far as i know from the hardware and i have been monitoring the issue using the mobile app ( to confirm remote accessibility and that the server is online of course). I took out some ram to verify if they were working as intended and they are. I left installed 40gbRAM and the previously used drives. I will attach the logs below. All your help is greatly appreciated. Plex Media Server Logs_2023-04-12_01-55-21.zip (3.7 MB) Plex Media Server Logs_2023-04-29_20-39-12.zip (3.0 MB)
As requested previously i have attached BOTH logs to the post. I will start the plex dance now and clean bundles and such to see if anything improves on my end.
FIrst up. You’re running Ubuntu 21.10. All of Ubuntu 21 is EndOfLife.
Only the Even numbered years are supported.
As such, you’re two years behind on updates.
First order of business is to get the machine updated. You can go up to 22.04 (which is a LTS… Long Term Service… release and will hold for 5 years. 23.04 will be good only until next year when 24.04 is released but still a big improvement.
Evening, UPGRADE was completed a little after you made the suggestion. The upgrade to 22.04 was completed and the server shows it’s not available via mobile, Roku, and Samsung TV. I however was directly playing a 4K movie while these issues were taking place. Once my family member came to the room to tell me about the issue again, I tried using the phone to open Plex via mobile, and no connection to the server was found, it kept loading, and once it “loaded” it was only Plex content. I did the following in steps:
UPGRADE Ubuntu Server to 22.04.
Restarted the Mesh and made sure the firmware was current
confirmed dedicated ip was attached to the server
confirmed access with a different platform (confirmed that it was connecting).
Turn off IPv6 (Settings - Server - Network - Show advanced). Everything you have is IPv4.
2… I see the server restart. I see, in the previous instances, Verbose logging. Please turn that off unless requested. It’s too verbose, captures too little elapsed time, and extremely difficult to read unless we need to look at each packet exchange.
This shows your server is externally reachable at your published WAN IP.
PubSub: Got notified of reachability for async identifier abe0e2c6-8060-4ca2-a8a4-819360720cb8: 1 for xx.xxx.xxx.xxx
For the next part, When it fails,
At next restart, Grab the Logs ZIP again as soon as you restart it. (This guarantees we capture the last thing it did (which will be in the Plex Media Server.1.log file)
copy, everything was done. As soon as it fails and I restart the server after restart i will download the Logs again and will re-post.
Apologies for the Verbose.
Would your recommend that I turn off IPv6 from the MESH as well. I dont think we have many if any… devices that support IPV6 other than the mobiles and a few cameras around the property.
Wanted to update the status of all.
Have been watching the CONSOLE and nothing irregular.
IPV6 was turned off and after the upgrade, everything has been operational so far, locally and remotely. Usually, I noticed that everything happened as soon as I would sit down and watch a 4K movie, I will do this today hopefully, and report if I lose access during that time. THANKS again for your swift responses and very attentive help.
I am also experiencing the server becoming unavailable. I’m running this on CentOS Stream 8. I would get this error message in /var/log/messages.
May 2 16:29:01 plex kernel: INFO: task PMS HttpServer:4871 blocked for more than 120 seconds.
May 2 16:29:01 plex kernel: Not tainted 4.18.0-489.el8.x86_64 #1
May 2 16:29:01 plex kernel: “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
May 2 16:29:01 plex kernel: task:PMS HttpServer state:D stack: 0 pid: 4871 ppid: 1 flags:0x00000080
May 2 16:29:01 plex kernel: Call Trace:
May 2 16:29:01 plex kernel: __schedule+0x2d1/0x870
May 2 16:29:01 plex kernel: ? newidle_balance+0x274/0x3d0
May 2 16:29:01 plex kernel: schedule+0x55/0xf0
May 2 16:29:01 plex kernel: io_schedule+0x12/0x40
May 2 16:29:01 plex kernel: migration_entry_wait_on_locked+0x1ea/0x290
May 2 16:29:01 plex kernel: ? filemap_fdatawait_keep_errors+0x50/0x50
May 2 16:29:01 plex kernel: do_swap_page+0x5b0/0x710
May 2 16:29:01 plex kernel: ? pmd_devmap_trans_unstable+0x2e/0x40
May 2 16:29:01 plex kernel: ? handle_pte_fault+0x5d/0x880
May 2 16:29:01 plex kernel: __handle_mm_fault+0x365/0x6c0
May 2 16:29:01 plex kernel: handle_mm_fault+0xca/0x2a0
May 2 16:29:01 plex kernel: __do_page_fault+0x1f0/0x450
May 2 16:29:01 plex kernel: do_page_fault+0x37/0x130
May 2 16:29:01 plex kernel: ? page_fault+0x8/0x30
May 2 16:29:01 plex kernel: page_fault+0x1e/0x30
May 2 16:29:01 plex kernel: RIP: 0033:0x7f4ce0eaeeb9
May 2 16:29:01 plex kernel: Code: Unable to access opcode bytes at RIP 0x7f4ce0eaee8f.
May 2 16:29:01 plex kernel: RSP: 002b:00007f4cdc8be640 EFLAGS: 00010246
May 2 16:29:01 plex kernel: RAX: 00007f4cdc5eb148 RBX: 0000000000000000 RCX: 00007f4cdc5eb180
May 2 16:29:01 plex kernel: RDX: 000000000000000c RSI: 00007f4cdc5eb180 RDI: 0000000000000001
May 2 16:29:01 plex kernel: RBP: 00007f4cdc8bec80 R08: 0000000000000000 R09: 0000000000000008
May 2 16:29:01 plex kernel: R10: 0000000000004e1f R11: 0000000000000246 R12: 00007f4cdc8bed70
May 2 16:29:01 plex kernel: R13: 0000000000004e1f R14: 00007f4cdc5eb110 R15: 0000000000004e1f
After this appears, I can no longer access the server. When I SSH to it, trying to stop/restart plexmediaserver fails with connection timeouts. And in order for me to reboot the server, I need to perform a hard reset through the ESXi console.
I don’t know of which version this started happening, but it’s currently happening on 1.32.0.6973.
@Mad-Titan Are you also noticing this in your messages log file?
