[SAC] trac VM in unhealthy state
tech_dev at wildintellect.com
Wed May 22 23:38:28 PDT 2013
On 05/22/2013 11:32 PM, Markus Neteler wrote:
> On Thu, May 23, 2013 at 8:22 AM, Alex Mandel <tech_dev at wildintellect.com> wrote:
>> On 05/22/2013 11:12 PM, Martin Spott wrote:
>>> On Thu, May 23, 2013 at 07:57:07AM +0200, Markus Neteler wrote:
>>>> Reboot happily?
>>> Definitely, a production system with a stuck CPU is almost always a
>>> good candidate for a reboot ;-)
>> Full restart completed.
>> Anyone have ideas about what caused the CPU spikes yesterday and today?
> # For current traffic, use
> nethogs eth0
> Then I'd suggest to install fail2ban or so:
> grep 'Failed password' auth.log auth.log.1 | wc -l
> zgrep 'Failed password' auth.log*.gz | wc -l
That option is fine with me, for some reason thought we had that in the
default, guess not. Go ahead and do it.
Anyone have an opinion Fail2ban, DenyHosts or SSHGuard?
More information about the Sac