Verbose Logging?

[Aaron Oz]

I have an upgraded system, and upgraded unRAID to v6.

 

Functionality seems great, but there is some instability. The server will reboot once in a while. At first, I thought it was the Plex Media server, since it seems to reboot most often while a video is being played. But I also had a couple reboots while it was sitting idle. Regardless, I need to know more before speculating, so I assumed I should start with the log files.

 

I changed the logging to write to the flash drive, temporally for now, to see if there were any clues in the log file. But the log file appears to be very basic.

 

Is there a verbose logging setting that needs to be turned on to catch the events that happen before the server reboots?

 

This is as verbose as the log file is right now;

 

Dec 28 18:25:06 Tower emhttp: shcmd (64): /etc/rc.d/rc.avahidnsconfd start |& logger

Dec 28 18:25:06 Tower logger: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D

Dec 28 18:25:06 Tower avahi-dnsconfd[2817]: Successfully connected to Avahi daemon.

Dec 28 18:25:06 Tower emhttp: Starting Docker...

Dec 28 18:25:06 Tower kernel: BTRFS: device fsid 14b6b999-c0c3-45fb-a6dd-5521b8a051fd devid 1 transid 31401 /dev/loop0

Dec 28 18:25:06 Tower kernel: BTRFS info (device loop0): disk space caching is enabled

Dec 28 18:25:06 Tower kernel: BTRFS: has skinny extents

Dec 28 18:25:07 Tower logger: Resize '/var/lib/docker' of 'max'

Dec 28 18:25:07 Tower logger: starting docker ...

Dec 28 18:25:07 Tower kernel: BTRFS: new size for /dev/loop0 is 10737418240

Dec 28 18:25:07 Tower avahi-daemon[2808]: Server startup complete. Host name is Tower.local. Local service cookie is 476704224.

Dec 28 18:25:08 Tower avahi-daemon[2808]: Service "Tower" (/services/ssh.service) successfully established.

Dec 28 18:25:08 Tower avahi-daemon[2808]: Service "Tower" (/services/smb.service) successfully established.

Dec 28 18:25:08 Tower avahi-daemon[2808]: Service "Tower" (/services/sftp-ssh.service) successfully established.

Dec 28 18:25:10 Tower kernel: ip_tables: © 2000-2006 Netfilter Core Team

Dec 28 18:25:10 Tower avahi-daemon[2808]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1.

Dec 28 18:25:10 Tower avahi-daemon[2808]: New relevant interface docker0.IPv4 for mDNS.

Dec 28 18:25:10 Tower avahi-daemon[2808]: Registering new address record for 172.17.42.1 on docker0.IPv4.

Dec 28 18:25:11 Tower logger: PlexMediaServer: started succesfully!

Dec 28 18:25:11 Tower ntpd[1375]: Listen normally on 3 docker0 172.17.42.1:123

Dec 28 18:25:11 Tower ntpd[1375]: new interface(s) found: waking up resolver

Dec 28 18:25:11 Tower kernel: device vethfbb9413 entered promiscuous mode

Dec 28 18:25:11 Tower kernel: docker0: port 1(vethfbb9413) entered forwarding state

Dec 28 18:25:11 Tower kernel: docker0: port 1(vethfbb9413) entered forwarding state

Dec 28 18:25:11 Tower avahi-daemon[2808]: Withdrawing workstation service for vetheab7d85.

Dec 28 18:25:11 Tower kernel: docker0: port 1(vethfbb9413) entered disabled state

Dec 28 18:25:11 Tower kernel: eth0: renamed from vetheab7d85

Dec 28 18:25:11 Tower kernel: docker0: port 1(vethfbb9413) entered forwarding state

Dec 28 18:25:11 Tower kernel: docker0: port 1(vethfbb9413) entered forwarding state

Dec 28 18:25:13 Tower logger: HandBrake: started succesfully!

Dec 28 18:25:19 Tower logger: Updating templates... Updating info... Done.

Dec 28 18:25:26 Tower kernel: docker0: port 1(vethfbb9413) entered forwarding state

Dec 28 19:20:26 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Dec 28 19:26:48 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'MakeMKV-RDP'

Dec 28 19:26:48 Tower kernel: device veth36a9015 entered promiscuous mode

Dec 28 19:26:48 Tower kernel: docker0: port 2(veth36a9015) entered forwarding state

Dec 28 19:26:48 Tower kernel: docker0: port 2(veth36a9015) entered forwarding state

Dec 28 19:26:48 Tower avahi-daemon[2808]: Withdrawing workstation service for veth115b48a.

Dec 28 19:26:48 Tower kernel: eth0: renamed from veth115b48a

Dec 28 19:27:03 Tower kernel: docker0: port 2(veth36a9015) entered forwarding state

Dec 28 19:59:22 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Dec 28 20:19:20 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

[Squid]

If it just up and resets with no warning and under high cpu load (plex transcoding) odds on it's hardware causing the abrupt reset. (power supply / memory / cpu overheat)

[Aaron Oz]

I appreciate you saying it like it is. The shut down is usually during transcoding in Plex or compressing in handbrake.

 

It's a 775 motherboard with a converted 771 Xeon processor in it. Deep down, I figured that might have issues.

 

I'll start by putting the Core 2 Quad back in and see how it goes from there.

 

Thanks for the input and reality check!