Title kinda sums it up.  System runs fine.  3 dockers (PLEX, NZBGET, SONARR) work fine w/ no delay.  Only the HTTP page is SO SLOW it's almost unusable.  It can take several minutes to load the dashboard. Saw mention of something similar that was a USB controller issue, but my log file has something different than the other users' incident. 

 

Any ideas or pointers would be welcomed.

 

Thanks!

Apr 15 03:44:36 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:03:10 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:05:42 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:07:00 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:07:41 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:08:01 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:08:10 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:09:06 tower kernel: mce_notify_irq: 7 callbacks suppressed
Apr 15 04:09:06 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:09:09 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:10:10 tower kernel: mce_notify_irq: 9 callbacks suppressed
Apr 15 04:10:10 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 04:10:13 tower kernel: mce: [Hardware Error]: Machine check events logged
Apr 15 06:18:04 tower kernel: docker0: port 1(veth69569df) entered disabled state
Apr 15 06:18:04 tower kernel: veth6035b2c: renamed from eth0
Apr 15 06:18:05 tower kernel: docker0: port 1(veth69569df) entered disabled state
Apr 15 06:18:05 tower kernel: device veth69569df left promiscuous mode
Apr 15 06:18:05 tower kernel: docker0: port 1(veth69569df) entered disabled state
Apr 15 06:18:05 tower kernel: docker0: port 1(vethdc9e06c) entered blocking state
Apr 15 06:18:05 tower kernel: docker0: port 1(vethdc9e06c) entered disabled state
Apr 15 06:18:05 tower kernel: device vethdc9e06c entered promiscuous mode
Apr 15 06:18:07 tower kernel: eth0: renamed from veth6a19419
Apr 15 06:18:07 tower kernel: docker0: port 1(vethdc9e06c) entered blocking state
Apr 15 06:18:07 tower kernel: docker0: port 1(vethdc9e06c) entered forwarding state
Apr 15 06:18:38 tower kernel: docker0: port 1(vethdc9e06c) entered disabled state
Apr 15 06:18:38 tower kernel: veth6a19419: renamed from eth0
Apr 15 06:18:39 tower kernel: docker0: port 1(vethdc9e06c) entered disabled state
Apr 15 06:18:39 tower kernel: device vethdc9e06c left promiscuous mode
Apr 15 06:18:39 tower kernel: docker0: port 1(vethdc9e06c) entered disabled state
Apr 15 06:18:39 tower kernel: docker0: port 1(veth74e8edc) entered blocking state
Apr 15 06:18:39 tower kernel: docker0: port 1(veth74e8edc) entered disabled state
Apr 15 06:18:39 tower kernel: device veth74e8edc entered promiscuous mode
Apr 15 06:18:41 tower kernel: eth0: renamed from veth17baf18
Apr 15 06:18:41 tower kernel: docker0: port 1(veth74e8edc) entered blocking state
Apr 15 06:18:41 tower kernel: docker0: port 1(veth74e8edc) entered forwarding state
Apr 15 12:19:08 tower shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/appdata/binhex-plex/transcode/Transcode/Sessions/plex-transcode-kk8egjzw1vefpv6548wmgrq1-51a8be6c-2de3-46c7-ac56-321946b3c3b9 (39) Directory not empty
Apr 15 12:19:08 tower shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/appdata/binhex-plex/transcode/Transcode/Sessions/plex-transcode-kk8egjzw1vefpv6548wmgrq1-51a8be6c-2de3-46c7-ac56-321946b3c3b9 (39) Directory not empty
Apr 15 15:25:49 tower emhttp: shcmd (211238): smbcontrol smbd close-share 'TV'
Apr 15 15:36:26 tower emhttp: shcmd (211374): smbcontrol smbd close-share 'TV'

 

10 hours ago, johnny121b said:

Apr 15 06:18:05 tower kernel: docker0: port 1(veth69569df) entered disabled state
Apr 15 06:18:05 tower kernel: docker0: port 1(vethdc9e06c) entered blocking state
Apr 15 06:18:05 tower kernel: docker0: port 1(vethdc9e06c) entered disabled state
Apr 15 06:18:05 tower kernel: device vethdc9e06c entered promiscuous mode
Apr 15 06:18:07 tower kernel: eth0: renamed from veth6a19419

These are normal, machine checks events are a hardware issue, mcelog might have more info.