CMD_BRUTE_FORCE_MONITOR generates a timeout


Enter Your Query:
Use '%' for wildcards and quotes for "exact phrases"


Top Level » DirectAdmin

CMD_BRUTE_FORCE_MONITOR generates a timeoutLast Modified: Dec 17, 2012, 4:39 pm
If you get a timeout message similar to the one below when accessing the Brute Force Monitor (BMF) CMD_BRUTE_FORCE_MONITOR:

Your connection has timed out

Either your request was invalid or the program hasn't completed your request.
Please notify the server admin.

This is usually caused by an oversized file:

/usr/local/directadmin/data/admin/brute_log_entries.list

Check this file to see if it's large. If it is, you shrink it down, but only keeping the entries at the end of the file (end of the file has the newest entries).

cd /usr/local/directadmin/data/admin
mv brute_log_entries.list brute_log_entries.list.backup
tail -n 1000 brute_log_entries.list.backup > brute_log_entries.list
chown diradmin:diradmin brute_log_entries.list

Where you can increase or decrease the 1000 lines as needed.

Other possible affected file are the brute_user.data and brute_ip.data.  Of these 2 files, it's more likely the brute_user.data is causing the slowdown, because attacks typically happen on many Users from 1 IP address.  If you need to empty the brute_user.data file, type:

cd /usr/local/directadmin/data/admin
mv brute_user.data brute_user.data.backup
touch brute_user.data
chown diradmin:diradmin brute_user.data

We wouldn't recommend emptying the brute_ip.data because this is what counts the attacks per IP, and is what is used to determine if an IP should be blocked.
 
Related Helpfiles
I wish to have a block_ip.sh so I can block IPs through DirectAdmin
The dataskq is causing a high load: 100% cpu
Message System has too many messages - How to empty the list

© 2018 JBMC Software, Suite 173  3-11 Bellerose Drive, St Albert, AB  T8N 1P7  Canada.  Mon-Fri 9AM-5PM MST