Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Failed to connect to socket and send command /tmp/suricata-command.socket: [Errno 2] No such file or directory
See original GitHub issueSummary:
After running cape2.sh and trying both the base and suricata argument, the suricata processing module is still unable to find the socket file:
2020-09-22 17:54:34,334 [modules.processing.suricata] WARNING: Failed to connect to socket and send command /tmp/suricata-command.socket: [Errno 2] No such file or directory
Digging into /var/log/suricata/suricata.log I discovered:
<Error> - [ERRCODE: SC_ERR_UID_FAILED(155)] - unable to get the user ID, check if user exist!!
| Question | Answer |
|---|---|
| OS version | Ubuntu 20.04 |
| CAPEv2 Version | Latest |
| Suricata Service | SystemD |
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
thanks, my solution is simplier 😉
Noice. As far as that one liner goes for ensuring the crontab doesn’t exist, this works for me:
crontab -l 2>/dev/null | grep 'suricata-update' &>/dev/null || (crontab -l 2>/dev/null; echo "15 * * * * /usr/bin/suricata-update --suricata /usr/bin/suricata --suricata-conf /etc/suricata/suricata.yaml -o /etc/suricata/rules/ && /usr/bin/suricatasc -c reload-rules /tmp/suricata-command.socket &>/dev/null") | crontab -