Posting diag logs per recommendation from the "Fix Common Problems" plugin. - Logs typically do not fill up immediately after reboot, but will do so after a day or two of runtime. 

 

diagnostics-20190831-1643.zip

Edited March 30, 20215 yr by MarkRMonaco

Aug 30 07:30:27 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php enable 60 > /dev/null 2>&1

? * * *  isn't a valid custom cron entry that you've used for CA turbo mode which doesn't help as this is logged every minute

 

You might want to look at how often mover runs, as you've also got a ton of share cache full messages 

 

Aug 30 08:38:43 WadeWilson kernel: ICMPv6: RA: ndisc_router_discovery failed to add default route

Don't know what this is about, but it's spamming the log every 5 minutes

 

A lot of repeating items in your syslogs... Cache being full, CronTab Parsing, and Router Discovery.

 

Aug 29 12:04:38 WadeWilson shfs: share cache full
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 29 12:04:39 WadeWilson kernel: vfio_ecap_init: 0000:26:00.0 hiding ecap 0x19@0x280
Aug 29 12:04:40 WadeWilson unassigned.devices: Error: Remote SMB/NFS server 'UNRAID-GAMESERV' is off-line and share '//UNRAID-GAMESERV/PlexLogs' cannot be mounted.
Aug 29 12:04:50 WadeWilson shfs: share cache full
### [PREVIOUS LINE REPEATED 5 TIMES] ###
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php enable 60 > /dev/null 2>&1
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 300 > /dev/null 2>&1
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php enable 60 > /dev/null 2>&1
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 300 > /dev/null 2>&1
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php enable 60 > /dev/null 2>&1
Aug 29 12:05:03 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 300 > /dev/null 2>&1
Aug 29 12:05:05 WadeWilson shfs: share cache full
### [PREVIOUS LINE REPEATED 11 TIMES] ###
Aug 29 12:10:04 WadeWilson ntpd[1876]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Aug 29 12:14:00 WadeWilson root: Fix Common Problems Version 2019.06.30a
Aug 29 12:14:08 WadeWilson root: Fix Common Problems: Other Warning: CPU possibly will not throttle down frequency at idle ** Ignored
Aug 29 12:20:51 WadeWilson kernel: ICMPv6: RA: ndisc_router_discovery failed to add default route
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 29 12:25:01 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php enable 60 > /dev/null 2>&1
Aug 29 12:25:01 WadeWilson crond[1896]: failed parsing crontab for user root: ? * * * /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 300 > /dev/null 2>&1

 

Aug 29 13:00:02 WadeWilson shfs: share cache full
### [PREVIOUS LINE REPEATED 1561 TIMES] ###
Aug 29 13:00:30 WadeWilson kernel: ICMPv6: RA: ndisc_router_discovery failed to add default route
Aug 29 13:00:30 WadeWilson shfs: share cache full
### [PREVIOUS LINE REPEATED 20543 TIMES] ###
Aug 29 13:06:52 WadeWilson kernel: ICMPv6: RA: ndisc_router_discovery failed to add default route

Thanks. I'll look into the cron issue. Any ideas on the ICMPv6 router discovery issue?

Disable IPv6 in Network Settings

I'm actually using IPv6 for one of my VMs.

21 minutes ago, MarkRMonaco said:

Any ideas on the ICMPv6 router discovery issue?

Remove the static gateway assignment "fe80::b239:56ff:fef6:ade4"

Edited August 31, 20196 yr by bonienl

If I remove the static gateway, wouldn't that cause issues w/ the statically assigned IPv6 address that I already have configured? When looking at another one of my PC's that is pulling IPv6 via DHCP, I'm seeing the following format "fe80::b239:56ff:fef6:ade4%19".

Best approach is to move away completely from static assignments. Your server will get automatically an IPv6 address assigned.

 

Ok. Made the cron adjustments and deleted the IPv6 static gateway yesterday, but still wound up hitting 100% on the logs a little under 24hrs later. Therefore, I went ahead and switched the IPv6 config to auto (DHCP), as recommend.

Edited September 1, 20196 yr by MarkRMonaco

Not sure what the normal growth rate is for the logs, but its currently at 15% three hours later.

Not sure what the normal growth rate is for the logs, but its currently at 15% three hours later.

Too fast too soon (good movie title?) Post a new set of diags

Sent from my NSA monitored device

Attached.

wadewilson-diagnostics-20190901-2237.zip

So now you're down to this:

Sep  1 13:50:27 WadeWilson shfs: share cache full

Which is probably from your appdata share which is set to use cache: prefer, but it's set to require 512GB of free space (but your cache drive isn't even that large).  Adjust it accordingly

Thanks. The cache drive itself (unformatted) is 512gb, but odd that its configured to require that much space to be available.

"Normal" settings would be in and around 10-20GB

You were definitely right about it being the "appdata" share. I brought it down to 100gb, which matches the vdd size of my only running/remaining VM. - You think that will work, or should I bring it down lower, per your comment above?

I didn't think that last one through.  The vdd would be on the "domains" share. So, I'm going to swap the values around so that "appdata" has a lower threshold, and "domains" is higher.

I think we finally got all of the issues resolved. - About 31hrs after my last reboot, and the logs are only at 1%.