From: Kern S. <ke...@si...> - 2012-12-13 17:50:28
|
Hello Marc, Thanks for the tip. I already have a blocked.list that is automatically put into the IP tables. In this case, I didn't have the time to chase down the offending IP address. It turns out that it was probably a robot walking our git repo, so adding a simple robot exclusion has probably corrected the problem. Regards, Kern On 12/13/2012 04:55 PM, Marc Schiffbauer wrote: > Am Mittwoch, 12. Dezember 2012, 08:49:05 schrieb Kern Sibbald: >> Hello Dan, >> >> Thanks for the report. I shutdown Apache last night for about >> 6 hours because someone was saturating the CPU with some >> cgi requests. Taking Apache down for about 5 minutes didn't work, >> so I shut it down longer, and the problem "seems" to have gone >> away. > Hint: > Next time maybe you could use iptables to block that IP instead of shutting > down the whole service ;) > > iptables -I INPUT -s <source ip> -j DROP > > Using the recent module of iptables you can even automatically unblock that IP > after a defined time. > > -Marc > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel |