mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-08-20 22:48:21 +02:00
Josh Patterson
a337a3e4f6
LogExpireInterval, StatsLogExpireInterval and CrashExpireInterval are only acted on by "zeekctl cron", which nothing in the grid ran, so setting them in SOC did nothing. Add so-zeek-cron and run it every 5 minutes, the interval upstream recommends. This also restarts a node that died unexpectedly and marks it crashed so a crash report is written, which is what CrashExpireInterval then reaps. The crontab runs as root because the script needs the docker socket; it drops to the zeek user inside the container so the stats logs and zeekctl-config.sh it writes stay owned by uid 937. Annotate the five zeekctl settings that were previously undocumented. The regex on LogExpireInterval matters: a bare number means days, and a value shorter than LogRotationInterval raises ConfigurationError, which fails the zeekctl deploy in the container entrypoint. Zeek then never starts while Salt still reports success and the container still reports healthy. Excluding the min unit keeps that unreachable at the default 3600 second rotation interval. MinDiskSpace and MailHostUpDown only send mail and the image has no sendmail, so their descriptions say they currently have no effect.