Roger Wilco
Explorer
- Joined
- Jul 17, 2014
- Messages
- 65
Hi,
I have a fresh (not updated from 9.2) 9.3. installation with one jail configured and during startup the following messages are logged (and also appear in the console):
First question:
Can anyone explain why some of the messages appear twice?
Second question:
What does
kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
mean? I've failed to find an answer so far...
Thanks and bye,
Roger
I have a fresh (not updated from 9.2) 9.3. installation with one jail configured and during startup the following messages are logged (and also appear in the console):
Code:
Jan 4 18:55:22 freenas01 bridge0: Ethernet address: 02:c2:e6:2b:47:00 Jan 4 18:55:22 freenas01 kernel: bridge0: link state changed to UP Jan 4 18:55:22 freenas01 kernel: bridge0: link state changed to UP Jan 4 18:55:22 freenas01 kernel: bge0: promiscuous mode enabled Jan 4 18:55:22 freenas01 epair0a: Ethernet address: 02:9b:d0:00:09:0a Jan 4 18:55:22 freenas01 epair0b: Ethernet address: 02:9b:d0:00:0a:0b Jan 4 18:55:22 freenas01 kernel: epair0a: link state changed to UP Jan 4 18:55:22 freenas01 kernel: epair0a: link state changed to UP Jan 4 18:55:22 freenas01 kernel: epair0b: link state changed to UP Jan 4 18:55:22 freenas01 kernel: epair0b: link state changed to UP Jan 4 18:55:22 freenas01 kernel: epair0a: promiscuous mode enabled Jan 4 18:55:22 freenas01 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Jan 4 18:55:22 freenas01 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
First question:
Can anyone explain why some of the messages appear twice?
Second question:
What does
kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
mean? I've failed to find an answer so far...
Thanks and bye,
Roger