Hello,
I've set up my FreeNAS box again and I think that I'm seriously a magnet for trouble when it comes to FreeNAS...
This time I've encountered a problem where the FreeNAS box randomly resets all network connections every minute, making it unaccessible for a few seconds every time. It didn't start until I enabled CIFS sharing and Active Directory authentication and I first noticed that all connections to FreeNAS would drop if I initiated a file transfer even though browsing worked fine. It's not only related to Samba because any SSH connection also stops working, and I see latency spikes from NFS clients even though the connection remains.
I've tried to turn off both the CIFS and Active Directory service and rebooted the FreeNAS box with no improvement. It still seems to be triggered with about a minute in between and I can't find any trace of the issue in any logs.
Specs:
Intel Core i3 3220
16GB RAM
4x 2TB 7200 rpm drives, confed as 2x mirror vdevs.
Intel i350-T2 NIC for main data and build in Realtek NIC for management traffic.
FreeNAS 8.3.1-BETA3
EDIT:
Okay, it seems I've made a mistake when ruling out the firewall, which probably is the cause here. I do not under stand why though since it should pass all traffic between the hosts.
Did you resolve this?
We are having an identical issue with our Dell T620 with an Intel I350DP adapter. This entry hits /var/log/messages about every minute.
Feb 25 16:25:05 freenas notifier: devd already running? (pid=1119).
Feb 25 16:25:05 freenas notifier: Setting hostuuid: 4c4c4544-0051-5610-8030-c3c04f515731.
Feb 25 16:25:05 freenas notifier: Setting hostid: 0xb65d682f.
Feb 25 16:25:06 freenas notifier: Starting Network: lo0 igb0 igb1.
Feb 25 16:25:06 freenas notifier: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
Feb 25 16:25:06 freenas notifier: options=3<RXCSUM,TXCSUM>
Feb 25 16:25:06 freenas notifier: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
Feb 25 16:25:06 freenas notifier: inet6 ::1 prefixlen 128
Feb 25 16:25:06 freenas notifier: inet 127.0.0.1 netmask 0xff000000
Feb 25 16:25:06 freenas notifier: nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
Feb 25 16:25:06 freenas notifier: igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
Feb 25 16:25:06 freenas notifier: options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
Feb 25 16:25:06 freenas notifier: ether a0:36:9f:06:8b:1e
Feb 25 16:25:06 freenas notifier: inet 10.1.1.96 netmask 0xffffff00 broadcast 10.1.1.255
Feb 25 16:25:06 freenas notifier: media: Ethernet autoselect (1000baseT <full-duplex>)
Feb 25 16:25:06 freenas notifier: status: active
Feb 25 16:25:06 freenas notifier: igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
Feb 25 16:25:06 freenas notifier: options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
Feb 25 16:25:06 freenas notifier: ether a0:36:9f:06:8b:1f
Feb 25 16:25:06 freenas notifier: inet 10.1.1.92 netmask 0xffffff00 broadcast 10.1.1.255
Feb 25 16:25:06 freenas notifier: media: Ethernet autoselect (1000baseT <full-duplex>)
Feb 25 16:25:06 freenas notifier: status: active
Feb 25 16:25:06 freenas root: /etc/rc.d/dhclient: ERROR: /etc/rc.d/dhclient: no interface specified
Feb 25 16:25:06 freenas notifier: /etc/rc.d/dhclient: ERROR: /etc/rc.d/dhclient: no interface specified
Feb 25 16:25:06 freenas notifier: route: writing to routing socket: File exists
Feb 25 16:25:06 freenas notifier: add net ::ffff:0.0.0.0: gateway ::1: route already in table
Feb 25 16:25:06 freenas notifier: route: writing to routing socket: File exists
Feb 25 16:25:06 freenas notifier: add net ::0.0.0.0: gateway ::1: route already in table
Feb 25 16:26:04 freenas notifier: devd already running? (pid=1119).
Feb 25 16:26:04 freenas notifier: Setting hostuuid: 4c4c4544-0051-5610-8030-c3c04f515731.
Feb 25 16:26:04 freenas notifier: Setting hostid: 0xb65d682f.
Feb 25 16:26:04 freenas notifier: Starting Network: lo0 igb0 igb1.
Feb 25 16:26:04 freenas notifier: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
Feb 25 16:26:04 freenas notifier: options=3<RXCSUM,TXCSUM>
Feb 25 16:26:04 freenas notifier: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
Feb 25 16:26:04 freenas notifier: inet6 ::1 prefixlen 128
Feb 25 16:26:04 freenas notifier: inet 127.0.0.1 netmask 0xff000000
Feb 25 16:26:04 freenas notifier: nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
Feb 25 16:26:04 freenas notifier: igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
Feb 25 16:26:04 freenas notifier: options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
Feb 25 16:26:04 freenas notifier: ether a0:36:9f:06:8b:1e
Feb 25 16:26:04 freenas notifier: inet 10.1.1.96 netmask 0xffffff00 broadcast 10.1.1.255
Feb 25 16:26:04 freenas notifier: media: Ethernet autoselect (1000baseT <full-duplex>)
Feb 25 16:26:04 freenas notifier: status: active
Feb 25 16:26:04 freenas notifier: igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
Feb 25 16:26:04 freenas notifier: options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
Feb 25 16:26:04 freenas notifier: ether a0:36:9f:06:8b:1f
Feb 25 16:26:04 freenas notifier: inet 10.1.1.91 netmask 0xffffff00 broadcast 10.1.1.255
Feb 25 16:26:04 freenas notifier: media: Ethernet autoselect (1000baseT <full-duplex>)
Feb 25 16:26:04 freenas notifier: status: active
Feb 25 16:26:05 freenas root: /etc/rc.d/dhclient: ERROR: /etc/rc.d/dhclient: no interface specified
Feb 25 16:26:05 freenas notifier: /etc/rc.d/dhclient: ERROR: /etc/rc.d/dhclient: no interface specified
Feb 25 16:26:05 freenas notifier: route: writing to routing socket: File exists
Feb 25 16:26:05 freenas notifier: add net ::ffff:0.0.0.0: gateway ::1: route already in table
Feb 25 16:26:05 freenas notifier: route: writing to routing socket: File exists
Feb 25 16:26:05 freenas notifier: add net ::0.0.0.0: gateway ::1: route already in table
We're going to implement the system tunable recommended here and see if that sorts it out:
http://support.freenas.org/ticket/1729
I'll report back my findings in a day or two.