Your message dated Mon, 15 May 2017 10:17:25 +0200
with message-id
<caoksjbhwjdh8ng_fs1cwrs7naxas8k7ebh6xnclk8_evauk...@mail.gmail.com>
and subject line closing bug, fixed in the archive
has caused the Debian Bug report #861732,
regarding suricata will not start at boot
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.)
--
861732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: suricata
Version: 3.2.1-1
Severity: important
Dear Maintainer,
maybe I am doing something wrong, but maybe this is a bug.
The problem is: Suricata will not start at boot.
This is what I did:
I installed the package. Then copied (as written in the doc)
/lib/systemd/system/suricata.service to /etc/systemd/system/suricata.service
and tested with
systemctl start suricata.service
"ps -aux | grep suricata" showed me the running process. But after reboot, the
process is not started automatically.
Then I edited /etc/default/suricata and edited RUN=yes.
Tested either with
systemctl start suricata.service
and
/etc/init.d/suricata start
worked both fine. But again: no process after reboot.
Dunno if it is really a bug, maybe a configuration problem? Anything, where I
should look in the logs, to see what happens? I checked syslog, but it did not
really help me.
Thanks for your help.
Best regards
Hans
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386
(i686)
Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages suricata depends on:
ii dpkg 1.18.23
ii libc6 2.24-10
ii libcap-ng0 0.7.7-3+b1
ii libgcrypt20 1.7.6-1
ii libgeoip1 1.6.9-4
ii libgnutls30 3.5.8-5
ii libhiredis0.13 0.13.3-2
ii libhtp-0.5.23-1 3.2.1-1
ii libhyperscan4 4.4.1-1
ii libjansson4 2.9-1
ii libluajit-5.1-2 2.0.4+dfsg-1+b1
ii libmagic1 1:5.29-3
ii libnet1 1.1.6+dfsg-3
ii libnetfilter-log1 1.0.1-1.1
ii libnetfilter-queue1 1.0.2-2
ii libnfnetlink0 1.0.1-3
ii libnspr4 2:4.12-6
ii libnss3 2:3.26.2-1
ii libpcap0.8 1.8.1-3
ii libpcre3 2:8.39-3
ii libprelude2 1.0.0-11.9
ii libyaml-0-2 0.1.7-2
ii lsb-base 9.20161125
ii python 2.7.13-2
pn python:any <none>
Versions of packages suricata recommends:
ii snort-rules-default 2.9.7.0-5
ii suricata-oinkmaster 3.2.1-1
Versions of packages suricata suggests:
ii libtcmalloc-minimal4 2.5-2.2
-- Configuration Files:
/etc/default/suricata changed:
RUN=yes
SURCONF=/etc/suricata/suricata.yaml
LISTENMODE=nfqueue
IFACE=wlan0
NFQUEUE=0
TCMALLOC="YES"
PIDFILE=/var/run/suricata.pid
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 3.2.1-1
This fixed code is already in the archive starting with suricata 3.2.1-1.
Closing the bug now.
--- End Message ---
