March 26, 20251 yr Hi, my docker system crash on unraid even after recreate my docker.img... Thanks for the help syslog.txt
March 26, 20251 yr Community Expert Try this firs to see if stops the PCIe errors: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009 Then reboot, use the server for an hour or so, and post new diags.
March 26, 20251 yr Author 9 minutes ago, JorgeB said: Try this firs to see if stops the PCIe errors: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009 Then reboot, use the server for an hour or so, and post new diags. I'll try it out, thanks
March 26, 20251 yr Author 18 minutes ago, JorgeB said: Try this firs to see if stops the PCIe errors: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009 Then reboot, use the server for an hour or so, and post new diags. I put it here ?
March 26, 20251 yr Community Expert On that screen, but not where the cursor appears to be in that screenshot. Go to the top under menu default and add to the append line
March 26, 20251 yr Community Expert Select menu view, top right, then add it to the green option, after /bzroot, like the mitigations option here.
April 8, 20251 yr Author On 3/26/2025 at 7:51 PM, JorgeB said: Select menu view, top right, then add it to the green option, after /bzroot, like the mitigations option here. It's work few days on yesterday the docker crash again... jamesserver-diagnostics-20250407-2217.zip jamesserver-syslog-20250407-2017.zip
April 8, 20251 yr Community Expert Stating from this time, the log is filled with similar messages: Apr 6 12:20:15 JamesServer kernel: eth0: renamed from vethd4345ec Apr 6 12:20:15 JamesServer kernel: eth0: renamed from veth2fa70b5 Apr 6 12:20:17 JamesServer kernel: vethd4345ec: renamed from eth0 Apr 6 12:20:17 JamesServer kernel: eth0: renamed from veth723a35d Any idea what was done? Possibly, there's a container constantly restarting, and that possibly ended up running the server out of RAM: Apr 7 21:16:47 JamesServer kernel: __vm_enough_memory: pid: 22695, comm: ffprobe, no enough memory for the allocation Apr 7 21:16:47 JamesServer kernel: ffprobe[22695]: segfault at 2000000000 ip 0000000000ca5ce4 sp 00007ffc739f0770 error 4 in ffprobe[401000+bd2000] likely on CPU 7 (core 1, socket 0) Apr 7 21:16:47 JamesServer kernel: Code: 84 00 00 00 00 00 48 63 ff 48 c1 e7 04 48 03 7b 08 e8 80 e3 00 00 48 63 3b 48 c1 e7 04 48 03 7b 08 48 83 c7 08 e8 6c e3 00 00 <8b> 03 8d 78 ff 89 3b 85 c0 75 d1 48 8d 7b 08 e8 58 e3 00 00 48 83 Reboot, then keep monitoring the log, and if those messages show up again for hours, look at the containers uptime.
April 25, 20251 yr Author On 4/8/2025 at 8:02 PM, JorgeB said: Stating from this time, the log is filled with similar messages: Apr 6 12:20:15 JamesServer kernel: eth0: renamed from vethd4345ec Apr 6 12:20:15 JamesServer kernel: eth0: renamed from veth2fa70b5 Apr 6 12:20:17 JamesServer kernel: vethd4345ec: renamed from eth0 Apr 6 12:20:17 JamesServer kernel: eth0: renamed from veth723a35d Any idea what was done? Possibly, there's a container constantly restarting, and that possibly ended up running the server out of RAM: Apr 7 21:16:47 JamesServer kernel: __vm_enough_memory: pid: 22695, comm: ffprobe, no enough memory for the allocation Apr 7 21:16:47 JamesServer kernel: ffprobe[22695]: segfault at 2000000000 ip 0000000000ca5ce4 sp 00007ffc739f0770 error 4 in ffprobe[401000+bd2000] likely on CPU 7 (core 1, socket 0) Apr 7 21:16:47 JamesServer kernel: Code: 84 00 00 00 00 00 48 63 ff 48 c1 e7 04 48 03 7b 08 e8 80 e3 00 00 48 63 3b 48 c1 e7 04 48 03 7b 08 48 83 c7 08 e8 6c e3 00 00 <8b> 03 8d 78 ff 89 3b 85 c0 75 d1 48 8d 7b 08 e8 58 e3 00 00 48 83 Reboot, then keep monitoring the log, and if those messages show up again for hours, look at the containers uptime. After few tests the crash came from my Qbitorrent docker container i try to shutdown the container and after a week the server working well and 24h after re-start the container the docker service crash again... I don't understand why, i limit the ram and the cpu for the container but nothing change always crash... jamesserver-diagnostics-20250425-0941.zip
April 26, 20251 yr Author 14 hours ago, trurl said: Click CONTAINER SIZE on the DOCKER page and post the results
April 28, 20251 yr Community Expert What exactly do you mean by "crash"? Can you access the command line?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.