Bug #3498
closedKeep reporting eth0 when it has been updated in configuration
Description
Dear all! After yum package manager installation and basic configuration of a 4.1.5 RELEASE in Centos 7.7.1908 I get the following error log output:
24/2/2020 -- 16:59:37 - <Notice> - This is Suricata version 4.1.5 RELEASE
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to find type for iface "eth0": No such device
24/2/2020 -- 16:59:51 - <Notice> - all 2 packet processing threads, 4 management threads initialized, engine started.
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to find iface eth0: No such device
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Couldn't init AF_PACKET socket, fatal error
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_FATAL(171)] - thread W#01-eth0 failed
The interface has been updated to the correct name however it keeps showing in log.
If the service is stopped and suricata launches with:
/usr/bin/suricata -c /etc/suricata/suricata.yaml --af-packet=enp7s0
it does not throw the same errors.
Files
Updated by Athanasios Viennas about 4 years ago
Athanasios Viennas wrote:
Dear all! After yum package manager installation and basic configuration of a 4.1.5 RELEASE in Centos 7.7.1908 I get the following error log output:
24/2/2020 -- 16:59:37 - <Notice> - This is Suricata version 4.1.5 RELEASE
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to find type for iface "eth0": No such device
24/2/2020 -- 16:59:51 - <Notice> - all 2 packet processing threads, 4 management threads initialized, engine started.
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to find iface eth0: No such device
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Couldn't init AF_PACKET socket, fatal error
24/2/2020 -- 16:59:51 - <Error> - [ERRCODE: SC_ERR_FATAL(171)] - thread W#01-eth0 failedThe interface has been updated to the correct name however it keeps showing in log.
If the service is stopped and suricata launches with:
/usr/bin/suricata -c /etc/suricata/suricata.yaml --af-packet=enp7s0
it does not throw the same errors.
As the effort pretty much goes on Version 5, I will try out reinstallation of latest stable, from source, this time! Please close this ticket!