Your message dated Tue, 22 Sep 2026 08:26:07 +0000
with message-id <[email protected]>
and subject line Bug#895342: fixed in suricata 1:8.0.7-2~exp1
has caused the Debian Bug report #895342,
regarding suricata: new version fails to start if eth0 not present
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: suricata
Version: 1:4.0.4-1
Severity: serious
User: [email protected]
Usertags: origin-ubuntu bionic autopkgtest
Dear maintainers,
The latest version of suricata is failing its autopkgtests in Ubuntu because
the suricata daemon does not start in the test environment. This appears to
be due to the fact that the default suricata config assumes eth0 as an
interface name, but the testbed has ens2 as its default interface:
# /usr/bin/suricata --af-packet -c /etc/suricata/suricata.yaml --pidfile
/var/run/suricata.pid
10/4/2018 -- 05:31:56 - <Notice> - This is Suricata version 4.0.4 RELEASE
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure
when trying to get MTU via ioctl for 'eth0': No such device (19)
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_SYSCALL(50)] - Failure
when trying to get MTU via ioctl for 'eth0': No such device (19)
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/botcc.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/ciarmy.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/compromised.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/drop.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/dshield.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-attack_response.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-chat.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-current_events.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-dns.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-dos.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-exploit.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-ftp.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-imap.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-malware.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-misc.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-mobile_malware.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-netbios.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-p2p.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-policy.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-pop3.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-rpc.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-scan.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-smtp.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-snmp.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-sql.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-telnet.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-tftp.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-trojan.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-user_agents.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-voip.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-web_client.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-web_server.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/emerging-worm.rules
10/4/2018 -- 05:31:56 - <Warning> - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule
files match the pattern /etc/suricata/rules/tor.rules
10/4/2018 -- 05:31:56 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to
find type for iface "eth0": No such device
10/4/2018 -- 05:31:56 - <Notice> - all 1 packet processing threads, 4
management threads initialized, engine started.
10/4/2018 -- 05:31:56 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Unable to
find iface eth0: No such device
10/4/2018 -- 05:31:56 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Couldn't
init AF_PACKET socket, fatal error
10/4/2018 -- 05:31:56 - <Error> - [ERRCODE: SC_ERR_FATAL(171)] - thread
W#01-eth0 failed
#
Previous versions of suricata also had a default interface name of eth0
configured, but this was not a fatal error; the suricata daemon still
started and the tests could be run.
I'm filing this as serious because it seems to me that neither of these
behaviors - either starting up and being ineffective because it's running on
the wrong interface, or failing to start up because the interface is
hard-coded and not present - is a reasonable default behavior for an IDS. I
think the interface should either be autodetected or prompted for at install
time.
Feel free to downgrade if you disagree.
In any case, while the autopkgtests do not pass, the new version of suricata
will not be included in the Ubuntu release, as regressing autopkgtests are
considered release blockers there.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: suricata
Source-Version: 1:8.0.7-2~exp1
Done: Andreas Dolp <[email protected]>
We believe that the bug you reported is fixed in the latest version of
suricata, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Dolp <[email protected]> (supplier of updated suricata package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 22 Sep 2026 09:41:20 +0200
Source: suricata
Architecture: source
Version: 1:8.0.7-2~exp1
Distribution: experimental
Urgency: medium
Maintainer: Sascha Steinbiss <[email protected]>
Changed-By: Andreas Dolp <[email protected]>
Closes: 895342
Changes:
suricata (1:8.0.7-2~exp1) experimental; urgency=medium
.
* Update changelog for 1:8.0.7-2~exp1 release
* d/t/unix-socket-test.sh: Add unix-socket-test.sh, which starts its own
Suricata instance for unix socket tests instead of silently relying on
hardcoded interface names from suricata.yaml.
* d/t/systemd-service-test.sh: Improve tests by:
* detecting a capture interface that exists in the testbed,
* keeping the shipped suricata.yaml,
* waiting for the systemd service state instead of sleeping,
* re-enabling the reload test and
* testing the suricatasc commands that need a live capture instance.
* d/t/control: Set explicit test names for the remaining tests.
* d/t/control: Remove unnecessary test dependencies for unit tests.
* Do not enable the Suricata systemd service on first installations because
it fails on all systems without an 'eth0' interface.
Add a test to d/t/systemd-service-test.sh to verify the stopped service.
Closes: #895342
Checksums-Sha1:
b9404312c5760ec5f05247e342ef437c52b73e3d 2511 suricata_8.0.7-2~exp1.dsc
83481e95cde5452794fe0ef1b549c52c64370ffd 26992
suricata_8.0.7-2~exp1.debian.tar.xz
a9645e7e7fa904635b89d2a718ec941582082560 17197
suricata_8.0.7-2~exp1_arm64.buildinfo
Checksums-Sha256:
be7eae18cec702d3fdc036eff00538d42076088cbf6b1ad51c6cb883355f0a5e 2511
suricata_8.0.7-2~exp1.dsc
5d5896c2477d7748208c81dedeea0229ade382ce17142c0b78d163cae86662e9 26992
suricata_8.0.7-2~exp1.debian.tar.xz
72faf3f03e8ba4e523295c816d73e70feaa9a72c86d8c33b6a1cf3954d497e75 17197
suricata_8.0.7-2~exp1_arm64.buildinfo
Files:
83ac89649d94a9dcdf02edba10606c8f 2511 net optional suricata_8.0.7-2~exp1.dsc
e7244eacd8e7ade98119fa2bbf5de1e5 26992 net optional
suricata_8.0.7-2~exp1.debian.tar.xz
d7ea7c5e648503f25e9222cf98fca769 17197 net optional
suricata_8.0.7-2~exp1_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQTjqpLKhithiGov9EruqOTPfpjPmQUCarIzFgAKCRDuqOTPfpjP
mXpgAPsEKmr6rK2mOU1CHqQfOFRxJjUpzLwjw3mNQpeukdY4sgEAghPLruKe93M2
09nONMYUR2S/4622IDac/klCFPiFHgU=
=5g+o
-----END PGP SIGNATURE-----
pgpXRNSrDu7AG.pgp
Description: PGP signature
--- End Message ---
