2018-01-24T23:24:19 [INFO/event] libevent 2.1.8-stable initialized with epoll method 2018-01-24T23:24:19 [WARN/interfaces] cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted 2018-01-24T23:24:19 [WARN/seccomp] invalid syscall attempted: openat(257) 2018-01-24T23:24:19 [CRIT/seccomp] invalid syscall not allowed: stop here 2018-01-24T23:24:19 [WARN/lldpctl] unable to get configuration from lldpd. A failure occurred during callback processing 2018-01-24T23:24:19 [INFO/lldpctl] an error occurred while executing Looks like it's openat causing the problem. BTW: The warning is not really meaningful, what's GLINKSETTINGS and what requires 4.9+? While it says something about ethtool: ethtool --version ethtool version 4.13 Can't be the ethtool version.
(In reply to Sven E. from comment #0) > 2018-01-24T23:24:19 [INFO/event] libevent 2.1.8-stable initialized with > epoll method > 2018-01-24T23:24:19 [WARN/interfaces] cannot get ethtool link information > with GLINKSETTINGS (requires 4.9+): Operation not permitted > 2018-01-24T23:24:19 [WARN/seccomp] invalid syscall attempted: openat(257) > 2018-01-24T23:24:19 [CRIT/seccomp] invalid syscall not allowed: stop here > 2018-01-24T23:24:19 [WARN/lldpctl] unable to get configuration from lldpd. A > failure occurred during callback processing > 2018-01-24T23:24:19 [INFO/lldpctl] an error occurred while executing > > Looks like it's openat causing the problem. > > BTW: The warning is not really meaningful, what's GLINKSETTINGS and what > requires 4.9+? > > While it says something about ethtool: > ethtool --version > ethtool version 4.13 > > Can't be the ethtool version. Kernel version? If only you had posted your `emerge --info` output like you should, we might already know.
(In reply to Jeroen Roovers from comment #1) > (In reply to Sven E. from comment #0) > > 2018-01-24T23:24:19 [INFO/event] libevent 2.1.8-stable initialized with > > epoll method > > 2018-01-24T23:24:19 [WARN/interfaces] cannot get ethtool link information > > with GLINKSETTINGS (requires 4.9+): Operation not permitted > > 2018-01-24T23:24:19 [WARN/seccomp] invalid syscall attempted: openat(257) > > 2018-01-24T23:24:19 [CRIT/seccomp] invalid syscall not allowed: stop here > > 2018-01-24T23:24:19 [WARN/lldpctl] unable to get configuration from lldpd. A > > failure occurred during callback processing > > 2018-01-24T23:24:19 [INFO/lldpctl] an error occurred while executing > > > > Looks like it's openat causing the problem. > > > > BTW: The warning is not really meaningful, what's GLINKSETTINGS and what > > requires 4.9+? > > > > While it says something about ethtool: > > ethtool --version > > ethtool version 4.13 > > > > Can't be the ethtool version. > > Kernel version? If only you had posted your `emerge --info` output like you > should, we might already know. Digging into this ... Yes, 4.9+ seems to refer to the kernel version, however a meaningful error message would state that it tries to use GLINKSETTINGS which requires a 4.9+ kernel. Since the message talsk about ethtool the the word kernel is absolutely required for clarification. However, this is a warning and won't stop lldpd from working in general, as the warning is also displayed with -seccomp and lldpd starts up as expected. (And it seems to operate as expected as well) The seccomp issue is with the openat() call which will stop lldpd from starting up and working alltogether. So, adding openat to the list of acceptable calls should fix the startup error when compiled with +seccomp. And a clarified warning message will help to understand, that a new kernel version is expected for full functionality. This is more of a cosmetic nature, yet it should be done.
And as comparison, a startup under kernel 4.9: 2018-01-26T16:52:22 [INFO/main] protocol LLDP enabled 2018-01-26T16:52:22 [INFO/main] protocol CDPv1 disabled 2018-01-26T16:52:22 [INFO/main] protocol CDPv2 disabled 2018-01-26T16:52:22 [INFO/event] libevent 2.1.8-stable initialized with epoll method 2018-01-26T16:52:22 [WARN/seccomp] invalid syscall attempted: openat(257) 2018-01-26T16:52:22 [CRIT/seccomp] invalid syscall not allowed: stop here 2018-01-26T16:52:22 [WARN/lldpctl] unable to get configuration from lldpd. A failure occurred during callback processing 2018-01-26T16:52:22 [INFO/lldpctl] an error occurred while executing last command So as assumed, the warning about ethtool and 4.9+ refers to the kernel and is not fatal, while with +seccomp the openat() call is refused.
This should be fixed in net-misc/lldpd-0.9.9
