You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that having sqlite in WAL mode is a must when using community-blocklist, which is adviced to be used with swag-crowdsec.
But the default configuration is not activating this option and triggers a warning:
time="18-12-2023 20:16:27" level=warning msg="sqlite is not using WAL mode, LAPI might become unresponsive when inserting the community blocklist"
time="18-12-2023 20:16:28" level=info msg="crowdsecurity/community-blocklist : added 15000 entries, deleted 11060 entries (alert:2)"
/etc/crowdsec/config.yaml, section db_config should be updated with use_wal: true. Maybe it should be configurable, if needed. But default config seems not to be the one which is advised in combination with community-blocklist, to my understanding.
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
It seems that having sqlite in WAL mode is a must when using community-blocklist, which is adviced to be used with swag-crowdsec.
But the default configuration is not activating this option and triggers a warning:
/etc/crowdsec/config.yaml
, sectiondb_config
should be updated withuse_wal: true
. Maybe it should be configurable, if needed. But default config seems not to be the one which is advised in combination with community-blocklist, to my understanding.Thanks
The text was updated successfully, but these errors were encountered: