Ascii227

Hi, I use Unraid as a backup server. Every night I run rsync to backup files from other servers to unraid. This has been working fine for years. Recently, rsync has started freezing and crashing the array every night. There is high load and IOWait in top, but low cpu usage. I cannot see any errors on disks. Rsync processes go into D state and never wake up. The array cannot be stopped, it hangs on 'Sync Filesystems...' forever. Soft reboot and powerdown do nothing. A hard reset is the only way I have been able to get out of this. I can see from lsof and ps that the rsync process is stuck waiting in some IO, but I cant figure out exactly what, or how to resolve it. Could somebody cleverer than I please take a look at my diagnostics and suggest what I could try to track this error down and make stop rsync from stalling? Thankyou very much. vault-diagnostics-20240426-0935.zip

Hi, My server has been up and running fine for years. Today it is down. Please help! Clicking around the UI is slow, and 50% of the time gives me this error message in the browser: Warning: shell_exec(): Unable to execute 'logger error: '/webGui/include/DeviceList.php': missing csrf_token' in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18 I went to the syslog and it has been throwing this error every 5 mins for the last 2 weeks: Sep 14 12:45:06 Server_name ntfs-3g[26405]: Failed to read vcn 0x0: Input/output error Sep 14 12:45:06 Server_name kernel: Buffer I/O error on dev sdt1, logical block 36, async page read Sep 14 12:50:06 Server_name ntfs-3g[26405]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Sep 14 12:50:06 Server_name ntfs-3g[26405]: Failed to read vcn 0x0: Input/output error Then last night it started throwing this error every 5 mins: Sep 18 01:50:29 Server_name emhttpd: Pro key detected, GUID: ***REDACTED*** FILE: /boot/config/Pro.key Sep 18 01:50:54 Server_name emhttpd: Unregistered - flash device error (ENOFLASH7) Sep 18 01:56:22 Server_name emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) and now all I am getting in the logs is this over and over: Sep 18 14:24:50 Server_name emhttpd: read SMART /dev/sdf Sep 18 14:24:50 Server_name emhttpd: error: device_read_smart, 7977: Cannot allocate memory (12): device_spinup: stream did not open: sdf and Sep 18 14:17:57 Server_name php-fpm[5669]: [ERROR] fork() failed: Resource temporarily unavailable (11) I have tried exporting diagnostics but the server just hangs. My basic knowledge is suggesting that my flash drive is toast, but I dont want to go down that route without some confirmation from somebody who knows a bit more Any help or guidance on how to troubleshoot or fix this issue is much appreciated. Thanks in advance!

Im sorry that you seem to have taken it this way. Due to the way both unraid and dockers have developed over time, the standard way now advised in all tutorials and youtube videos to get these systems set up is to use automated setup scripts and plugins. Unfortunately in depth documentation or even signposts to the correct locations of the docs have not kept up with this pattern and remain on developer centric sites such as github. As Squid himself has said, he foresaw this as a potential issue and specifically developed a feature in his app store to combat it. If you look at my post history you will see I have spent quite some time researching how to use unraid properly, and never just whined and asked for people to solve the problems for me. All I suggested was that on the first post of this thread you mention that the readme and all potential troubleshooting info can be found on the github page. No spoonfeeding necessary, just a simple signpost to where the docs are so people can find them. Considering this thread is the official support for this docker and system I think thats quite a constructive suggestion, and not really one that requires a condescending reply about how little I am doing to help myself.

Thanks for the calm and considered responses from you guys. I appreciate that documentation is hard to keep updated in many different locations, I was just pointing out that the signposting to it in this instance is a little expectant of the user to assume to go to the docker hub or github repo. Squids feature in CA looks awesome, this would have nailed my issue with tag confusion upfront before it even appeared

If you want to go down this path of pointing out where I should have looked then thats fine, but I did check the first post of this thread several times and had no reason to go to the github link as I had no interest in the code and already had a path of downloading the docker directly from the community apps. If you want to avoid other people making these same mistakes may I suggest you make it much more obvious everywhere that the readme and possible troubleshooting options are all on the github site and to check that first before posting. Better still copy and pasting the entire readme into the first post would be even better as the thread is listed as the place to get support, not the github repo.

Fair enough. When I created the docker from the template in community apps the tag field was prefilled with latest, so I assumed that was default and I was doing the right thing by leaving it like that. I have just been through the linuxserver.io docker image info in the unraid community apps plugin and there is no mention of tags whatsoever. The only reference I can find is in the template overview where it states 'VERSION Set to either latest,public or a specific version e.g. "1.2.7.2987-1bef33a"' Nothing to implicate that latest is a beta build and public should be used for stability. For users like me who are just installing the Docker straight through community apps there is little in the way of explanations as to what the differnt tags mean. In fact in all my weeks posting in the forums this is first I have ever heard of the public tag. I have now changed the tag in my docker to public and all is well. Apologies for polluting this issue with misunderstanding the tag system.

No offence, but I really dont think this is much help. Its not like I am manually trying to upgrade to some bleeding edge beta version. As soon as I fire up the standard plex docker the logs show 'Attempting to upgrade to 1.15' and then all the trouble begins. Only by reverting to an old version of the docker am I able to get anything working. Me too, which is why I am using all the default settings on the docker and just letting it do its thing. It is attempting the upgrading to 1.15 on its own and causing me to not be able to watch anything. Just for info, here is the plex docker log from the first time I install and run it directly from the app store. As you can see, I am doing nothing. The docker is doing everything itself the first time it starts up from a fresh install. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.15.0.659-9311f93fd 2019-02-20 07:46:24 URL:https://downloads.plex.tv/plex-media-server-new/1.15.0.659-9311f93fd/debian/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb [81547030/81547030] -> "/tmp/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb" [1] 2019-02-20 07:46:24 URL:https://downloads.plex.tv/plex-media-server-new/1.15.0.659-9311f93fd/debian/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb [81547030/81547030] -> "/tmp/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb" [1] (Reading database ... 10486 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.15.0.659-9311f93fd_amd64.deb ... (Reading database ... 10486 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.15.0.659-9311f93fd_amd64.deb ... Unpacking plexmediaserver (1.15.0.659-9311f93fd) over (1.14.1.5488-cc260c476) ... Setting up plexmediaserver (1.15.0.659-9311f93fd) ... Setting up plexmediaserver (1.15.0.659-9311f93fd) ... Installing new version of config file /etc/init/plexmediaserver.conf ... Processing triggers for libc-bin (2.27-3ubuntu1) ... [cont-init.d] 60-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done.

I deleted my codec folder from the location you specified then watched as plex redownloaded the required codecs for every file I pressed play on, but still failed to play them all with the same error as before. I took gacpacs advice as it seems the last thing I can possibly do. So I deleted the docker and image, and reinstalled from the community apps plugin. Remapped and scanned all my library files. After all that I get exactly the same results, nothing plays with a transcoder crash error. Changing the docker tag back to 168 (PMS 1.14.1) and restarting the docker makes everything play fine again. Im hoping this at least rules out anything to do with my unraid setup. I did manage to find an mp4 file in my library which will direct play just fine in latest/1.15, but as soon as I try to convert or transcode it I get the same error. I guess I will just sit on tag 168 forever, its not causing me any issues to stay there so as gacpac inferred - if its not broke dont fix it! EDIT: I noticed from poking in the codec folder that the two versions of plex (1.14.1 and 1.15.0) Seem to be keeping their codecs in differently named folders. Could be nothing, but could mean something to someone: 1.15.0 stores them in codecs/a22632d-2034-linux-x86_64 1.14.1 stores them in codecs/531e313-1328-linux-ubuntu-x86_64

Thanks very much for such a comprehensive list of steps! A couple of differences in my usage though. I never use subtitles and only ever use the web client, never any apps or players. Also I am unable to p[lay anything both locally and remotely. The only thing I can see to try is to delete my codecs folder and see if plex redownloads the correct ones. I will give this a go and report back. Thanks again.

Thanks, thats good to know. Saves me trying it round both ways all the time. I think my problem may go deeper than this. Unchecking the 'Use hardware acceleration' box in the Plex server settings, and I still get exactly the same error. Other peopel are seeing sporadic errors on certain files or no issues at all, whilst I cannot play anything from my library regardless of the filetype or transcoding method. I just cant see why this would be such a stark difference between the two docker versions for me. PMS 1.14.1 plays everything no problem, whereas version 1.15 plays nothing at all. As nobody else seems to be sharing my symptoms, could anybody point to a place in the logs where I might be able to start diagnosing this? Im happy to do the digging and troubleshoting myself, but plex has such a plethora of log files its difficult to know where to begin or what to look for! Thanks very much.

No but this is all good troubleshooting info, thankyou. Are you using the '--device=/dev/dri:/dev/dri' switch in the extra parameters field for the docker?

I was hoping this was the issue but no luck : Unfortunately Plex specifically state that they dont support hw transcoding through a docker image, and so they wont touch this with a barge pole. Is anybody seeing this issue who isnt using a docker image? (Not much chance in this thread I know but worth asking!)

Thanks for confirming. Now that I look in the logs I see the upgrade error for tag 168. I will have a sift through the plex forums to see if anybody else is posting any similar issues with 1.15. Please do post back if you find any more info.

Thankyou for the advice, I have done a forced update several times now. I always have advanced mode on, but dont have any orphaned docker images. LATEST tag on the plex docker is giving me transcoder crash errors trying to play anything, just switching it back to 168 and restarting the docker makes everything play fine. I am a plexpass subscriber, will this have anything to do with it? Mind you I wouldnt have hardware transcoding available to me if I wasnt! Is there anything else I can try? Thanks again EDIT: Adding my plex docker logs after forcing an update on LATEST tag, just incase it helps. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.15.0.659-9311f93fd 2019-02-17 08:19:09 URL:https://downloads.plex.tv/plex-media-server-new/1.15.0.659-9311f93fd/debian/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb [81547030/81547030] -> "/tmp/plexmediaserver_1.15.0.659-9311f93fd_amd64.deb" [1] (Reading database ... 10486 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.15.0.659-9311f93fd_amd64.deb ... (Reading database ... 10486 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.15.0.659-9311f93fd_amd64.deb ... Unpacking plexmediaserver (1.15.0.659-9311f93fd) over (1.14.1.5488-cc260c476) ... Setting up plexmediaserver (1.15.0.659-9311f93fd) ... Installing new version of config file /etc/init/plexmediaserver.conf ... Processing triggers for libc-bin (2.27-3ubuntu1) ... [cont-init.d] 60-plex-update: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server.

Apologies for getting this wrong, but still having the same issue after forcing the latest update. i am able to browse around my library, but still trying to play anything results in the transcoder process crash error. Again, if i revert to tag 168 everything works fine again. is there any info i can retrieve from my system to help pinppint why this might be? Thanks very much.

Thanks for the suggestion, forcing an update has fixed the issue for me.

Unfortunately for me this problem is reproduceable every time. If I change the docker tag to LATEST and restart the docker I cant play anything. Any plex player can browse the library fine but when attempting to play anything the loading spinner will just sit there spinning. If I leave it long enough I will get the message "Playback Error - Conversion Failed. The Transcoder Process Crashed". If I change the docker tag back to 168 and restart it then everything plays fine. I am using hardware transcoding via the /dev/dri module. Is anybody else seeing these issues with the latest docker version and hardware decoding?

I am seeing exactly the same issue, and reverting to docker version 168 solved it for me. With the latest docker update I was getting nothing playing, and if I left it long enough trying to play the plex web player would show the error 'Transcoder process has crashed' or something similar. When I reverted back to version 168 everything played fine again. I specifically came into this thread to try to find other users with the same issue. Have you found any more info on what your problem is? I have also done a lot of file moving about recently. Did you find restoring your appdata backup helped? Thanks

Hi unraiders, not having fun today. Syslog is reporting a cpu stall on docker, which in turn is causing some sort of IO disk errors. In top, Docker is reporting extremely high cpu usage, and I cant kill it. I think its due to the mounted share it is trying to access being unavailable due to the cpu error. Unraid web gui is completely unresponsive Netdata is working and reporting extremely high load and iowait times "ls /mnt" just hangs the terminal "umount -f /var/lib/docker" just returns "Target is busy" "reboot" and "powerdown -r" just do nothing I have included what my syslog is looping on below. Any advice on what to try is much appreciated. Thankyou! Dec 22 20:22:50 AsQ-NAS kernel: INFO: rcu_bh self-detected stall on CPU Dec 22 20:22:50 AsQ-NAS kernel: INFO: rcu_bh detected stalls on CPUs/tasks: Dec 22 20:22:50 AsQ-NAS kernel: 6-....: (1 GPs behind) idle=912/1/4611686018427387906 softirq=3811864/3811866 fqs=15825140 Dec 22 20:22:50 AsQ-NAS kernel: (t=63601766 jiffies g=-185 c=-186 q=130) Dec 22 20:22:50 AsQ-NAS kernel: 6-....: (1 GPs behind) idle=912/1/4611686018427387906 softirq=3811864/3811866 fqs=15825140 Dec 22 20:22:50 AsQ-NAS kernel: (detected by 1, t=63601769 jiffies, g=-185, c=-186, q=130) Dec 22 20:22:50 AsQ-NAS kernel: NMI backtrace for cpu 6 Dec 22 20:22:50 AsQ-NAS kernel: CPU: 6 PID: 22098 Comm: docker Tainted: G B D 4.18.17-unRAID #1 Dec 22 20:22:50 AsQ-NAS kernel: Hardware name: System manufacturer System Product Name/ROG STRIX Z370-G GAMING (WI-FI AC), BIOS 1601 10/29/2018 Dec 22 20:22:50 AsQ-NAS kernel: Call Trace: Dec 22 20:22:50 AsQ-NAS kernel: <IRQ> Dec 22 20:22:50 AsQ-NAS kernel: dump_stack+0x5d/0x79 Dec 22 20:22:50 AsQ-NAS kernel: nmi_cpu_backtrace+0x71/0x83 Dec 22 20:22:50 AsQ-NAS kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Dec 22 20:22:50 AsQ-NAS kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7 Dec 22 20:22:50 AsQ-NAS kernel: rcu_dump_cpu_stacks+0x91/0xbb Dec 22 20:22:50 AsQ-NAS kernel: rcu_check_callbacks+0x23f/0x5ca Dec 22 20:22:50 AsQ-NAS kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Dec 22 20:22:50 AsQ-NAS kernel: update_process_times+0x23/0x45 Dec 22 20:22:50 AsQ-NAS kernel: tick_sched_timer+0x36/0x64 Dec 22 20:22:50 AsQ-NAS kernel: __hrtimer_run_queues+0xb1/0x105 Dec 22 20:22:50 AsQ-NAS kernel: hrtimer_interrupt+0xf4/0x20d Dec 22 20:22:50 AsQ-NAS kernel: smp_apic_timer_interrupt+0x79/0x89 Dec 22 20:22:50 AsQ-NAS kernel: apic_timer_interrupt+0xf/0x20 Dec 22 20:22:50 AsQ-NAS kernel: </IRQ> Dec 22 20:22:50 AsQ-NAS kernel: RIP: 0010:filemap_map_pages+0x98/0x2b8 Dec 22 20:22:50 AsQ-NAS kernel: Code: 89 f8 83 e0 03 74 23 48 ff c8 0f 85 77 01 00 00 48 c7 44 24 20 00 00 00 00 48 8b 44 24 10 31 db 48 89 44 24 18 e9 89 01 00 00 <49> 8b 47 08 4c 89 ff a8 01 74 04 48 8d 78 ff 8b 47 34 85 c0 74 b3 Dec 22 20:22:50 AsQ-NAS kernel: RSP: 0000:ffffc9000da2bd90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Dec 22 20:22:50 AsQ-NAS kernel: RAX: 0000000000000000 RBX: ffff8808259c75f8 RCX: 0000000000000000 Dec 22 20:22:50 AsQ-NAS kernel: RDX: 0000000000000001 RSI: 000000000096a000 RDI: ffffea0020621280 Dec 22 20:22:50 AsQ-NAS kernel: RBP: ffffc9000da2be10 R08: 000000000000056a R09: 0000000818849000 Dec 22 20:22:50 AsQ-NAS kernel: R10: 0000000000000580 R11: 0000000000000000 R12: ffff88081d69eaa0 Dec 22 20:22:50 AsQ-NAS kernel: R13: ffff880718c86a00 R14: 000000000000056a R15: ffffea0020621280 Dec 22 20:22:50 AsQ-NAS kernel: __handle_mm_fault+0xda0/0x10aa Dec 22 20:22:50 AsQ-NAS kernel: handle_mm_fault+0x159/0x1a8 Dec 22 20:22:50 AsQ-NAS kernel: __do_page_fault+0x271/0x40b Dec 22 20:22:50 AsQ-NAS kernel: ? page_fault+0x8/0x30 Dec 22 20:22:50 AsQ-NAS kernel: page_fault+0x1e/0x30 Dec 22 20:22:50 AsQ-NAS kernel: RIP: 0033:0x966ef0 Dec 22 20:22:50 AsQ-NAS kernel: Code: 4c 24 08 48 89 44 24 10 e8 dd 89 b0 ff e9 73 fe ff ff e8 53 cd ae ff e9 fe fd ff ff cc cc cc cc cc cc cc cc cc cc cc cc cc cc <64> 48 8b 0c 25 f8 ff ff ff 48 3b 61 10 0f 86 b3 00 00 00 48 83 ec Dec 22 20:22:50 AsQ-NAS kernel: RSP: 002b:000000c420205f08 EFLAGS: 00010202 Dec 22 20:22:50 AsQ-NAS kernel: RAX: 0000000000000002 RBX: 0000000000000040 RCX: 000000c420000180 Dec 22 20:22:50 AsQ-NAS kernel: RDX: 0000000001962020 RSI: 000000000158ad00 RDI: 000000c4202512a8 Dec 22 20:22:50 AsQ-NAS kernel: RBP: 000000c420205f30 R08: 000000c420251270 R09: 0000000000000047 Dec 22 20:22:50 AsQ-NAS kernel: R10: 0000000000000010 R11: 000000c420251270 R12: 0000000000000068 Dec 22 20:22:50 AsQ-NAS kernel: R13: 0000000000000018 R14: 0000000000000057 R15: 0000000000000100 Dec 22 20:22:50 AsQ-NAS kernel: Sending NMI from CPU 1 to CPUs 6: Dec 22 20:22:50 AsQ-NAS kernel: NMI backtrace for cpu 6 Dec 22 20:22:50 AsQ-NAS kernel: CPU: 6 PID: 22098 Comm: docker Tainted: G B D 4.18.17-unRAID #1 Dec 22 20:22:50 AsQ-NAS kernel: Hardware name: System manufacturer System Product Name/ROG STRIX Z370-G GAMING (WI-FI AC), BIOS 1601 10/29/2018 Dec 22 20:22:50 AsQ-NAS kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x103/0x16d Dec 22 20:22:50 AsQ-NAS kernel: Code: 36 c1 e9 12 83 e0 03 ff c9 48 c1 e0 04 48 63 c9 48 05 c0 17 02 00 48 03 04 cd 00 17 da 81 48 89 10 8b 42 08 85 c0 75 04 f3 90 <eb> f5 48 8b 0a 48 85 c9 74 c9 0f 0d 09 8b 07 66 85 c0 74 04 f3 90 Dec 22 20:22:50 AsQ-NAS kernel: RSP: 0000:ffff880826383e90 EFLAGS: 00000046 Dec 22 20:22:50 AsQ-NAS kernel: RAX: 0000000000000000 RBX: 0000000000000046 RCX: 0000000000000008 Dec 22 20:22:50 AsQ-NAS kernel: RDX: ffff8808263a17c0 RSI: 00000000001c0000 RDI: ffffffff81e38ac0 Dec 22 20:22:50 AsQ-NAS kernel: RBP: ffff8808263a1840 R08: 000000000000000f R09: ffff88081fb53b00 Dec 22 20:22:50 AsQ-NAS kernel: R10: 0000000000000001 R11: 000000000000002b R12: 0000000000000046 Dec 22 20:22:50 AsQ-NAS kernel: R13: ffff8808263a1840 R14: 0000000000000000 R15: ffffffff81e38ac0 Dec 22 20:22:50 AsQ-NAS kernel: FS: 00000000022e9a90(0000) GS:ffff880826380000(0000) knlGS:0000000000000000 Dec 22 20:22:50 AsQ-NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 22 20:22:50 AsQ-NAS kernel: CR2: 0000000000966ef0 CR3: 0000000718ad0003 CR4: 00000000003606e0 Dec 22 20:22:50 AsQ-NAS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 22 20:22:50 AsQ-NAS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 22 20:22:50 AsQ-NAS kernel: Call Trace: Dec 22 20:22:50 AsQ-NAS kernel: <IRQ> Dec 22 20:22:50 AsQ-NAS kernel: _raw_spin_lock_irqsave+0x28/0x2f Dec 22 20:22:50 AsQ-NAS kernel: rcu_check_callbacks+0x247/0x5ca Dec 22 20:22:50 AsQ-NAS kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Dec 22 20:22:50 AsQ-NAS kernel: update_process_times+0x23/0x45 Dec 22 20:22:50 AsQ-NAS kernel: tick_sched_timer+0x36/0x64 Dec 22 20:22:50 AsQ-NAS kernel: __hrtimer_run_queues+0xb1/0x105 Dec 22 20:22:50 AsQ-NAS kernel: hrtimer_interrupt+0xf4/0x20d Dec 22 20:22:50 AsQ-NAS kernel: smp_apic_timer_interrupt+0x79/0x89 Dec 22 20:22:50 AsQ-NAS kernel: apic_timer_interrupt+0xf/0x20 Dec 22 20:22:50 AsQ-NAS kernel: </IRQ> Dec 22 20:22:50 AsQ-NAS kernel: RIP: 0010:filemap_map_pages+0x98/0x2b8 Dec 22 20:22:50 AsQ-NAS kernel: Code: 89 f8 83 e0 03 74 23 48 ff c8 0f 85 77 01 00 00 48 c7 44 24 20 00 00 00 00 48 8b 44 24 10 31 db 48 89 44 24 18 e9 89 01 00 00 <49> 8b 47 08 4c 89 ff a8 01 74 04 48 8d 78 ff 8b 47 34 85 c0 74 b3 Dec 22 20:22:50 AsQ-NAS kernel: RSP: 0000:ffffc9000da2bd90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Dec 22 20:22:50 AsQ-NAS kernel: RAX: 0000000000000000 RBX: ffff8808259c75f8 RCX: 0000000000000000 Dec 22 20:22:50 AsQ-NAS kernel: RDX: 0000000000000001 RSI: 000000000096a000 RDI: ffffea0020621280 Dec 22 20:22:50 AsQ-NAS kernel: RBP: ffffc9000da2be10 R08: 000000000000056a R09: 0000000818849000 Dec 22 20:22:50 AsQ-NAS kernel: R10: 0000000000000580 R11: 0000000000000000 R12: ffff88081d69eaa0 Dec 22 20:22:50 AsQ-NAS kernel: R13: ffff880718c86a00 R14: 000000000000056a R15: ffffea0020621280 Dec 22 20:22:50 AsQ-NAS kernel: __handle_mm_fault+0xda0/0x10aa Dec 22 20:22:50 AsQ-NAS kernel: handle_mm_fault+0x159/0x1a8 Dec 22 20:22:50 AsQ-NAS kernel: __do_page_fault+0x271/0x40b Dec 22 20:22:50 AsQ-NAS kernel: ? page_fault+0x8/0x30 Dec 22 20:22:50 AsQ-NAS kernel: page_fault+0x1e/0x30 Dec 22 20:22:50 AsQ-NAS kernel: RIP: 0033:0x966ef0 Dec 22 20:22:50 AsQ-NAS kernel: Code: 4c 24 08 48 89 44 24 10 e8 dd 89 b0 ff e9 73 fe ff ff e8 53 cd ae ff e9 fe fd ff ff cc cc cc cc cc cc cc cc cc cc cc cc cc cc <64> 48 8b 0c 25 f8 ff ff ff 48 3b 61 10 0f 86 b3 00 00 00 48 83 ec Dec 22 20:22:50 AsQ-NAS kernel: RSP: 002b:000000c420205f08 EFLAGS: 00010202 Dec 22 20:22:50 AsQ-NAS kernel: RAX: 0000000000000002 RBX: 0000000000000040 RCX: 000000c420000180 Dec 22 20:22:50 AsQ-NAS kernel: RDX: 0000000001962020 RSI: 000000000158ad00 RDI: 000000c4202512a8 Dec 22 20:22:50 AsQ-NAS kernel: RBP: 000000c420205f30 R08: 000000c420251270 R09: 0000000000000047 Dec 22 20:22:50 AsQ-NAS kernel: R10: 0000000000000010 R11: 000000c420251270 R12: 0000000000000068 Dec 22 20:22:50 AsQ-NAS kernel: R13: 0000000000000018 R14: 0000000000000057 R15: 0000000000000100

Thanks very much for the crash course in docker management! I specified 158 in the tag field, restarted the docker, and now plex is working fine again with the previous version and minimal cpu usage. I will wait til another version is released and then change the tag back to latest and see if my issue is resolved. Thankyou for the knowledge.

Thankyou very much for your time and advice, but is there an easy way to do that? I cant see any option from within the unraid gui. Thanks again.

Hi unraiders, new issue here today. Plex has been running fine for many months and through many docker updates. However, just updated the docker image on my unraid server and now a single core of my i7 8700 is constantly being used 100% by the plex docker. No other cpu cores are affected at all. From time to time the specific core which is at 100% might switch but it is always only 1 core. Ther is nothing in the plex logs to show it is doing anything, and I have restarted the docker image a few times but every time I start it the single core jumps straight back up to 100% again. Any advice much appreciated, thankyou. Edit: I am also seeing that in Netdata my 'IPv4 UDP Sockets Memory' metric is slowly creeping up to levels where it is giving me alarms and registered UDP errors. When I stop the plex docker this jumps back down to zero, and when I start it back up the metric starts to creep up again. Seems related somehow.