noweakness Posted October 2, 2023 Share Posted October 2, 2023 Can someone point me in the right direction where I can review logs to see why unraid is crashing? When I check the logs after a reboot, they only start after I restart the server. The server has gone offline or been unreachable only after a day or two since I updated, very frustrating. I have also attached my diagnostics if anyone is better at reading them than myself. Thanks in advance. gatekeeper-diagnostics-20231002-1016.zip Quote Link to comment
JorgeB Posted October 2, 2023 Share Posted October 2, 2023 Enable the syslog server and post that after a crash. Quote Link to comment
noweakness Posted October 2, 2023 Author Share Posted October 2, 2023 22 minutes ago, JorgeB said: Enable the syslog server and post that after a crash. Perfect, thank you and will do. Quote Link to comment
noweakness Posted October 4, 2023 Author Share Posted October 4, 2023 On 10/2/2023 at 10:26 AM, JorgeB said: Enable the syslog server and post that after a crash. Hi JorgeB, I have enabled the Syslog server but no logs are being generated. The Local syslog folder is my appdata and I tried another public share, and nothing is showing up. I also setup a remote Syslog server on my home desktop and enabled it on unraid with no logs being detected. My unraid server keeps crashing every 8-12 hours. Anywhere else I can look for whats causing the issue? Quote Link to comment
JorgeB Posted October 4, 2023 Share Posted October 4, 2023 36 minutes ago, noweakness said: but no logs are being generated. Likely you are missing the remote server IP, you have to set the current Unraid IP as mentioned in the instructions, or just enable the mirror to flash drive option. Quote Link to comment
noweakness Posted October 4, 2023 Author Share Posted October 4, 2023 2 hours ago, JorgeB said: Likely you are missing the remote server IP, you have to set the current Unraid IP as mentioned in the instructions, or just enable the mirror to flash drive option. Ok I actually did the mirror to flash drive yesterday as a precaution since I didn't see any logs generated otherwise. At some point between Oct 3 and Oct 4 is when the computer last went offline. By the looks of it the last logs recorded were related to the network port. I'm sure my settings are a mess. I never had any issues before upgrading though which I find strange. Here is a snippet of the logs and I attached the full log (starting Oct 3). Thanks in advance Oct 3 15:16:34 GateKeeper kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbdcda6f: link becomes ready Oct 3 15:16:34 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered blocking state Oct 3 15:16:34 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered forwarding state Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:16:39 GateKeeper kernel: veth179c74e: renamed from eth0 Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:16:39 GateKeeper kernel: device vethbdcda6f left promiscuous mode Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:25:27 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:25:27 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:55:37 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:55:37 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:25:47 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:25:47 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:55:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:55:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:26:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:26:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:56:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:56:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:26:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:26:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:56:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:56:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:26:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:26:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:56:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:56:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:27:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:27:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:57:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:57:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:27:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:27:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:57:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:57:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:27:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:27:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:57:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:57:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:28:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:28:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:58:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:58:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 4 06:41:07 GateKeeper kernel: microcode: microcode updated early to revision 0x49, date = 2021-08-11 Oct 4 06:41:07 GateKeeper kernel: Linux version 6.1.49-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 Oct 4 06:41:07 GateKeeper kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Oct 4 06:41:07 GateKeeper kernel: BIOS-provided physical RAM map: syslog Quote Link to comment
JorgeB Posted October 5, 2023 Share Posted October 5, 2023 12 hours ago, noweakness said: ct 3 23:58:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) These mean a network configuration issue, though won't usually cause crashing, still should be corrected. Quote Link to comment
Recommended Posts
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.