Christophe1
Verified User
Hi all
On a recently installed, pretty standard and up-to-date directadmin server, the brute force monitor suddenly stopped working after accidentally installing fail2ban (misunderstanding with colleague).
As if the logs are no longer been read. Meanwhile, fail2ban is removed again.
The instructions on http://help.directadmin.com/item.php?id=380 were followed and originally all this worked perfect.
Manually blocking an IP from the Brute Force Monitor that was detected earlier, still works.
The dataskq is still running.
When deleting /usr/local/directadmin/data/admin/brute.conf (after backup), no new file is created.
When deleting /usr/local/directadmin/data/admin/brute.conf.lock (after backup), a new file is created.
According to directadmin.conf, the brute force monitor should be active.
Any help would be particularly appreciated...
On a recently installed, pretty standard and up-to-date directadmin server, the brute force monitor suddenly stopped working after accidentally installing fail2ban (misunderstanding with colleague).
As if the logs are no longer been read. Meanwhile, fail2ban is removed again.
The instructions on http://help.directadmin.com/item.php?id=380 were followed and originally all this worked perfect.
Manually blocking an IP from the Brute Force Monitor that was detected earlier, still works.
The dataskq is still running.
When deleting /usr/local/directadmin/data/admin/brute.conf (after backup), no new file is created.
When deleting /usr/local/directadmin/data/admin/brute.conf.lock (after backup), a new file is created.
According to directadmin.conf, the brute force monitor should be active.
Any help would be particularly appreciated...