April 10, 20251 yr Not sure what is going on, but I wake up to stack trace dump and nothing in syslog. Frustrated...any ideas or help? Syslog doesn't show much but I grabbed a picture of the console before reboot. And of course diagnostic attached for good measure but not sure how helpful it will be. Would mirroring syslog to flash help capture more information for the next (😒) crash? EDIT: added small section of syslog showing time leading up to crash. Only thing I see is some docker seg faults 6 hours earlier, but not sure if that would be related. Apr 9 19:11:14 Tower rc.nfsd: NFS server daemon... Started. Apr 9 19:14:51 Tower root: Fix Common Problems Version 2025.03.12 Apr 9 19:14:52 Tower root: Fix Common Problems: Warning: Docker Application ClamAV has an update available for it Apr 9 19:14:52 Tower root: Fix Common Problems: Warning: Docker Application n8n has an update available for it Apr 9 19:14:56 Tower root: Fix Common Problems: Warning: Share downloads set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:14:56 Tower root: Fix Common Problems: Warning: Share Temp set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:14:56 Tower kernel: block nvme0n1: the capability attribute has been deprecated. Apr 9 19:14:57 Tower kernel: r8169 0000:04:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Apr 9 19:14:57 Tower kernel: mpt3sas 0000:05:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Apr 9 19:20:00 Tower root: Fix Common Problems Version 2025.03.12 Apr 9 19:20:04 Tower root: Fix Common Problems: Warning: Share downloads set to use pool cachessd, but files / folders exist on the cache pool Apr 9 19:20:04 Tower root: Fix Common Problems: Warning: Share Temp set to use pool cachessd, but files / folders exist on the cache pool Apr 9 20:19:08 Tower kernel: Radarr[19134]: segfault at 12e7 ip 0000154fe97c5f7e sp 0000154fe83f6d90 error 6 in libsqlite3.so.3.49.1[154fe9697000+130000] likely on CPU 7 (core 12, socket 0) Apr 9 20:19:08 Tower kernel: Code: 71 2c 03 71 28 48 f7 d8 48 63 f6 48 c1 e0 0a 48 99 48 f7 fe ba 00 ca 9a 3b 48 39 d0 48 0f 4e d0 48 89 d6 48 8b 79 48 41 ff d0 <41> 80 00 24 11 00 00 08 41 83 00 24 14 01 00 22 48 83 00 10 41 5c Apr 9 20:28:04 Tower kernel: traps: Plex Transcoder[399491] general protection fault ip:14953c1edd26 sp:149539a38770 error:0 in libh264_decoder.so[14953c13d000+13e000] Apr 9 20:55:47 Tower kernel: python3[18875]: segfault at 140043703100 ip 000014bc45783543 sp 00007ffd37362080 error 4 in libpython3.13.so.1.0[14bc4563a000+2c0000] likely on CPU 2 (core 4, socket 0) Apr 9 20:55:47 Tower kernel: Code: 89 cf ff e0 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 49 89 f5 41 54 49 89 fc 53 48 83 ec 18 4c 8b 3f eb 2f 0f 1f 40 00 4d 89 fe <49> 8b 17 49 8b 46 10 49 8b 5e 08 49 89 d7 85 c0 0f 88 55 1a ed ff Apr 9 22:15:06 Tower emhttpd: spinning down /dev/sdd Apr 9 22:15:07 Tower emhttpd: spinning down /dev/sdc Apr 9 22:17:21 Tower kernel: traps: Plex Transcoder[1111868] general protection fault ip:14a46af4fd26 sp:14a46943f770 error:0 in libh264_decoder.so[14a46ae9f000+13e000] Apr 9 22:21:38 Tower emhttpd: spinning down /dev/sdi Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdk Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdg Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sde Apr 9 22:21:42 Tower emhttpd: spinning down /dev/sdf Apr 9 23:19:02 Tower emhttpd: spinning down /dev/sdh Apr 10 00:19:47 Tower emhttpd: spinning down /dev/sdn Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdm Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdo Apr 10 00:20:07 Tower emhttpd: spinning down /dev/sdl Apr 10 00:20:11 Tower emhttpd: spinning down /dev/sdj Apr 10 01:00:12 Tower emhttpd: read SMART /dev/sde Apr 10 01:00:14 Tower emhttpd: read SMART /dev/sdi Apr 10 01:00:24 Tower emhttpd: read SMART /dev/sdg Apr 10 01:00:24 Tower emhttpd: read SMART /dev/sdf Apr 10 01:03:26 Tower emhttpd: read SMART /dev/sdh Apr 10 02:00:01 Tower Plugin Auto Update: Checking for available plugin updates Apr 10 02:00:02 Tower Plugin Auto Update: Checking for language updates Apr 10 02:00:02 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Apr 10 02:01:23 Tower emhttpd: read SMART /dev/sdo Apr 10 02:10:48 Tower emhttpd: read SMART /dev/sdl Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: veth3b723c7: renamed from eth0 Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: veth32a44e3 (unregistering): left allmulticast mode Apr 10 03:01:09 Tower kernel: veth32a44e3 (unregistering): left promiscuous mode Apr 10 03:01:09 Tower kernel: docker0: port 3(veth32a44e3) entered disabled state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered disabled state Apr 10 03:01:09 Tower kernel: veth9ff322f: entered allmulticast mode Apr 10 03:01:09 Tower kernel: veth9ff322f: entered promiscuous mode Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:09 Tower kernel: docker0: port 3(veth9ff322f) entered forwarding state Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered disabled state Apr 10 03:01:10 Tower kernel: eth0: renamed from veth23aa3cc Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered blocking state Apr 10 03:01:10 Tower kernel: docker0: port 3(veth9ff322f) entered forwarding state Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:12 Tower kernel: veth75603fc: renamed from eth0 Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:12 Tower kernel: veth510c4a0 (unregistering): left allmulticast mode Apr 10 03:01:12 Tower kernel: veth510c4a0 (unregistering): left promiscuous mode Apr 10 03:01:12 Tower kernel: docker0: port 7(veth510c4a0) entered disabled state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered blocking state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered disabled state Apr 10 03:01:13 Tower kernel: veth423eaa6: entered allmulticast mode Apr 10 03:01:13 Tower kernel: veth423eaa6: entered promiscuous mode Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered blocking state Apr 10 03:01:13 Tower kernel: docker0: port 7(veth423eaa6) entered forwarding state Apr 10 03:01:13 Tower kernel: eth0: renamed from vethfde0f6f Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: veth676d27d: renamed from eth0 Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: veth4367e69 (unregistering): left allmulticast mode Apr 10 03:01:15 Tower kernel: veth4367e69 (unregistering): left promiscuous mode Apr 10 03:01:15 Tower kernel: docker0: port 6(veth4367e69) entered disabled state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered blocking state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered disabled state Apr 10 03:01:15 Tower kernel: veth19c9d7d: entered allmulticast mode Apr 10 03:01:15 Tower kernel: veth19c9d7d: entered promiscuous mode Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered blocking state Apr 10 03:01:15 Tower kernel: docker0: port 6(veth19c9d7d) entered forwarding state Apr 10 03:01:15 Tower kernel: eth0: renamed from veth04889ce Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: vethab96854: renamed from eth0 Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: veth09a5ca7 (unregistering): left allmulticast mode Apr 10 03:01:18 Tower kernel: veth09a5ca7 (unregistering): left promiscuous mode Apr 10 03:01:18 Tower kernel: docker0: port 5(veth09a5ca7) entered disabled state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered blocking state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered disabled state Apr 10 03:01:18 Tower kernel: veth06e02b3: entered allmulticast mode Apr 10 03:01:18 Tower kernel: veth06e02b3: entered promiscuous mode Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered blocking state Apr 10 03:01:18 Tower kernel: docker0: port 5(veth06e02b3) entered forwarding state Apr 10 03:01:18 Tower kernel: eth0: renamed from veth69ebad8 Apr 10 03:01:20 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:20 Tower kernel: veth2feba60: renamed from eth0 Apr 10 03:01:21 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:21 Tower kernel: vethec0b410 (unregistering): left allmulticast mode Apr 10 03:01:21 Tower kernel: vethec0b410 (unregistering): left promiscuous mode Apr 10 03:01:21 Tower kernel: docker0: port 4(vethec0b410) entered disabled state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered blocking state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered disabled state Apr 10 03:01:21 Tower kernel: vethf05803a: entered allmulticast mode Apr 10 03:01:21 Tower kernel: vethf05803a: entered promiscuous mode Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered blocking state Apr 10 03:01:21 Tower kernel: docker0: port 4(vethf05803a) entered forwarding state Apr 10 03:01:21 Tower kernel: eth0: renamed from veth7d66b03 Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: veth2da8298: renamed from eth0 Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: vethc3acd7a (unregistering): left allmulticast mode Apr 10 03:01:24 Tower kernel: vethc3acd7a (unregistering): left promiscuous mode Apr 10 03:01:24 Tower kernel: docker0: port 2(vethc3acd7a) entered disabled state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered blocking state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered disabled state Apr 10 03:01:24 Tower kernel: veth1a8aac9: entered allmulticast mode Apr 10 03:01:24 Tower kernel: veth1a8aac9: entered promiscuous mode Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered blocking state Apr 10 03:01:24 Tower kernel: docker0: port 2(veth1a8aac9) entered forwarding state Apr 10 03:01:24 Tower kernel: eth0: renamed from vethdef6b4e Apr 10 03:01:28 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:28 Tower kernel: vethb4343d5: renamed from eth0 Apr 10 03:01:29 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:29 Tower kernel: veth7378604 (unregistering): left allmulticast mode Apr 10 03:01:29 Tower kernel: veth7378604 (unregistering): left promiscuous mode Apr 10 03:01:29 Tower kernel: docker0: port 1(veth7378604) entered disabled state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered blocking state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered disabled state Apr 10 03:01:29 Tower kernel: veth8b136f5: entered allmulticast mode Apr 10 03:01:29 Tower kernel: veth8b136f5: entered promiscuous mode Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered blocking state Apr 10 03:01:29 Tower kernel: docker0: port 1(veth8b136f5) entered forwarding state Apr 10 03:01:29 Tower kernel: eth0: renamed from veth4f38e95 Apr 10 04:10:30 Tower emhttpd: spinning down /dev/sdh Apr 10 04:13:10 Tower emhttpd: spinning down /dev/sdg Apr 10 04:13:10 Tower emhttpd: spinning down /dev/sdf Apr 10 05:01:36 Tower emhttpd: spinning down /dev/sdo Apr 10 05:58:59 Tower emhttpd: spinning down /dev/sdl Apr 10 06:04:21 Tower emhttpd: spinning down /dev/sde Apr 10 06:40:44 Tower emhttpd: read SMART /dev/sde Apr 10 06:46:43 Tower emhttpd: spinning down /dev/sdi Apr 10 07:10:04 Tower rc.rsyslogd: Syslog server daemon... Started. tower-diagnostics-20250410-0713.zip Edited April 10, 20251 yr by onyx00
April 10, 20251 yr Community Expert Start by running memtest, or since memtest is only definitive if it finds errors, and you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.
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.