Security run output explanation

[Rilo Ravestein]

I wonder what some of the lines in the security emails i am getting mean. I was hoping someone here was able to explain a bit or point me in the right direction. I'm not having issues, everything seems to work fine, just want to learn a bit.

nas.local kernel log messages:
> arp: 192.168.2.100 moved from 02:b7:56:00:09:0a to 0c:c4:7a:09:bf:44 on epair0b
> arp: 192.168.2.100 moved from 02:b7:56:00:09:0a to 0c:c4:7a:09:bf:44 on epair0b
> arp: 192.168.2.100 moved from 02:b7:56:00:09:0a to 0c:c4:7a:09:bf:44 on epair0b
> epair2a: Ethernet address: 02:e6:a9:00:0b:0a
> epair2b: Ethernet address: 02:e6:a9:00:0c:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled (read some here, but don't know why used in FreeNAS)
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (80 items). Lost 8 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items). Lost 6 pages of memory.
> Freed UMA keg (tcpreass) was not empty (1092 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (400 items). Lost 8 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (120 items). Lost 12 pages of memory.
> Freed UMA keg (tcpcb) was not empty (48 items). Lost 12 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair2a: Ethernet address: 02:10:7c:00:0b:0a
> epair2b: Ethernet address: 02:10:7c:00:0c:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> arp: 192.168.2.100 moved from 02:b7:56:00:09:0a to 0c:c4:7a:09:bf:44 on epair0b
> epair2a: Ethernet address: 02:83:25:00:0b:0a
> epair2b: Ethernet address: 02:83:25:00:0c:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (70 items). Lost 7 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items). Lost 6 pages of memory.
> Freed UMA keg (tcptw) was not empty (400 items). Lost 8 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (90 items). Lost 9 pages of memory.
> Freed UMA keg (tcpcb) was not empty (48 items). Lost 12 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (60 items). Lost 6 pages of memory.
> Freed UMA keg (udpcb) was not empty (840 items). Lost 5 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair2a: Ethernet address: 02:48:ef:00:0b:0a
> epair2b: Ethernet address: 02:48:ef:00:0c:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> nfsd: can't register svc name

 

[Rilo Ravestein]

Isthere nobody around here who knows what this all means? :(

 

[depasseg]

arp - just means a different MAC address has that IP address.
the epair stuff is the bridging for the jails and promiscuous mode allows the jails to have full access to the network.
nfsd is the NFS service.

I'm not exactly sure what the others mean.

And don't get too concerned. While it's called the security output, I think it is just a list of the system log listing any changes.

 

[Rilo Ravestein]

Thanks for the info. I'm not concerned, just want to learn.

arp: why is another MAC address given that ip address? Does this got to do with LACP?
epair: why does the link status go up and down?
nfsd is the NFS server, i know, but why can't it register the svc name (service name i guess)?

 

[depasseg]

For arp - DHCP changes, and possibly LACP could be the reason.

Don't know the rest. My guess would be the jails restarting, but it's just a guess.

I don't know enough about nfs. If it were me, I'd start with google.

 

[Rilo Ravestein]

For arp - DHCP changes, and possibly LACP could be the reason.

Now i am confused. I don't use DHCP. Only static addressed configured.

 

[SwampRabbit]

Two of those lines are the same as this old bug that was resolved.
https://bugs.freenas.org/issues/6281

Are you running the latest 9.3?
Just a possibility.

 

[Rilo Ravestein]

I read the issue, and I do sometimes have to force shutdown to get a reboot. I only do a reboot after upgrading, and I don't remember if this happened the last time. I'm running the latest stable version.

But as I mentioned, I do not experience any issues.
Wel... besides the fact that that not transfer is slow from/to my Linux laptop. Don't know if that has anything to do with these messages.

I just like to know what all this info in the emails means

 

[diskdiddler]

<SNIP>
> Freed UMA keg (udp_inpcb) was not empty (80 items). Lost 8 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items). Lost 6 pages of memory.
> Freed UMA keg (tcpreass) was not empty (1092 items). Lost 13 pages of memory.
> Freed UMA keg (tcptw) was not empty (400 items). Lost 8 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (120 items). Lost 12 pages of memory.
> Freed UMA keg (tcpcb) was not empty (48 items). Lost 12 pages of memory.
<SNIP>

This one sounds bad, I'm seeing similar stuff. Just went to 9.3 last night.

Feb 18 17:15:03 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 18 17:15:03 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 18 17:15:05 freenas epair5a: Ethernet address: 02:e2:70:00:10:0a
Feb 18 17:15:05 freenas epair5b: Ethernet address: 02:e2:70:00:11:0b
Feb 18 17:15:05 freenas kernel: epair5a: link state changed to UP
Feb 18 17:15:05 freenas kernel: epair5a: link state changed to UP
Feb 18 17:15:05 freenas kernel: epair5b: link state changed to UP
Feb 18 17:15:05 freenas kernel: epair5b: link state changed to UP
Feb 18 17:15:05 freenas kernel: epair5a: promiscuous mode enabled
Feb 18 17:15:05 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:15:05 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:16:18 freenas kernel: epair5a: link state changed to DOWN
Feb 18 17:16:18 freenas kernel: epair5a: link state changed to DOWN
Feb 18 17:16:18 freenas kernel: epair5b: link state changed to DOWN
Feb 18 17:16:18 freenas kernel: epair5b: link state changed to DOWN
Feb 18 17:16:32 freenas notifier: Performing sanity check on nginx configuration:
Feb 18 17:16:32 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 18 17:16:32 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 18 17:16:33 freenas epair5a: Ethernet address: 02:3b:92:00:10:0a
Feb 18 17:16:33 freenas epair5b: Ethernet address: 02:3b:92:00:11:0b
Feb 18 17:16:33 freenas kernel: epair5a: link state changed to UP
Feb 18 17:16:33 freenas kernel: epair5a: link state changed to UP
Feb 18 17:16:33 freenas kernel: epair5b: link state changed to UP
Feb 18 17:16:33 freenas kernel: epair5b: link state changed to UP
Feb 18 17:16:33 freenas kernel: epair5a: promiscuous mode enabled
Feb 18 17:16:33 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:16:33 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:20:36 freenas kernel: ifa_del_loopback_route: deletion failed
Feb 18 17:20:36 freenas Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Feb 18 17:20:36 freenas Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.
Feb 18 17:20:36 freenas Freed UMA keg (tcptw) was not empty (100 items). Lost 2 pages of memory.
Feb 18 17:20:36 freenas Freed UMA keg (tcp_inpcb) was not empty (40 items). Lost 4 pages of memory.
Feb 18 17:20:36 freenas Freed UMA keg (tcpcb) was not empty (28 items). Lost 7 pages of memory.
Feb 18 17:20:36 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Feb 18 17:20:36 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Feb 18 17:22:33 freenas kernel: ifa_del_loopback_route: deletion failed
Feb 18 17:22:33 freenas Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Feb 18 17:22:33 freenas Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.
Feb 18 17:22:33 freenas Freed UMA keg (tcptw) was not empty (100 items). Lost 2 pages of memory.
Feb 18 17:22:33 freenas Freed UMA keg (tcp_inpcb) was not empty (30 items). Lost 3 pages of memory.
Feb 18 17:22:33 freenas Freed UMA keg (tcpcb) was not empty (20 items). Lost 5 pages of memory.
Feb 18 17:22:33 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Feb 18 17:22:33 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Feb 18 17:24:04 freenas kernel: epair5a: link state changed to DOWN
Feb 18 17:24:04 freenas kernel: epair5a: link state changed to DOWN
Feb 18 17:24:04 freenas kernel: epair5b: link state changed to DOWN
Feb 18 17:24:04 freenas kernel: epair5b: link state changed to DOWN
Feb 18 17:24:53 freenas notifier: Performing sanity check on nginx configuration:
Feb 18 17:24:53 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 18 17:24:53 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 18 17:24:53 freenas epair5a: Ethernet address: 02:c0:c3:00:10:0a
Feb 18 17:24:53 freenas epair5b: Ethernet address: 02:c0:c3:00:11:0b
Feb 18 17:24:53 freenas kernel: epair5a: link state changed to UP
Feb 18 17:24:53 freenas kernel: epair5a: link state changed to UP
Feb 18 17:24:53 freenas kernel: epair5b: link state changed to UP
Feb 18 17:24:53 freenas kernel: epair5b: link state changed to UP
Feb 18 17:24:53 freenas kernel: epair5a: promiscuous mode enabled
Feb 18 17:24:53 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:24:53 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Feb 18 17:25:25 freenas kernel: ifa_del_loopback_route: deletion failed
Feb 18 17:25:25 freenas Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Feb 18 17:25:25 freenas Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.
Feb 18 17:25:25 freenas Freed UMA keg (tcptw) was not empty (100 items). Lost 2 pages of memory.
Feb 18 17:25:25 freenas Freed UMA keg (tcp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Feb 18 17:25:25 freenas Freed UMA keg (tcpcb) was not empty (12 items). Lost 3 pages of memory.
Feb 18 17:25:25 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Feb 18 17:25:25 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

 

[Rilo Ravestein]

Not bad at all, according to this thread.