I'm rather noobish despite using Unraid for over a year now. I rely heavily on Spaceinvaderones awesome videos and the combined knowledge of this amazing community. Unfortunately, this one has me stumped. Unraid will simply lock up, I am unable to do anything but perform a manual reboot. I am crap with terminal unless I have precise instructions so please keep that in mind.

 

I have spend considerable time researching the issue but the only thing I have gleaned from it all is that it is likely a network issue.

 

I finally managed to grab the log and this is the days log up to the last freeze.

 

Dec 27 04:00:07 Jarvis crond[1833]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

Dec 27 04:28:31 Jarvis kernel: Plex Media Scan[8866]: segfault at 0 ip 000014a985c73bcd sp 00007ffd336e34e0 error 4 in libavcodec.so.58[14a985c30000+3ed000] Dec 27 04:28:31 Jarvis kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

Dec 27 04:35:14 Jarvis kernel: Plex Media Scan[2833]: segfault at 0 ip 00001524da879bcd sp 00007ffe12a4a330 error 4 in libavcodec.so.58[1524da836000+3ed000] Dec 27 04:35:14 Jarvis kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

Dec 27 06:00:47 Jarvis root: /etc/libvirt: 921.5 MiB (966209536 bytes) trimmed on /dev/loop3

Dec 27 06:00:47 Jarvis root: /var/lib/docker: 12.2 GiB (13090787328 bytes) trimmed on /dev/loop2

Dec 27 06:00:47 Jarvis root: /mnt/cache: 876.2 GiB (940782350336 bytes) trimmed on /dev/sdb1

Dec 27 11:50:05 Jarvis kernel: br0: port 2(vnet0) entered blocking state

Dec 27 11:50:05 Jarvis kernel: br0: port 2(vnet0) entered disabled state

Dec 27 11:50:05 Jarvis kernel: device vnet0 entered promiscuous mode

Dec 27 11:50:05 Jarvis kernel: br0: port 2(vnet0) entered blocking state

Dec 27 11:50:05 Jarvis kernel: br0: port 2(vnet0) entered forwarding state

Dec 27 11:50:31 Jarvis kernel: perf: interrupt took too long (3161 > 3137), lowering kernel.perf_event_max_sample_rate to 63000

Dec 27 12:44:06 Jarvis kernel: br0: port 2(vnet0) entered disabled state

Dec 27 12:44:06 Jarvis kernel: device vnet0 left promiscuous mode

Dec 27 12:44:06 Jarvis kernel: br0: port 2(vnet0) entered disabled state

Dec 27 15:23:41 Jarvis kernel: docker0: port 1(veth6cdacb7) entered disabled state

Dec 27 15:23:41 Jarvis kernel: veth843fafe: renamed from eth0

Dec 27 15:23:41 Jarvis kernel: docker0: port 1(veth6cdacb7) entered disabled state

Dec 27 15:23:41 Jarvis kernel: device veth6cdacb7 left promiscuous mode

Dec 27 15:23:41 Jarvis kernel: docker0: port 1(veth6cdacb7) entered disabled state

Dec 27 15:23:45 Jarvis kernel: docker0: port 1(vethab20bfb) entered blocking state

Dec 27 15:23:45 Jarvis kernel: docker0: port 1(vethab20bfb) entered disabled state

Dec 27 15:23:45 Jarvis kernel: device vethab20bfb entered promiscuous mode

Dec 27 15:23:45 Jarvis kernel: IPv6: ADDRCONF(NETDEV_UP): vethab20bfb: link is not ready

Dec 27 15:23:46 Jarvis kernel: eth0: renamed from vethcadeda1

Dec 27 15:23:46 Jarvis kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethab20bfb: link becomes ready

Dec 27 15:23:46 Jarvis kernel: docker0: port 1(vethab20bfb) entered blocking state

Dec 27 15:23:46 Jarvis kernel: docker0: port 1(vethab20bfb) entered forwarding state

Dec 27 15:24:22 Jarvis kernel: veth12e50b0: renamed from eth0

Dec 27 15:24:22 Jarvis kernel: docker0: port 5(veth3a863ed) entered disabled state

Dec 27 15:24:23 Jarvis kernel: docker0: port 5(veth3a863ed) entered disabled state

Dec 27 15:24:23 Jarvis kernel: device veth3a863ed left promiscuous mode

Dec 27 15:24:23 Jarvis kernel: docker0: port 5(veth3a863ed) entered disabled state

Dec 27 15:24:25 Jarvis kernel: docker0: port 5(veth4171cd4) entered blocking state

Dec 27 15:24:25 Jarvis kernel: docker0: port 5(veth4171cd4) entered disabled state

Dec 27 15:24:25 Jarvis kernel: device veth4171cd4 entered promiscuous mode

Dec 27 15:24:25 Jarvis kernel: IPv6: ADDRCONF(NETDEV_UP): veth4171cd4: link is not ready

Dec 27 15:24:25 Jarvis kernel: docker0: port 5(veth4171cd4) entered blocking state

Dec 27 15:24:25 Jarvis kernel: docker0: port 5(veth4171cd4) entered forwarding state

Dec 27 15:24:25 Jarvis kernel: docker0: port 5(veth4171cd4) entered disabled state

Dec 27 15:24:26 Jarvis kernel: eth0: renamed from vethfbbb7b0

Dec 27 15:24:26 Jarvis kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4171cd4: link becomes ready

Dec 27 15:24:26 Jarvis kernel: docker0: port 5(veth4171cd4) entered blocking state

Dec 27 15:24:26 Jarvis kernel: docker0: port 5(veth4171cd4) entered forwarding state

 

Please let me know if you need any more information and thank you for your help.

Edited December 28, 20196 yr by hooversdlhd

Describe "random freezes". Does the GUI become unresponsive, but dockers/VMs/SSH sessions remain available? Do Dockers stop but the GUI remains available? Does the whole server hang and nothing but pushing the power button works to get it back up and running?

 

If you have terminal access, but the GUI has frozen, from the terminal type "diagnostics" and hit enter. It will create a full diagnostics file that will be stored in /root/logs. You can access that remotely (if you've shared your flash drive) at \\server\flash\logs\<servername>-diagnostics-<date>-<time>.zip. Post that.

 

Also, you can go to Settings | Network Services | Syslog Server and set "Mirror syslog to flag" to "Yes" so that your syslogs will persist after a reboot. Posting both diagnostics and a full syslog from the time leading up to the "freeze" will help the experts diagnose your issues.

Thank's for the quick reply FreeMan

 

The server become completely unresponsive, GUI, dockers, terminal all freeze.

 

I do have the full log, I just wasn't sure how much you would need.

jarvis-syslog-127.0.0.1-20191228-1611.zip jarvis-diagnostics-20191228-1011.zip

Full diagnostics are always best. It's a tiny file, so not an issue if not needed. 

 

I'm not the expert to parse that and identify the issue, but someone will be along soon who can.

Has happened two more times. I am at a loss.

On 1/2/2020 at 8:59 AM, hooversdlhd said:

Has happened two more times. I am at a loss.

Not trying to resurrect a dead thread... but did you ever figure out what was going wrong?  Having the same issue, and I started running Memtest across 4 sticks.  All passed a total of 16 scans, but with 4 sticks in it becomes unstable.  2 sticks seem fine...

I eventually dropped in a new motherboard. I suspect there was an issue with the memory connections. I haven't had a problem since then.