Currently Being ModeratedFeb 23, 2012 2:15 PM (in response to starion)
I get the feeling it has something to do with authenticating things in general. That's what fails when you open a terminal window, and when you try to authenticate anything in the system. When it asks for an administrator password and you enter it, it takes a couple of minutes to do anything.
Currently Being ModeratedFeb 23, 2012 2:41 PM (in response to starion)
Now I'm reasonably sure it has something to do with postfix. If I reboot the machine, then quickly launch the SA before the machine becomes unresponsive, I can turn off mail services, and the machine stays stable.
From there, I have no idea. Trying mailbfr on the permissions....
Currently Being ModeratedFeb 24, 2012 1:56 PM (in response to starion)
Well, here is the solution, as unbelievable as it sounds.
I narrowed the problem down to when the SA was set to receive incoming mail. If I left the mail server up and running, and unchecked the "allow incoming mail", the server was stable. Only when incoming mail was turned on would things get goofy.
That pretty much narrows it down to the smtpd process in postfix.
I copied the smtpd executable from another working server (same version) and replaced it on the problem server. Problem solved. The smtpd must have gotten corrupted during the spam attack. It was located:
Server has been running smoothly for 12 hours now after 4 days of up and down every 3 minutes.