Hacking attempt fixed with Fail2Ban, but high memory usage remains
We were regularly having apache silently crash for the last few days, and found that it was likely due to a vigorous hacking attempt on the site, which we have fixed by implementing Fail2Ban.
However we are unsure if we've fixed the apache crashing issue completely, initially the droplet was running at 1.1GB of free memory, this is now down to 165MB (apache had been crashing when the memory dipped to 70-84MB). We're concerned the site may crash again under these conditions.
In addition there appears to be 7 apache instances running simultaneously, which does not seem right.
Any guidance of suggestions would be very much appreciated.