Suricata package fails to prune suricata.log
The suricata package does not prune suricata.log. As a result, suricata.log grows without bound eventually resulting in a PHP out of memory error when the log file is viewed through the UI.
I had to manually prune suricata.log after it had grown to approximately 450MB and crashed PHP.
This was previously resolved under Bug #8607 unfortunately with the recent updated to pfsense 2.5.0 this issue has returned.
I have set the priority of this to very high in hopes of receiving a temporary manual commands that can be used to resolve it at which point it can be lowered to normal.
See attached log file and compare against the bug in 8607 and you will notice the identical problem.
Updated by Viktor Gurov 3 months ago