No logins after several days 2006-02-15 - By Paul N
Back
I know you've shot this down already, but seriously, audit.d makes
some weird issues. If your /var directory is above 80% full on a
default audit.d configuration, your system will hang - no logins
through ssh, the console, or anything, but your services will still
work fine.
Even if you don't have logging on for audit.d, if you have audit.d
running and the partition /var is on hits 80%, you will have no
ability.
That said, you are definitely NOT running audit.d, and the partition
var is on is definitely NOT above 80%, right?
Sorry for the redundancy...
Paul
On 2/14/06, Jay Lee <jlee@(protected)> wrote:
> On Tue, February 14, 2006 5:49 pm, Thom Paine wrote:
> > Okay, I'm home finally and checked out the server.
> > The console is pretty much dead. I can't get a login prompt up, but I
> > can hit CTRL-ALT-F2 to get a new one. Typing in root and pressing enter
>
> Just to chime in, I had similar issues on a RHEL3 box configured for
> squid. Removing the laus rpm fixed the problem for me. just stoppindg
> auditd would probably do it to. Looking at /var/log/auditd/ an extreme
> amount of info was being logged...
>
> Jay
> --
> Jay Lee
> Network / Systems Administrator
> Information Technology Dept.
> Philadelphia Biblical University
> --
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> https://www.redhat.com/mailman/listinfo/taroon-list
>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
