Re: random system crashes

----- Original Message -----
From: "Matthew Hodgson" <[email protected]>
To: <[email protected]>
Sent: Saturday, October 19, 2002 12:08 AM
Subject: Re: random system crashes


> Well, this certainly ties in with my experiences - can anyone on the list
> admit to actually running a stable yet busy (>30 hits/sec) server whilst
> logging is enabled?  Is there any correlation with the setting of
> log_incomplete?  It's obviously also possible that Alex's rm -f
/var/log/tux
> cron job is more to blame for his hangs than the actual act of logging in
> the first place.
>
> If such a straightforward setup does cause the bug, it seems strange that
> the developer(s) didn't at least notice problem during dev - and also that
> the problem has remained completely unaddressed on the list until so
> recently.

this probably explains why there are only about 500 servers reported using
tux on  netcraft. too bad development is on hold . People, please try to
help us troubleshoot this and determine what is the cause of the problem -
give us more real life tests and experiences, i already done my tests, but
we need to confirm this with other systems ...

the developer probably didn't notice that because logging is disabled by
default, and for benchmark perposes logging is usually turned off ...

> M.
>
> ----- Original Message -----
> From: "Alex Kramarov" <[email protected]>
> To: <[email protected]>
> Sent: Thursday, October 17, 2002 8:40 PM
> Subject: Re: random system crashes
>
>
> > Ok, the only thing i can say, that the entire logging of tux , with or
> without referrer, causes hangs. i have just started copying 200MB files
> between servers, like i do from time to time, and the server that had
> logging enabled on tux just hang on me in the middle of the copy - the
> regular sympthoms : pings work, no ssh access . It is probably related to
> disk activity along with the normal logging process - the only other
> possible explanation i have is that my server suddenly gone bad, and i
don't
> believe that. Well, just run tux without logging then, check if it's ok
now
> ...
> >
> >
> >
> > _______________________________________________
> > tux-list mailing list
> > [email protected]
> > https://listman.redhat.com/mailman/listinfo/tux-list
> >
> >
>
>
>
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/tux-list
>