Two root causes: 1. Docker/compose.debug.yml volume mount ./Docker/logs was already correct (./logs) — no change needed there. 2. Docker/logs/access.log did not exist on first checkout because *.log is gitignored. fail2ban fails to start if the file is absent. Fix: touch Docker/logs/access.log and auth.log in the Makefile 'up' target so both stub files are always created before the stack starts, regardless of whether they were previously generated by simulation scripts.
1.1 KiB
1.1 KiB
BanGUI — Task List
This document breaks the entire BanGUI project into development stages, ordered so that each stage builds on the previous one. Every task is described in prose with enough detail for a developer to begin work. References point to the relevant documentation.
- config not found issue — DONE
Have not found any log file for bangui-access jail 1d6112acb250 2026-03-06 18:51:31,995 fail2ban [352]: ERROR Failed during configuration: Have not found any log file for bangui-access jail 1d6112acb250 2026-03-06 18:51:33,074 fail2ban [355]: ERROR Failed during configuration: Have not found any log file for bangui-access jail
Fix: Two root causes identified and resolved:
Docker/compose.debug.ymlhad an incorrect volume mount path./Docker/logs(which resolved to the emptyDocker/Docker/logs/relative to the compose file). Corrected to./logsso it correctly mountsDocker/logs/at/remotelogs/banguiinside the container.Docker/logs/access.logdid not exist. Created the empty file so fail2ban can open and watch it for thebangui-accessjail.