Can someone check their syslog and tell me what your system does after it's loaded the last docker successfully?  My server has been rebooting at this point.  I feel like if I know what the next process is after the last docker was loaded I may know where my server is dying.

 

So here's a snippet from a recent syslog.  For me, openvpn is my last docker alphabetically to load.  After your last one loads what does your syslog show? 

 

Thanks..

 

Oct 27 15:16:17 Snuts rc.docker: nextcloud: started succesfully!
Oct 27 15:16:17 Snuts kernel: docker0: port 6(vethfd3be47) entered blocking state
Oct 27 15:16:17 Snuts kernel: docker0: port 6(vethfd3be47) entered disabled state
Oct 27 15:16:17 Snuts kernel: device vethfd3be47 entered promiscuous mode
Oct 27 15:16:17 Snuts kernel: IPv6: ADDRCONF(NETDEV_UP): vethfd3be47: link is not ready
Oct 27 15:16:17 Snuts kernel: docker0: port 6(vethfd3be47) entered blocking state
Oct 27 15:16:17 Snuts kernel: docker0: port 6(vethfd3be47) entered forwarding state
Oct 27 15:16:17 Snuts kernel: eth0: renamed from veth2d15c3f
Oct 27 15:16:17 Snuts kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfd3be47: link becomes ready
Oct 27 15:16:17 Snuts rc.docker: openvpn-as: started succesfully!
Oct 27 15:16:36 Snuts kernel: TCP: request_sock_TCP: Possible SYN flooding on port 39268. Sending cookies.  Check SNMP counters.

>crash and reboot here<

The last bits in my syslog from Docker. The next bits in the log are minutes later when I initiated something else.

 

Oct 19 13:36:47 REAVER kernel: device br0 entered promiscuous mode
Oct 19 13:36:47 REAVER rc.docker: EggDrop: started succesfully!
Oct 19 13:36:47 REAVER kernel: eth0: renamed from vethb573e85
Oct 19 13:36:47 REAVER rc.docker: EmbyServer: started succesfully!
Oct 19 13:36:48 REAVER kernel: eth0: renamed from veth3dc263d
Oct 19 13:36:48 REAVER rc.docker: nzbget: started succesfully!
 

Alright so docker loading may be totally unrelated to my issue.  I may just have a bad motherboard.  After enough hard reboots my usb starts to get corrupted and loses the server info and defaults to Tower from the server name I gave it on initial install.  2nd bad motherboard in a row?  Supermicro x9scm-f.  Just wish I could definitively pin point if my issue is software or hardware related.  I hate blindly throwing money at issues in a lame pin the tail on the donkey game of buying, applying, and praying its now fixed.  Any help available from Unraid?

Have you run extensive MemTest overnight?

 

33 minutes ago, BRiT said:

Have you run extensive MemTest overnight?

 

ya ran it for 24 hours with zero errors just yesterday

10 hours ago, DontWorryScro said:

ya ran it for 24 hours with zero errors just yesterday

You have ECC RAM, according to your sig. It corrects single errors and the system halts if it detects multiple errors. Have you checked the BIOS event log?

I only see fan sensor events. Are these relevant?  I just figured this was akin to benign messaging to display fan speed changes based on temperature.