monitoring - fail2ban stop working ambigiously -
its has been 3 months since monitoring. , nature of fail2ban observe stop blocking ips after few days of busy schedule. use restart , again start working, blocking ip. few months things goes way after few months, fail2ban not block ip after restarting. have fresh installation of fail2ban , again start blocking.
can tell reason such nature of fail2ban?
is hard know happening withou config file or log. anyway, kind of behavior can because of clock sync problem.
i don't know if structure be: 1 machine generating logs of services , other machine fail2ban reading , banning. or host machine fail2ban , services in docker containers. in these case of scenarios, date should sync, includes timezone. maybe after restarting server synchronizing clock , changing date... don't know. possibility.
Comments
Post a Comment