DrKK
FreeNAS Generalissimo
- Joined
- Oct 15, 2013
- Messages
- 3,630
Just saw this in my footer:
I think the epair0b stuff is just some kind of b.s. that I get because I'm in a virtual testbed. But I don't like the syslog-ng coredump there at the bottom.
What do you guys think? What kind of investigation can I do to assist if it's important?
Code:
Nov 10 23:30:18 freenasbeta kernel: epair0a: link state changed to UP Nov 10 23:30:18 freenasbeta kernel: epair0a: link state changed to UP Nov 10 23:30:18 freenasbeta kernel: epair0b: link state changed to UP Nov 10 23:30:18 freenasbeta kernel: epair0b: link state changed to UP Nov 10 23:30:18 freenasbeta kernel: epair0a: promiscuous mode enabled Nov 10 23:30:19 freenasbeta kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Nov 10 23:30:19 freenasbeta kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Nov 10 23:30:50 freenasbeta smbd[4990]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host na me/name mismatch: 192.168.159.1 != (NULL) Nov 10 23:30:51 freenasbeta syslog-ng[4991]: syslog-ng starting up; version='3.5.6' Nov 10 23:30:51 freenasbeta kernel: pid 1541 (syslog-ng), uid 0: exited on signal 6 (core dumped) [root@freenasbeta] ~#
I think the epair0b stuff is just some kind of b.s. that I get because I'm in a virtual testbed. But I don't like the syslog-ng coredump there at the bottom.
What do you guys think? What kind of investigation can I do to assist if it's important?