22367rh Posted November 18, 2020 Share Posted November 18, 2020 (edited) My UnRaid server was stable for over 100 days without issue but in the last 10+ days it has been becoming unresponsive on the webUI / windows explorer (necessetating a hard reset) so I brought it upstairs and have it plugged into a monitor and keyboard but when it hangs the keyboard no longer sends input (num lock even turns off) thereby forcing more hard resets. I am now resorting to SSH-ing in from my PC (using tail -f /var/log/syslog) in the hopes I get something that could explain the issue... (will post whatever comes out when it next locks up). Currently all I can see is "kernel reports TIME_ERROR: 0x41: Clock Unsynchronized" (not yet locked up but seen a few times recently prior to lock ups) so have followed instructions at the following thread to no avail. These are what I get when telling it to update time which shows it is only very slightly out of sync... Quote root@Tower:~# ntpdate -u pool.ntp.org 18 Nov 17:57:25 ntpdate[13710]: adjust time server 43.252.70.34 offset -0.468997 sec root@Tower:~# ntpdate -u pool.ntp.org 18 Nov 18:03:47 ntpdate[21004]: adjust time server 111.69.49.125 offset -0.275523 sec root@Tower:~# ntpdate -u pool.ntp.org 18 Nov 18:23:14 ntpdate[11886]: adjust time server 122.252.188.99 offset 0.070782 sec I am now at my wits end as not sure what could have changed. I don't run any VMs. Have a handful of Docker images running (including Plex & Transmission). Specs: Ryzen 1700X (8-core @ 3400 MHz) 16 GiB DDR4 @ 2400 MHz (2 sticks of 8 Model CT8G4DFS824A.C8FAD1) Gigabyte B450M DS3H-CF (Bios version F50 - Dated: 2019-Nov-27) Onboard gigabit Ethernet + Aquantia AQC108 5 gigabit RX 550 Graphics Card Drives: 4x 8TB (one is the Parity drive) 1x 6TB 1x 4TB 2x 240GB Sata SSD (cache drives) 32GB USB3 Flash Drive as boot drive Edited November 18, 2020 by 22367rh Add command am using on SSH watcher Quote Link to comment
itimpi Posted November 18, 2020 Share Posted November 18, 2020 To help with getting informed feedback you should post your system’s diagnostics zip file (obtained via Tools -> Diagnostics) so we can get a better feel for the state of your system. Quote Link to comment
22367rh Posted November 18, 2020 Author Share Posted November 18, 2020 Apologies. Here it is. tower-diagnostics-20201118-1829.zip Quote Link to comment
itimpi Posted November 18, 2020 Share Posted November 18, 2020 At a first glance I did not spot anything obvious in the diagnostics. The time issue is not likely to be relevant as the the time being right is normally only important if running with a Trial licence. It occurs to me that you may have updated plugins or docker containers in the period leading up to the start of your instability. You might want to consider doing either/both of the following as part of your diagnostic attempts: booting in Safe Mode to stop any plugins being run in case one of them is loading a component that is incompatible with your current Unraid release. running with docker disabled in case one of them is causing a problem. I believe plex in particular has been known to do this in the past. If it looks like a docker is the culprit you can then progressively enable them to try and identify the guilty party. Quote Link to comment
22367rh Posted November 18, 2020 Author Share Posted November 18, 2020 Have tried stopping all containers after starting the array but still seemed to crash within a matter of hours. Will try the safe mode after the next crash (along with posting full SSH log once it happens). Also it could be that I turned off CPU Pinning on my Docker containers so have set them back up so no container can hog the entire CPU just in case. Quote Link to comment
itimpi Posted November 18, 2020 Share Posted November 18, 2020 The other possibility is that you have a hardware component that is starting to fail. These are always much harder to track down. It might be worth running a RAM check (memtest from the a Unraid Boot menu) in case you have a stick that has started to act up. Power supply is also something that can cause unpredictable failures. Quote Link to comment
22367rh Posted November 18, 2020 Author Share Posted November 18, 2020 Only error just now was: Nov 18 20:14:54 Tower crond[2122]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Full Log from SSH: Quote login as: root Linux 4.19.107-Unraid. root@Tower:~# tail -f /var/log/syslog Nov 18 17:50:05 Tower kernel: md2: stopping Nov 18 17:50:05 Tower kernel: md3: stopping Nov 18 17:50:05 Tower kernel: md4: stopping Nov 18 17:50:05 Tower kernel: md5: stopping Nov 18 17:50:05 Tower emhttpd: shcmd (38): /etc/rc.d/rc.php-fpm start Nov 18 17:50:05 Tower root: Starting php-fpm done Nov 18 17:50:05 Tower emhttpd: shcmd (39): /etc/rc.d/rc.nginx start Nov 18 17:50:05 Tower root: Starting Nginx server daemon... Nov 18 17:51:19 Tower sshd[4870]: Accepted none for root from 192.168.178.93 port 41095 ssh2 Nov 18 17:51:19 Tower rsyslogd: action 'action-3-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ] Nov 18 17:52:00 Tower kernel: mdcmd (43): set md_num_stripes 1280 Nov 18 17:52:00 Tower kernel: mdcmd (44): set md_queue_limit 80 Nov 18 17:52:00 Tower kernel: mdcmd (45): set md_sync_limit 5 Nov 18 17:52:00 Tower kernel: mdcmd (46): set md_write_method Nov 18 17:52:00 Tower kernel: mdcmd (47): set spinup_group 0 0 Nov 18 17:52:00 Tower kernel: mdcmd (48): set spinup_group 1 0 Nov 18 17:52:00 Tower kernel: mdcmd (49): set spinup_group 2 0 Nov 18 17:52:00 Tower kernel: mdcmd (50): set spinup_group 3 0 Nov 18 17:52:00 Tower kernel: mdcmd (51): set spinup_group 4 0 Nov 18 17:52:00 Tower kernel: mdcmd (52): set spinup_group 5 0 Nov 18 17:52:00 Tower emhttpd: shcmd (155): echo 128 > /sys/block/sdi/queue/nr_requests Nov 18 17:52:00 Tower emhttpd: shcmd (156): echo 128 > /sys/block/sde/queue/nr_requests Nov 18 17:52:00 Tower emhttpd: shcmd (157): echo 128 > /sys/block/sdb/queue/nr_requests Nov 18 17:52:00 Tower emhttpd: shcmd (158): echo 128 > /sys/block/sdc/queue/nr_requests Nov 18 17:52:00 Tower emhttpd: shcmd (159): echo 128 > /sys/block/sdd/queue/nr_requests Nov 18 17:52:00 Tower emhttpd: shcmd (160): echo 128 > /sys/block/sdh/queue/nr_requests Nov 18 17:52:00 Tower kernel: mdcmd (53): start STOPPED Nov 18 17:52:00 Tower kernel: unraid: allocating 36230K for 1280 stripes (7 disks) Nov 18 17:52:00 Tower kernel: md1: running, size: 5860522532 blocks Nov 18 17:52:00 Tower kernel: md2: running, size: 7814026532 blocks Nov 18 17:52:00 Tower kernel: md3: running, size: 7814026532 blocks Nov 18 17:52:00 Tower kernel: md4: running, size: 3907018532 blocks Nov 18 17:52:00 Tower kernel: md5: running, size: 7814026532 blocks Nov 18 17:52:00 Tower emhttpd: shcmd (161): udevadm settle Nov 18 17:52:00 Tower root: Starting diskload Nov 18 17:52:00 Tower emhttpd: Mounting disks... Nov 18 17:52:00 Tower emhttpd: shcmd (169): /sbin/btrfs device scan Nov 18 17:52:01 Tower root: Scanning for Btrfs filesystems Nov 18 17:52:01 Tower emhttpd: shcmd (170): mkdir -p /mnt/disk1 Nov 18 17:52:01 Tower emhttpd: shcmd (171): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Nov 18 17:52:01 Tower kernel: SGI XFS with ACLs, security attributes, no debug enabled Nov 18 17:52:01 Tower kernel: XFS (md1): Mounting V5 Filesystem Nov 18 17:52:01 Tower kernel: XFS (md1): Starting recovery (logdev: internal) Nov 18 17:52:01 Tower kernel: XFS (md1): Ending recovery (logdev: internal) Nov 18 17:52:01 Tower emhttpd: shcmd (172): xfs_growfs /mnt/disk1 Nov 18 17:52:01 Tower root: meta-data=/dev/md1 isize=512 agcount=6, agsize=268435455 blks Nov 18 17:52:01 Tower root: = sectsz=512 attr=2, projid32bit=1 Nov 18 17:52:01 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Nov 18 17:52:01 Tower root: = reflink=0 Nov 18 17:52:01 Tower root: data = bsize=4096 blocks=1465130633, imaxpct=5 Nov 18 17:52:01 Tower root: = sunit=0 swidth=0 blks Nov 18 17:52:01 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Nov 18 17:52:01 Tower root: log =internal log bsize=4096 blocks=521728, version=2 Nov 18 17:52:01 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Nov 18 17:52:01 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Nov 18 17:52:01 Tower emhttpd: shcmd (173): mkdir -p /mnt/disk2 Nov 18 17:52:01 Tower emhttpd: shcmd (174): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Nov 18 17:52:01 Tower kernel: XFS (md2): Mounting V5 Filesystem Nov 18 17:52:02 Tower kernel: XFS (md2): Starting recovery (logdev: internal) Nov 18 17:52:02 Tower kernel: XFS (md2): Ending recovery (logdev: internal) Nov 18 17:52:02 Tower emhttpd: shcmd (175): xfs_growfs /mnt/disk2 Nov 18 17:52:02 Tower root: meta-data=/dev/md2 isize=512 agcount=8, agsize=268435455 blks Nov 18 17:52:02 Tower root: = sectsz=512 attr=2, projid32bit=1 Nov 18 17:52:02 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Nov 18 17:52:02 Tower root: = reflink=0 Nov 18 17:52:02 Tower root: data = bsize=4096 blocks=1953506633, imaxpct=5 Nov 18 17:52:02 Tower root: = sunit=0 swidth=0 blks Nov 18 17:52:02 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Nov 18 17:52:02 Tower root: log =internal log bsize=4096 blocks=521728, version=2 Nov 18 17:52:02 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Nov 18 17:52:02 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Nov 18 17:52:02 Tower emhttpd: shcmd (176): mkdir -p /mnt/disk3 Nov 18 17:52:02 Tower emhttpd: shcmd (177): mount -t xfs -o noatime,nodiratime /dev/md3 /mnt/disk3 Nov 18 17:52:02 Tower kernel: XFS (md3): Mounting V5 Filesystem Nov 18 17:52:02 Tower kernel: XFS (md3): Starting recovery (logdev: internal) Nov 18 17:52:02 Tower kernel: XFS (md3): Ending recovery (logdev: internal) Nov 18 17:52:02 Tower emhttpd: shcmd (178): xfs_growfs /mnt/disk3 Nov 18 17:52:02 Tower root: meta-data=/dev/md3 isize=512 agcount=8, agsize=268435455 blks Nov 18 17:52:02 Tower root: = sectsz=512 attr=2, projid32bit=1 Nov 18 17:52:02 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Nov 18 17:52:02 Tower root: = reflink=0 Nov 18 17:52:02 Tower root: data = bsize=4096 blocks=1953506633, imaxpct=5 Nov 18 17:52:02 Tower root: = sunit=0 swidth=0 blks Nov 18 17:52:02 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Nov 18 17:52:02 Tower root: log =internal log bsize=4096 blocks=521728, version=2 Nov 18 17:52:02 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Nov 18 17:52:02 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Nov 18 17:52:02 Tower emhttpd: shcmd (179): mkdir -p /mnt/disk4 Nov 18 17:52:02 Tower emhttpd: shcmd (180): mount -t xfs -o noatime,nodiratime /dev/md4 /mnt/disk4 Nov 18 17:52:02 Tower kernel: XFS (md4): Mounting V5 Filesystem Nov 18 17:52:02 Tower kernel: XFS (md4): Starting recovery (logdev: internal) Nov 18 17:52:03 Tower kernel: XFS (md4): Ending recovery (logdev: internal) Nov 18 17:52:03 Tower emhttpd: shcmd (181): xfs_growfs /mnt/disk4 Nov 18 17:52:03 Tower root: meta-data=/dev/md4 isize=512 agcount=4, agsize=244188659 blks Nov 18 17:52:03 Tower root: = sectsz=512 attr=2, projid32bit=1 Nov 18 17:52:03 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Nov 18 17:52:03 Tower root: = reflink=1 Nov 18 17:52:03 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Nov 18 17:52:03 Tower root: = sunit=0 swidth=0 blks Nov 18 17:52:03 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Nov 18 17:52:03 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Nov 18 17:52:03 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Nov 18 17:52:03 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Nov 18 17:52:03 Tower emhttpd: shcmd (182): mkdir -p /mnt/disk5 Nov 18 17:52:03 Tower emhttpd: shcmd (183): mount -t xfs -o noatime,nodiratime /dev/md5 /mnt/disk5 Nov 18 17:52:03 Tower kernel: XFS (md5): Mounting V5 Filesystem Nov 18 17:52:03 Tower kernel: XFS (md5): Starting recovery (logdev: internal) Nov 18 17:52:03 Tower kernel: XFS (md5): Ending recovery (logdev: internal) Nov 18 17:52:03 Tower emhttpd: shcmd (184): xfs_growfs /mnt/disk5 Nov 18 17:52:03 Tower root: meta-data=/dev/md5 isize=512 agcount=8, agsize=268435455 blks Nov 18 17:52:03 Tower root: = sectsz=512 attr=2, projid32bit=1 Nov 18 17:52:03 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Nov 18 17:52:03 Tower root: = reflink=1 Nov 18 17:52:03 Tower root: data = bsize=4096 blocks=1953506633, imaxpct=5 Nov 18 17:52:03 Tower root: = sunit=0 swidth=0 blks Nov 18 17:52:03 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Nov 18 17:52:03 Tower root: log =internal log bsize=4096 blocks=521728, version=2 Nov 18 17:52:03 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Nov 18 17:52:03 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Nov 18 17:52:03 Tower emhttpd: shcmd (185): mkdir -p /mnt/cache Nov 18 17:52:04 Tower emhttpd: cache uuid: c9368650-0abd-4db8-a826-6f300db49caf Nov 18 17:52:04 Tower emhttpd: cache TotDevices: 2 Nov 18 17:52:04 Tower emhttpd: cache NumDevices: 2 Nov 18 17:52:04 Tower emhttpd: cache NumFound: 2 Nov 18 17:52:04 Tower emhttpd: cache NumMissing: 0 Nov 18 17:52:04 Tower emhttpd: cache NumMisplaced: 0 Nov 18 17:52:04 Tower emhttpd: cache NumExtra: 0 Nov 18 17:52:04 Tower emhttpd: cache LuksState: 0 Nov 18 17:52:04 Tower emhttpd: shcmd (186): mount -t btrfs -o noatime,nodiratime -U c9368650-0abd-4db8-a826-6f300db49caf /mnt/cache Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): disk space caching is enabled Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): has skinny extents Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): enabling ssd optimizations Nov 18 17:52:04 Tower emhttpd: shcmd (187): /sbin/btrfs filesystem resize 1:max /mnt/cache Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): resizing devid 1 Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): new size for /dev/sdf1 is 240057376768 Nov 18 17:52:04 Tower root: Resize '/mnt/cache' of '1:max' Nov 18 17:52:04 Tower emhttpd: shcmd (188): /sbin/btrfs filesystem resize 2:max /mnt/cache Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): resizing devid 2 Nov 18 17:52:04 Tower kernel: BTRFS info (device sdf1): new size for /dev/sdg1 is 240057376768 Nov 18 17:52:04 Tower root: Resize '/mnt/cache' of '2:max' Nov 18 17:52:04 Tower emhttpd: shcmd (189): sync Nov 18 17:52:04 Tower emhttpd: shcmd (190): mkdir /mnt/user0 Nov 18 17:52:04 Tower emhttpd: shcmd (191): /usr/local/sbin/shfs /mnt/user0 -disks 62 -o noatime,allow_other |& logger Nov 18 17:52:04 Tower shfs: use_ino: 1 Nov 18 17:52:04 Tower shfs: direct_io: 0 Nov 18 17:52:04 Tower emhttpd: shcmd (192): mkdir /mnt/user Nov 18 17:52:04 Tower emhttpd: shcmd (193): /usr/local/sbin/shfs /mnt/user -disks 63 2048000000 -o noatime,allow_other -o remember=0 |& logger Nov 18 17:52:04 Tower shfs: use_ino: 1 Nov 18 17:52:04 Tower shfs: direct_io: 0 Nov 18 17:52:04 Tower emhttpd: shcmd (195): /usr/local/sbin/update_cron Nov 18 17:52:04 Tower root: Creating custom tabs Nov 18 17:52:04 Tower emhttpd: Starting services... Nov 18 17:52:04 Tower emhttpd: shcmd (197): /etc/rc.d/rc.samba restart Nov 18 17:52:06 Tower root: Starting Samba: /usr/sbin/smbd -D Nov 18 17:52:06 Tower root: /usr/sbin/nmbd -D Nov 18 17:52:06 Tower root: /usr/sbin/wsdd Nov 18 17:52:07 Tower root: /usr/sbin/winbindd -D Nov 18 17:52:07 Tower emhttpd: shcmd (212): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 100 Nov 18 17:52:07 Tower kernel: BTRFS: device fsid d39d4e2b-8571-4325-8c50-414818af0687 devid 1 transid 1153760 /dev/loop2 Nov 18 17:52:07 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Nov 18 17:52:07 Tower kernel: BTRFS info (device loop2): has skinny extents Nov 18 17:52:07 Tower kernel: BTRFS info (device loop2): start tree-log replay Nov 18 17:52:07 Tower kernel: BTRFS info (device loop2): checking UUID tree Nov 18 17:52:08 Tower root: Resize '/var/lib/docker' of 'max' Nov 18 17:52:08 Tower kernel: BTRFS info (device loop2): new size for /dev/loop2 is 107374182400 Nov 18 17:52:08 Tower emhttpd: shcmd (214): /etc/rc.d/rc.docker start Nov 18 17:52:08 Tower root: starting dockerd ... Nov 18 17:52:11 Tower avahi-daemon[4516]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Nov 18 17:52:11 Tower avahi-daemon[4516]: New relevant interface docker0.IPv4 for mDNS. Nov 18 17:52:11 Tower avahi-daemon[4516]: Registering new address record for 172.17.0.1 on docker0.IPv4. Nov 18 17:52:11 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Nov 18 17:52:14 Tower kernel: docker0: port 1(veth76319e8) entered blocking state Nov 18 17:52:14 Tower kernel: docker0: port 1(veth76319e8) entered disabled state Nov 18 17:52:14 Tower kernel: device veth76319e8 entered promiscuous mode Nov 18 17:52:14 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth76319e8: link is not ready Nov 18 17:52:14 Tower kernel: docker0: port 1(veth76319e8) entered blocking state Nov 18 17:52:14 Tower kernel: docker0: port 1(veth76319e8) entered forwarding state Nov 18 17:52:14 Tower kernel: docker0: port 1(veth76319e8) entered disabled state Nov 18 17:52:17 Tower kernel: eth0: renamed from veth0b01867 Nov 18 17:52:17 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth76319e8: link becomes ready Nov 18 17:52:17 Tower kernel: docker0: port 1(veth76319e8) entered blocking state Nov 18 17:52:17 Tower kernel: docker0: port 1(veth76319e8) entered forwarding state Nov 18 17:52:17 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Nov 18 17:52:19 Tower kernel: mdcmd (54): check Nov 18 17:52:19 Tower kernel: md: recovery thread: check P ... Nov 18 17:52:19 Tower avahi-daemon[4516]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:ebff:fe1b:5ef3. Nov 18 17:52:19 Tower avahi-daemon[4516]: New relevant interface docker0.IPv6 for mDNS. Nov 18 17:52:19 Tower avahi-daemon[4516]: Registering new address record for fe80::42:ebff:fe1b:5ef3 on docker0.*. Nov 18 17:52:19 Tower avahi-daemon[4516]: Joining mDNS multicast group on interface veth76319e8.IPv6 with address fe80::a4e1:d2ff:fe6b:4c05. Nov 18 17:52:19 Tower avahi-daemon[4516]: New relevant interface veth76319e8.IPv6 for mDNS. Nov 18 17:52:19 Tower avahi-daemon[4516]: Registering new address record for fe80::a4e1:d2ff:fe6b:4c05 on veth76319e8.*. Nov 18 17:52:34 Tower kernel: mdcmd (55): nocheck Cancel Nov 18 17:52:34 Tower kernel: md: recovery thread: exit status: -4 Nov 18 17:52:36 Tower rc.docker: PMS: started succesfully! Nov 18 17:52:36 Tower kernel: docker0: port 2(veth0eabf83) entered blocking state Nov 18 17:52:36 Tower kernel: docker0: port 2(veth0eabf83) entered disabled state Nov 18 17:52:36 Tower kernel: device veth0eabf83 entered promiscuous mode Nov 18 17:52:36 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth0eabf83: link is not ready Nov 18 17:52:36 Tower kernel: docker0: port 2(veth0eabf83) entered blocking state Nov 18 17:52:36 Tower kernel: docker0: port 2(veth0eabf83) entered forwarding state Nov 18 17:52:36 Tower kernel: docker0: port 2(veth0eabf83) entered disabled state Nov 18 17:52:41 Tower kernel: eth0: renamed from vethe10bcd3 Nov 18 17:52:41 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0eabf83: link becomes ready Nov 18 17:52:41 Tower kernel: docker0: port 2(veth0eabf83) entered blocking state Nov 18 17:52:41 Tower kernel: docker0: port 2(veth0eabf83) entered forwarding state Nov 18 17:52:42 Tower rc.docker: speedtest-tracker: started succesfully! Nov 18 17:52:43 Tower kernel: docker0: port 3(vethc76e1a6) entered blocking state Nov 18 17:52:43 Tower kernel: docker0: port 3(vethc76e1a6) entered disabled state Nov 18 17:52:43 Tower kernel: device vethc76e1a6 entered promiscuous mode Nov 18 17:52:43 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethc76e1a6: link is not ready Nov 18 17:52:43 Tower kernel: docker0: port 3(vethc76e1a6) entered blocking state Nov 18 17:52:43 Tower kernel: docker0: port 3(vethc76e1a6) entered forwarding state Nov 18 17:52:43 Tower kernel: docker0: port 3(vethc76e1a6) entered disabled state Nov 18 17:52:43 Tower avahi-daemon[4516]: Joining mDNS multicast group on interface veth0eabf83.IPv6 with address fe80::d89e:16ff:feb7:c63d. Nov 18 17:52:43 Tower avahi-daemon[4516]: New relevant interface veth0eabf83.IPv6 for mDNS. Nov 18 17:52:43 Tower avahi-daemon[4516]: Registering new address record for fe80::d89e:16ff:feb7:c63d on veth0eabf83.*. Nov 18 17:52:47 Tower kernel: eth0: renamed from veth55df824 Nov 18 17:52:47 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc76e1a6: link becomes ready Nov 18 17:52:47 Tower kernel: docker0: port 3(vethc76e1a6) entered blocking state Nov 18 17:52:47 Tower kernel: docker0: port 3(vethc76e1a6) entered forwarding state Nov 18 17:52:48 Tower avahi-daemon[4516]: Joining mDNS multicast group on interface vethc76e1a6.IPv6 with address fe80::bc2d:40ff:fed3:4433. Nov 18 17:52:48 Tower avahi-daemon[4516]: New relevant interface vethc76e1a6.IPv6 for mDNS. Nov 18 17:52:48 Tower avahi-daemon[4516]: Registering new address record for fe80::bc2d:40ff:fed3:4433 on vethc76e1a6.*. Nov 18 17:52:49 Tower rc.docker: Transmission: started succesfully! Nov 18 17:54:20 Tower ool www[5030]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Nov 18 17:54:22 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="9896" x-info="https://www.rsyslog.com"] start Nov 18 17:55:14 Tower login[4331]: ROOT LOGIN on '/dev/tty1' Nov 18 17:56:52 Tower sshd[13074]: Accepted none for root from 192.168.178.93 port 41713 ssh2 Nov 18 18:00:26 Tower ntpd[2101]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Nov 18 18:34:04 Tower kernel: veth0b01867: renamed from eth0 Nov 18 18:34:04 Tower kernel: docker0: port 1(veth76319e8) entered disabled state Nov 18 18:34:05 Tower kernel: docker0: port 1(veth76319e8) entered disabled state Nov 18 18:34:05 Tower kernel: device veth76319e8 left promiscuous mode Nov 18 18:34:05 Tower kernel: docker0: port 1(veth76319e8) entered disabled state Nov 18 18:34:06 Tower kernel: veth55df824: renamed from eth0 Nov 18 18:34:06 Tower kernel: docker0: port 3(vethc76e1a6) entered disabled state Nov 18 18:34:07 Tower kernel: docker0: port 3(vethc76e1a6) entered disabled state Nov 18 18:34:07 Tower kernel: device vethc76e1a6 left promiscuous mode Nov 18 18:34:07 Tower kernel: docker0: port 3(vethc76e1a6) entered disabled state Nov 18 18:34:08 Tower kernel: vethe10bcd3: renamed from eth0 Nov 18 18:34:08 Tower kernel: docker0: port 2(veth0eabf83) entered disabled state Nov 18 18:34:10 Tower kernel: docker0: port 2(veth0eabf83) entered disabled state Nov 18 18:34:10 Tower kernel: device veth0eabf83 left promiscuous mode Nov 18 18:34:10 Tower kernel: docker0: port 2(veth0eabf83) entered disabled state Nov 18 18:34:32 Tower kernel: docker0: port 1(vethec861ee) entered blocking state Nov 18 18:34:32 Tower kernel: docker0: port 1(vethec861ee) entered disabled state Nov 18 18:34:32 Tower kernel: device vethec861ee entered promiscuous mode Nov 18 18:34:32 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethec861ee: link is not ready Nov 18 18:34:38 Tower kernel: eth0: renamed from veth8df04ea Nov 18 18:34:38 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethec861ee: link becomes ready Nov 18 18:34:38 Tower kernel: docker0: port 1(vethec861ee) entered blocking state Nov 18 18:34:38 Tower kernel: docker0: port 1(vethec861ee) entered forwarding state Nov 18 18:34:41 Tower kernel: docker0: port 2(veth8b6d895) entered blocking state Nov 18 18:34:41 Tower kernel: docker0: port 2(veth8b6d895) entered disabled state Nov 18 18:34:41 Tower kernel: device veth8b6d895 entered promiscuous mode Nov 18 18:34:41 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth8b6d895: link is not ready Nov 18 18:34:41 Tower kernel: docker0: port 2(veth8b6d895) entered blocking state Nov 18 18:34:41 Tower kernel: docker0: port 2(veth8b6d895) entered forwarding state Nov 18 18:34:41 Tower kernel: docker0: port 2(veth8b6d895) entered disabled state Nov 18 18:34:45 Tower kernel: eth0: renamed from veth950539b Nov 18 18:34:45 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8b6d895: link becomes ready Nov 18 18:34:45 Tower kernel: docker0: port 2(veth8b6d895) entered blocking state Nov 18 18:34:45 Tower kernel: docker0: port 2(veth8b6d895) entered forwarding state Nov 18 18:35:16 Tower kernel: docker0: port 3(veth1472e48) entered blocking state Nov 18 18:35:16 Tower kernel: docker0: port 3(veth1472e48) entered disabled state Nov 18 18:35:16 Tower kernel: device veth1472e48 entered promiscuous mode Nov 18 18:35:16 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth1472e48: link is not ready Nov 18 18:35:16 Tower kernel: docker0: port 3(veth1472e48) entered blocking state Nov 18 18:35:16 Tower kernel: docker0: port 3(veth1472e48) entered forwarding state Nov 18 18:35:16 Tower kernel: docker0: port 3(veth1472e48) entered disabled state Nov 18 18:35:22 Tower kernel: eth0: renamed from vethd566de6 Nov 18 18:35:22 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1472e48: link becomes ready Nov 18 18:35:22 Tower kernel: docker0: port 3(veth1472e48) entered blocking state Nov 18 18:35:22 Tower kernel: docker0: port 3(veth1472e48) entered forwarding state Nov 18 18:38:23 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sda Nov 18 18:43:21 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdi Nov 18 18:52:34 Tower kernel: veth8df04ea: renamed from eth0 Nov 18 18:52:34 Tower kernel: docker0: port 1(vethec861ee) entered disabled state Nov 18 18:52:35 Tower kernel: docker0: port 1(vethec861ee) entered disabled state Nov 18 18:52:35 Tower kernel: device vethec861ee left promiscuous mode Nov 18 18:52:35 Tower kernel: docker0: port 1(vethec861ee) entered disabled state Nov 18 19:03:38 Tower kernel: vethd566de6: renamed from eth0 Nov 18 19:03:38 Tower kernel: docker0: port 3(veth1472e48) entered disabled state Nov 18 19:03:59 Tower kernel: docker0: port 3(veth1472e48) entered disabled state Nov 18 19:03:59 Tower kernel: device veth1472e48 left promiscuous mode Nov 18 19:03:59 Tower kernel: docker0: port 3(veth1472e48) entered disabled state Nov 18 19:06:46 Tower kernel: veth950539b: renamed from eth0 Nov 18 19:06:46 Tower kernel: docker0: port 2(veth8b6d895) entered disabled state Nov 18 19:06:50 Tower kernel: docker0: port 2(veth8b6d895) entered disabled state Nov 18 19:06:50 Tower kernel: device veth8b6d895 left promiscuous mode Nov 18 19:06:50 Tower kernel: docker0: port 2(veth8b6d895) entered disabled state Nov 18 19:15:20 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove dynamix.system.info.plg Nov 18 19:15:20 Tower root: plugin: running: anonymous Nov 18 19:15:29 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove dynamix.system.buttons.plg Nov 18 19:15:29 Tower root: plugin: running: anonymous Nov 18 19:15:39 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove speedtest.plg Nov 18 19:15:39 Tower root: plugin: running: anonymous Nov 18 19:15:44 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove unbalance.plg Nov 18 19:15:44 Tower root: plugin: running: anonymous Nov 18 19:18:16 Tower kernel: docker0: port 1(vethf932097) entered blocking state Nov 18 19:18:16 Tower kernel: docker0: port 1(vethf932097) entered disabled state Nov 18 19:18:16 Tower kernel: device vethf932097 entered promiscuous mode Nov 18 19:18:16 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethf932097: link is not ready Nov 18 19:18:16 Tower kernel: docker0: port 1(vethf932097) entered blocking state Nov 18 19:18:16 Tower kernel: docker0: port 1(vethf932097) entered forwarding state Nov 18 19:18:16 Tower kernel: docker0: port 1(vethf932097) entered disabled state Nov 18 19:18:19 Tower kernel: eth0: renamed from vethb22179c Nov 18 19:18:19 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf932097: link becomes ready Nov 18 19:18:19 Tower kernel: docker0: port 1(vethf932097) entered blocking state Nov 18 19:18:19 Tower kernel: docker0: port 1(vethf932097) entered forwarding state Nov 18 20:14:54 Tower crond[2122]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Going to run a memtest overnight as it has crashed close enough to bed time to be feasable. Quote Link to comment
JorgeB Posted November 18, 2020 Share Posted November 18, 2020 Also make sure you're using the correct "Power Supply Idle Control" setting. Quote Link to comment
22367rh Posted November 18, 2020 Author Share Posted November 18, 2020 So I have now Disabled Cool-n-quiet & C-States in my BIOS. Will see if that makes a difference today. Quote Link to comment
JorgeB Posted November 19, 2020 Share Posted November 19, 2020 No need to disable it if you use the correct setting above. Quote Link to comment
22367rh Posted November 22, 2020 Author Share Posted November 22, 2020 Issue seems to have been resolved. Stable for 48 hours. And shut it down to move back to it's usual place and been up for 26hrs now Thank you all 1 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.