Well, I must admit that I'm having better luck than you are.  I've got
a Sparc server with 90 days uptime presently on RH 6.0 and kernel 2.2.5.

I've got an AMD K6 box with RH 6.0 2.2.5 doing about 50 days now that is
my personal development box at home.  And I have a PIII with Mandrake 5.3
and kernel 2.2.10 as my workstation at work, again with about 60 days on
it.  My firewall is still back at 2.0.36 something because I've never felt
a need to upgrade something that works well as is.

Obviously, I've got scsi hardware on the Sparc and IDE on the PCs and any
mix of other hardware on these boxes.  The uptime is from the last major
upgrade to the system.  Only the K6 had to be rebooted once due to a lockup
that occured while playing MP3s while doing IDE disk to disk copies.

I'm curious as to why you're not having similar luck.  There has been a
question or two asked about SCSI reliability issues (the drivers).  Are
your servers all SCSI based?  All my PCs are IDE, the Sparc having the
only SCSI tower.

And again, it may be worth moving some of the troublesome boxes back
to RH 5.2 or equivalent and 2.0.x.  The next big jump will be when the 2.2.4
kernels come out anyway.  Much finer grained kernel locks for SMP, threads,
and such, Also memory mapped socket buffers.  (Cuts overhead of the socket
abstraction.)  The main advantage with the 2.2.x is some file system improvements
and more flexibility in firewalling.  Perhaps you just need to sit back
and wait a few more months before pounding your head against these issues.
I know a lot of flakey bug fixes seem to be going into the code with the
2.3.x stuff right now.  Maybe time will work on your side.

Good luck.

On Tue, Dec 21, 1999 at 10:53:02AM -0200, Alexandre Hautequest wrote:
> On Sun, 19 Dec 1999, David Edwards wrote:
> 
> >About 2 months ago, I moved all of my servers ( 15 of them) to the 2.2.x
> >kernels.  Some were clean installs of RH 6.0, some were upgrades to RH
> >5.2.  But all of these servers ran 2.0.35 and 2.0.36 with 100+ days of
> >uptime and were rock solid.  But since moving to the 2.2 kernels on the
> >same hardware, reliability and uptime sucks.  Seems like I can rarely get a
> >month of uptime with the 2.2 kernels, and I've tried everything from 2.2.5
> >to 2.2.14pre13.  The few oopses I've had have been traced back to buggy
> >hardware that has since been replaced.  But in most every case with the 2.2
> >kernels, the servers (mainly serving web pages)  run for a few days to a
> >week and then lock up completely.  Then it requires a power cycle to bring
> >it back to life.
> >
> >So I'm stumped.  When a system locks up I don't get any console messages or
> >anything in syslog.  Since all of these servers ran 2.0.x kernels and were
> >very stable for months, I'm inclined to think the hardware is fine.  So any
> >clues as to how I might track this down?  I'd hate to say it (flame jacket
> >on) but my NT and freeBSD boxes are putting Linux to shame in terms of
> >stability....
> 
> Why don't you try Slackware? I have some production machines, all for
> web and databases (oracle and sybase) and uptimes are about 120+ days...
> now they are going down to a update -- i'm changing all to slack 7.
> 
> Of course you will need to learn a bit, but knowledge is not too much :)
> 
> Cheers,
> 
> -- 
> Alexandre Hautequest - Linux User #116289
> "When I'm on the road, I'm indestructible. No one can stop me. But they
> try..."
> 
> O .br que n�o para de crescer:
> http://stats.distributed.net/rc5-64/psearch.php3?st=.br
> The .br that don't stop to grow up:
> http://stats.distributed.net/rc5-64/psearch.php3?st=.br


-- 
J. Scott Kasten

jsk AT tetracon-eng DOT net

"That wasn't an attack.  It was preemptive retaliation!"


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to