[SLUG] Lock-ups, was "son of a dog"

From: Chuck Hast (wchast@gmail.com)
Date: Sat Jul 23 2005 - 08:58:37 EDT


Getting down to things more technical with regards to the brute force attempts
on the test box I have, changed the port number seems to have been the
present answer, I suppose that will be true until they find it. Then I
will change
it again...

One thing of note, the machine started 'hanging up' always about 11 pm. I
started looking at it and it appeared to be doing so when it was running
several cron jobs.

At the same time due to the inordinate amount of BF ssh activity the
auth.log grew to about 560K in size. I noticed that this appears to happen
when this log gets some size which I have not been able to determine yet
but it appears to be around 300K in size. As soon as logrotate rotates it
and starts a new log, the lockups stop happening. I had noticed this back
a couple of months ago, but did not link the two issues, but I noticed that
the logrotate started the new auth.log about the same time that the lockups
quite taking place.

Does anyone have any idea of as to why this would be happening? What
would cause the size of that log to lock the machine up?

-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:18:55 EDT