Hi

 

My unraid server is running very slowly. I tried to do a backup of my PC last night using Veeam endpoint backup. The backup was running fine but when i tried to use plex on my TV it could not connect. I was also unable to access the GUI at that time. I stopped the backup and the server became responsive after a minute or so. Ping time to the server are at around 50ms on my local network. Something seems to be really bogging it down.

 

I have tried stopping docker to see if that improves things but pings are still high.

 

If I stop the array completely, piings return to normal. Pings stay at less than 1ms once I start it again. I know that it will eventually slow down again.

 

Not really sure what else to try. I have attached my Diagnostic output. Hopefully someone can shed some light on the issue.

 

Thanks

tower-diagnostics-20160517-0541.zip

5 minutes after starting this thread the pings went back up to 50ms.

 

Here are the last few syslog entries as the problem started. Seems to be something with the network interface.

 

May 17 06:10:51 Tower ntpd[4448]: ntpd exiting on signal 1 (Hangup)

May 17 06:10:51 Tower ntpd[4448]: 127.127.1.0 local addr 127.0.0.1 -> <null>

May 17 06:10:51 Tower ntpd[4448]: 196.41.127.42 local addr 192.168.2.52 -> <null>

May 17 06:10:52 Tower ntpd[8021]: ntpd [email protected] Thu Oct 22 16:52:47 UTC 2015 (1): Starting

May 17 06:10:52 Tower ntpd[8021]: Command line: /usr/sbin/ntpd -g -p /var/run/ntpd.pid

May 17 06:10:52 Tower ntpd[8025]: proto: precision = 0.045 usec (-24)

May 17 06:10:52 Tower ntpd[8025]: restrict default: KOD does nothing without LIMITED.

May 17 06:10:52 Tower ntpd[8025]: Listen and drop on 0 v4wildcard 0.0.0.0:123

May 17 06:10:52 Tower ntpd[8025]: Listen normally on 1 lo 127.0.0.1:123

May 17 06:10:52 Tower ntpd[8025]: Listen normally on 2 br0 192.168.2.52:123

May 17 06:10:52 Tower ntpd[8025]: Listen normally on 3 docker0 172.17.42.1:123

May 17 06:10:52 Tower ntpd[8025]: Listening on routing socket on fd #20 for interface updates

May 17 06:10:52 Tower dhcpcd[1453]: br0: ARP announcing 192.168.2.52 (1 of 2), next in 2.0 seconds

May 17 06:10:54 Tower dhcpcd[1453]: br0: ARP announcing 192.168.2.52 (2 of 2)

May 17 06:11:12 Tower dhcpcd[1453]: br0: xid 0x602e6e is for hwaddr 48:5a:3f:75:b5:65:00:00:00:00:00:00:00:00:00:00

May 17 06:11:20 Tower kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1

May 17 06:15:51 Tower dhcpcd[1453]: br0: renewing lease of 192.168.2.52

May 17 06:15:51 Tower dhcpcd[1453]: br0: rebind in 225 seconds, expire in 300 seconds

May 17 06:15:51 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 3.1 seconds

May 17 06:15:54 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 7.7 seconds

May 17 06:16:02 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 16.6 seconds

May 17 06:16:18 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 32.6 seconds

May 17 06:16:51 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 64.0 seconds

May 17 06:17:55 Tower dhcpcd[1453]: br0: sending REQUEST (xid 0x2ca6ad0c), next in 63.2 seconds

 

Thanks

I tried taking out the network cable from the back of the unraid server. Once I plug it back in it pings are back to sub 1ms. So definitely seems to be a network issue. Possibly a problem with my mikrotik router?

Do you have your server configured to get an IP address via DHCP?  I prefer to assign unRAID a static IP address.

Thanks for the suggestion. I have changed to static now and will see what happens. It does seem to happen when bridge interface "br0" is looking though. Could that possibly be docker containers?