I  am having this random issue. Today (08/05/2024) the system had been going from a uptime of a few days to an uptime of 0. The system then wouldnt last more then 5 minutes then the OS would restart again.THis problem has occured before but it was random. Would be up for a few days some time longer then bang back to an uptime of zero

 

 

text  error  warn  system  array  login  

May  8 09:45:47 Fostar avahi-daemon[7026]: Service "Fostar" (/services/ssh.service) successfully established.
May  8 09:45:47 Fostar avahi-daemon[7026]: Service "Fostar" (/services/smb.service) successfully established.
May  8 09:45:47 Fostar avahi-daemon[7026]: Service "Fostar" (/services/sftp-ssh.service) successfully established.
May  8 09:45:51 Fostar webGUI: Successful login user root from 192.168.86.167
May  8 09:45:52 Fostar kernel: Bridge firewalling registered
May  8 09:45:52 Fostar kernel: Initializing XFRM netlink socket
May  8 09:45:57 Fostar network: reload service: nginx
May  8 09:46:06 Fostar kernel: docker0: port 1(veth72b4ce2) entered blocking state
May  8 09:46:06 Fostar kernel: docker0: port 1(veth72b4ce2) entered disabled state
May  8 09:46:06 Fostar kernel: device veth72b4ce2 entered promiscuous mode
May  8 09:46:06 Fostar emhttpd: nothing to sync
May  8 09:46:08 Fostar kernel: eth0: renamed from veth0423eda
May  8 09:46:08 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth72b4ce2: link becomes ready
May  8 09:46:08 Fostar kernel: docker0: port 1(veth72b4ce2) entered blocking state
May  8 09:46:08 Fostar kernel: docker0: port 1(veth72b4ce2) entered forwarding state
May  8 09:46:09 Fostar rc.docker: binhex-deluge: started succesfully!
May  8 09:46:09 Fostar kernel: docker0: port 2(vethc629388) entered blocking state
May  8 09:46:09 Fostar kernel: docker0: port 2(vethc629388) entered disabled state
May  8 09:46:09 Fostar kernel: device vethc629388 entered promiscuous mode
May  8 09:46:09 Fostar kernel: docker0: port 2(vethc629388) entered blocking state
May  8 09:46:09 Fostar kernel: docker0: port 2(vethc629388) entered forwarding state
May  8 09:46:09 Fostar kernel: docker0: port 2(vethc629388) entered disabled state
May  8 09:46:14 Fostar kernel: eth0: renamed from veth376465c
May  8 09:46:14 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc629388: link becomes ready
May  8 09:46:14 Fostar kernel: docker0: port 2(vethc629388) entered blocking state
May  8 09:46:14 Fostar kernel: docker0: port 2(vethc629388) entered forwarding state
May  8 09:46:15 Fostar rc.docker: binhex-prowlarr: started succesfully!
May  8 09:46:15 Fostar kernel: docker0: port 3(vethe9c0dcf) entered blocking state
May  8 09:46:15 Fostar kernel: docker0: port 3(vethe9c0dcf) entered disabled state
May  8 09:46:15 Fostar kernel: device vethe9c0dcf entered promiscuous mode
May  8 09:46:15 Fostar kernel: docker0: port 3(vethe9c0dcf) entered blocking state
May  8 09:46:15 Fostar kernel: docker0: port 3(vethe9c0dcf) entered forwarding state
May  8 09:46:15 Fostar kernel: docker0: port 3(vethe9c0dcf) entered disabled state
May  8 09:46:24 Fostar kernel: eth0: renamed from vethfb49cd7
May  8 09:46:24 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe9c0dcf: link becomes ready
May  8 09:46:24 Fostar kernel: docker0: port 3(vethe9c0dcf) entered blocking state
May  8 09:46:24 Fostar kernel: docker0: port 3(vethe9c0dcf) entered forwarding state
May  8 09:46:26 Fostar rc.docker: binhex-radarr: started succesfully!
May  8 09:46:26 Fostar kernel: docker0: port 4(veth8f97a9d) entered blocking state
May  8 09:46:26 Fostar kernel: docker0: port 4(veth8f97a9d) entered disabled state
May  8 09:46:26 Fostar kernel: device veth8f97a9d entered promiscuous mode
May  8 09:46:26 Fostar kernel: docker0: port 4(veth8f97a9d) entered blocking state
May  8 09:46:26 Fostar kernel: docker0: port 4(veth8f97a9d) entered forwarding state
May  8 09:46:26 Fostar kernel: docker0: port 4(veth8f97a9d) entered disabled state
May  8 09:46:35 Fostar kernel: eth0: renamed from veth9113627
May  8 09:46:35 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8f97a9d: link becomes ready
May  8 09:46:35 Fostar kernel: docker0: port 4(veth8f97a9d) entered blocking state
May  8 09:46:35 Fostar kernel: docker0: port 4(veth8f97a9d) entered forwarding state
May  8 09:46:36 Fostar rc.docker: binhex-sonarr: started succesfully!
May  8 09:46:36 Fostar kernel: docker0: port 5(veth59bc048) entered blocking state
May  8 09:46:36 Fostar kernel: docker0: port 5(veth59bc048) entered disabled state
May  8 09:46:36 Fostar kernel: device veth59bc048 entered promiscuous mode
May  8 09:46:36 Fostar kernel: docker0: port 5(veth59bc048) entered blocking state
May  8 09:46:36 Fostar kernel: docker0: port 5(veth59bc048) entered forwarding state
May  8 09:46:36 Fostar kernel: docker0: port 5(veth59bc048) entered disabled state
May  8 09:46:47 Fostar kernel: eth0: renamed from veth6f7877d
May  8 09:46:47 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth59bc048: link becomes ready
May  8 09:46:47 Fostar kernel: docker0: port 5(veth59bc048) entered blocking state
May  8 09:46:47 Fostar kernel: docker0: port 5(veth59bc048) entered forwarding state
May  8 09:46:49 Fostar rc.docker: ombi: started succesfully!
May  8 09:46:49 Fostar kernel: docker0: port 6(veth66ee814) entered blocking state
May  8 09:46:49 Fostar kernel: docker0: port 6(veth66ee814) entered disabled state
May  8 09:46:49 Fostar kernel: device veth66ee814 entered promiscuous mode
May  8 09:46:49 Fostar kernel: docker0: port 6(veth66ee814) entered blocking state
May  8 09:46:49 Fostar kernel: docker0: port 6(veth66ee814) entered forwarding state
May  8 09:46:49 Fostar kernel: docker0: port 6(veth66ee814) entered disabled state
May  8 09:47:08 Fostar kernel: eth0: renamed from veth8c4dd09
May  8 09:47:08 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth66ee814: link becomes ready
May  8 09:47:08 Fostar kernel: docker0: port 6(veth66ee814) entered blocking state
May  8 09:47:08 Fostar kernel: docker0: port 6(veth66ee814) entered forwarding state
May  8 09:47:10 Fostar rc.docker: PlexMediaServer: started succesfully!
May  8 09:47:10 Fostar kernel: docker0: port 7(veth5a9fe14) entered blocking state
May  8 09:47:10 Fostar kernel: docker0: port 7(veth5a9fe14) entered disabled state
May  8 09:47:10 Fostar kernel: device veth5a9fe14 entered promiscuous mode
May  8 09:47:10 Fostar kernel: docker0: port 7(veth5a9fe14) entered blocking state
May  8 09:47:10 Fostar kernel: docker0: port 7(veth5a9fe14) entered forwarding state
May  8 09:47:10 Fostar kernel: docker0: port 7(veth5a9fe14) entered disabled state
May  8 09:47:30 Fostar kernel: eth0: renamed from vethfa74fc8
May  8 09:47:30 Fostar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5a9fe14: link becomes ready
May  8 09:47:30 Fostar kernel: docker0: port 7(veth5a9fe14) entered blocking state
May  8 09:47:30 Fostar kernel: docker0: port 7(veth5a9fe14) entered forwarding state
May  8 09:47:33 Fostar rc.docker: youtube-dl-server: started succesfully!
May  8 09:49:02 Fostar root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
May  8 09:49:02 Fostar root: plugin: running: /bin/bash /tmp/unRAIDServer.sh
May  8 09:49:02 Fostar root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://stable.dl.unraid.net/6.12.10/2c9f5b4333711eb5b0739b8597cfc70a41144ae785d09276b87b14ee9ebee585/unRAIDServer-6.12.10-x86_64.zip
May  8 09:49:09 Fostar root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://stable.dl.unraid.net/6.12.10/2c9f5b4333711eb5b0739b8597cfc70a41144ae785d09276b87b14ee9ebee585/unRAIDServer-6.12.10-x86_64.md5
May  8 09:49:10 Fostar root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content
May  8 09:49:10 Fostar root: plugin: running: /bin/bash /tmp/unRAIDServer.sh
May  8 09:50:48 Fostar kernel: bash (18477): drop_caches: 3
May  8 09:51:02 Fostar root: plugin: unRAIDServer.plg installed

Server rebooting on its own is almost always a hardware issue, but can be caused by different components, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU.