Open techkid107 opened 7 years ago
What's the output of - systemctl status suricata
? and do you have the interface up?
Hi, please see the below output. The interface light is up but Im not sure if it is actually up
â— suricata.service - LSB: Next Generation IDS/IPS Loaded: loaded (/etc/init.d/suricata; generated; vendor preset: enabled) Active: active (exited) since Wed 2017-10-25 02:02:37 CDT; 6h ago Docs: man:systemd-sysv-generator(8) Process: 16250 ExecStop=/etc/init.d/suricata stop (code=exited, status=1/FAILURE) Process: 16258 ExecStart=/etc/init.d/suricata start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 7372) CGroup: /system.slice/suricata.service
Oct 25 02:02:37 SELKS systemd[1]: Starting LSB: Next Generation IDS/IPS... Oct 25 02:02:37 SELKS suricata[16258]: Starting suricata in IDS (af-packet) mode... done. Oct 25 02:02:37 SELKS systemd[1]: Started LSB: Next Generation IDS/IPS. root@SELKS:~#
ok - maybe a quick ifconfig
will show you if the interface is up.
Can you please share the output of :
/usr/bin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid --af-packet -v --user=logstash
The ifconfig isnt listing the interface. Might be that it doesnt have an IP address allocated since its only sniffing.
[22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:241)
(ConfYamlParse) -- Including configuration file /etc/suricata/selks4-addin.yaml. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'default-rule-path' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'rule-files' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'classification-file' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'reference-config-file' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'detect' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'default-log-dir' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'stats' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'outputs' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'logging' redefined. [22602] 25/10/2017 -- 08:57:51 - (conf-yaml-loader.c:265) (ConfYamlParse) -- Configuration node 'af-packet' redefined. [22602] 25/10/2017 -- 08:57:51 - (suricata.c:1109) (LogVersion) -- This is Suricata version 4.0.0-dev (rev b8428378) [22602] 25/10/2017 -- 08:57:51 - (util-cpu.c:171) (UtilCpuPrintSummary) -- CPUs/cores online: 4 [22602] 25/10/2017 -- 08:57:51 - (util-ioctl.c:107) (GetIfaceMTU) -- Found an MTU of 1500 for 'eno2' [22602] 25/10/2017 -- 08:57:51 - (util-ioctl.c:107) (GetIfaceMTU) -- Found an MTU of 1500 for 'eno2' [22602] 25/10/2017 -- 08:57:51 - (util-pidfile.c:129) (SCPidfileTestRunning) -- [ERRCODE: SC_ERR_INITIALIZATION(45)] - pid file '/var/run/suricata.pid' exists but appears stale. Make sure Suricata is not running and then remove /var/run/suricata.pid. Aborting!
ok. Remove the pid and do service restart -
rm /var/run/suricata.pid
systemctl restart suricata
I did that and it came up for about a minute then stopped working again.
ok. Lets try it in a different way:
rm /var/run/suricata.pid
/usr/bin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid --af-packet -vv --user=logstash
What would be the output?
Pevma, your rm pid instructions worked for me. The issue occured after setting up the NIC offloading, not sure if it was the cause, many a coincidence. Thanks for your help.
Hi Pevma,
I was using the new SELKS6 in ids mode.
After I'd decide to change to ips mode (I followed all steps from https://github.com/StamusNetworks/SELKS/wiki/Initial-Setup---Suricata-IPS) I got this same issue (RED Suricata)
Could you please help me?
Loaded: loaded (/etc/init.d/suricata; generated) Active: active (exited) since Thu 2021-03-18 11:27:38 PDT; 7s ago Docs: man:systemd-sysv-generator(8) Process: 2031 ExecStart=/etc/init.d/suricata start (code=exited, status=0/SUCCESS)
Mar 18 11:27:38 svips01 systemd[1]: Stopped LSB: Next Generation IDS/IPS. Mar 18 11:27:38 svips01 systemd[1]: Starting LSB: Next Generation IDS/IPS... Mar 18 11:27:38 svips01 suricata[2031]: Starting suricata in IDS (af-packet) mode... done. Mar 18 11:27:38 svips01 systemd[1]: Started LSB: Next Generation IDS/IPS.
about this output /usr/bin/suricata -c /etc/suricata/suricata.yaml --pidfile /var/run/suricata.pid --af-packet -v --user=logstash
I got it:
[2051] 18/3/2021 -- 11:29:39 - (conf-yaml-loader.c:265)
I did these steps: rm /var/run/suricata.pid systemctl restart suricata
And it came up for about a minute then stopped working again (RED suricata).
And also I tried the last different way.
and I got that:
[2119] 18/3/2021 -- 11:33:32 - (conf-yaml-loader.c:265)
I just finished setting up Selks but I am unable to view logs. Suricata on the dashboard appears red as if the service isnt working. I have already setup the IDS interface but I'm stuck.