Server crashing randomly

[RubyRose96]

So within the past month i've been getting weird crashes at pretty random times, all I can tell is that it relates somehow to a network issue. The only way I know it has crashed it because when it does it causes my powerline adapters (renting so can't run wired ethernet ) to 'crash' and will loose their connection to each other and will keep doing so until I unplug the server from the network or kill power to it. Checking the console after it has crashed shows me this.

After doing some digging after the first couple of crashes I set up the syslog server to monitor it, around the time of todays crash this is what the system logged.

Jan 23 20:09:23 Odin vsftpd[5290]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 20:12:01 Odin vsftpd[26931]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 20:12:01 Odin vsftpd[26990]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 20:12:01 Odin vsftpd[27039]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 20:12:01 Odin vsftpd[27041]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 20:12:01 Odin vsftpd[27043]: connect from 192.168.1.103 (192.168.1.103)
Jan 23 21:00:16 Odin crond[1841]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Jan 23 22:00:01 Odin crond[1841]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Jan 23 22:00:43 Odin webGUI: Successful login user root from 192.168.1.103
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered blocking state
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered disabled state
Jan 23 22:03:25 Odin kernel: device vethbda9298 entered promiscuous mode
Jan 23 22:03:25 Odin kernel: IPv6: ADDRCONF(NETDEV_UP): vethbda9298: link is not ready
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered blocking state
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered forwarding state
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered disabled state
Jan 23 22:03:25 Odin kernel: eth0: renamed from veth9de407b
Jan 23 22:03:25 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbda9298: link becomes ready
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered blocking state
Jan 23 22:03:25 Odin kernel: docker0: port 13(vethbda9298) entered forwarding state
Jan 23 22:03:52 Odin kernel: veth9de407b: renamed from eth0
Jan 23 22:03:52 Odin kernel: docker0: port 13(vethbda9298) entered disabled state
Jan 23 22:03:52 Odin kernel: docker0: port 13(vethbda9298) entered disabled state
Jan 23 22:03:52 Odin kernel: device vethbda9298 left promiscuous mode
Jan 23 22:03:52 Odin kernel: docker0: port 13(vethbda9298) entered disabled state
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered blocking state
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered disabled state
Jan 23 22:04:44 Odin kernel: device vethfc06112 entered promiscuous mode
Jan 23 22:04:44 Odin kernel: IPv6: ADDRCONF(NETDEV_UP): vethfc06112: link is not ready
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered blocking state
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered forwarding state
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered disabled state
Jan 23 22:04:44 Odin kernel: eth0: renamed from veth7affb4e
Jan 23 22:04:44 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfc06112: link becomes ready
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered blocking state
Jan 23 22:04:44 Odin kernel: docker0: port 13(vethfc06112) entered forwarding state
Jan 23 22:09:18 Odin kernel: veth7affb4e: renamed from eth0
Jan 23 22:09:18 Odin kernel: docker0: port 13(vethfc06112) entered disabled state
Jan 23 22:09:18 Odin kernel: docker0: port 13(vethfc06112) entered disabled state
Jan 23 22:09:18 Odin kernel: device vethfc06112 left promiscuous mode
Jan 23 22:09:18 Odin kernel: docker0: port 13(vethfc06112) entered disabled state
Jan 23 22:11:17 Odin root: https://raw.githubusercontent.com/Squidly271/unlimited-width/master/unlimited-width.plg
Jan 23 22:11:17 Odin root: https://raw.githubusercontent.com/Squidly271/fix.common.problems/master/plugins/fix.common.problems.plg
Jan 23 22:12:27 Odin kernel: docker0: port 13(vethfe9f459) entered blocking state
Jan 23 22:12:27 Odin kernel: docker0: port 13(vethfe9f459) entered disabled state
Jan 23 22:12:27 Odin kernel: device vethfe9f459 entered promiscuous mode
Jan 23 22:12:27 Odin kernel: IPv6: ADDRCONF(NETDEV_UP): vethfe9f459: link is not ready
Jan 23 22:12:27 Odin kernel: eth0: renamed from veth6ca70cc
Jan 23 22:12:27 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfe9f459: link becomes ready
Jan 23 22:12:27 Odin kernel: docker0: port 13(vethfe9f459) entered blocking state
Jan 23 22:12:27 Odin kernel: docker0: port 13(vethfe9f459) entered forwarding state
Jan 23 22:14:30 Odin kernel: veth6ca70cc: renamed from eth0
Jan 23 22:14:30 Odin kernel: docker0: port 13(vethfe9f459) entered disabled state
Jan 23 22:14:30 Odin kernel: docker0: port 13(vethfe9f459) entered disabled state
Jan 23 22:14:30 Odin kernel: device vethfe9f459 left promiscuous mode
Jan 23 22:14:30 Odin kernel: docker0: port 13(vethfe9f459) entered disabled state
Jan 23 22:15:47 Odin kernel: docker0: port 13(veth1d0fe52) entered blocking state
Jan 23 22:15:47 Odin kernel: docker0: port 13(veth1d0fe52) entered disabled state
Jan 23 22:15:47 Odin kernel: device veth1d0fe52 entered promiscuous mode
Jan 23 22:15:47 Odin kernel: IPv6: ADDRCONF(NETDEV_UP): veth1d0fe52: link is not ready
Jan 23 22:15:47 Odin kernel: eth0: renamed from vethf16ea35
Jan 23 22:15:47 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1d0fe52: link becomes ready
Jan 23 22:15:47 Odin kernel: docker0: port 13(veth1d0fe52) entered blocking state
Jan 23 22:15:47 Odin kernel: docker0: port 13(veth1d0fe52) entered forwarding state

I've got no idea and can't dig up much info, any help would be appreciated. 

Diagnostics also attached.

odin-diagnostics-20210123-2256.zip

[JorgeB]

10 hours ago, RubyRose96 said:

around the time of todays crash this is what the system logged.

If that's all that's logged not much to go on, those are normal, if there's nothing after that the crash is most likely a hardware problem.