Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? y
Have I searched the tickets before posting? y
Have I read the documentation before posting (which pages?)? y
Joomla! version: 2.5.11
PHP version: 5.3
MySQL version: 5.5
Host: (optional, but it helps us help you)
Admin Tools version: 2.5.5
Description of my issue:
we're using the auto-blocking tool for exceptions, because we were seeing an increased number of brute force login attempts. it has worked well in terms of identifying the exceptions and blocking the IP after repeated attempts.
however -- it appears that when it blocks IPs, or perhaps when it's processing the exception, it may not be closing the apache process correctly. during a few times when we had a large volume of hits, we found apache processes failing to close and would hit our max connection limit (they were getting stuck in CLOSE_WAIT which suggests the application is not closing them properly).
I can't definitively say that it's caused by AdminTools, but it seems that way. the problem arose once we implemented the auto-blocking; and we recently starting limiting access to the admin login via IP and the issue resolved -- suggesting something about the exception tracking and auto blocking was the culprit.
are there any known issues along these lines?
Have I read the related troubleshooter articles above before posting (which pages?)? y
Have I searched the tickets before posting? y
Have I read the documentation before posting (which pages?)? y
Joomla! version: 2.5.11
PHP version: 5.3
MySQL version: 5.5
Host: (optional, but it helps us help you)
Admin Tools version: 2.5.5
Description of my issue:
we're using the auto-blocking tool for exceptions, because we were seeing an increased number of brute force login attempts. it has worked well in terms of identifying the exceptions and blocking the IP after repeated attempts.
however -- it appears that when it blocks IPs, or perhaps when it's processing the exception, it may not be closing the apache process correctly. during a few times when we had a large volume of hits, we found apache processes failing to close and would hit our max connection limit (they were getting stuck in CLOSE_WAIT which suggests the application is not closing them properly).
I can't definitively say that it's caused by AdminTools, but it seems that way. the problem arose once we implemented the auto-blocking; and we recently starting limiting access to the admin login via IP and the issue resolved -- suggesting something about the exception tracking and auto blocking was the culprit.
are there any known issues along these lines?
