I was having very similar problems with a squid box running everything
from 2.2.14 to 2.2.15pre15.
After I recompiled the kernel with gcc-2.7.2 instead of the egcs-1.1.2
that came with Redhat-6.1 the problem has vanished.
I'm interested to see if other people have the same experience.
Robert
>
> help 2.2.x + apache stabilty & lockups, ok in 2.0.36
>
> To: linux-kernel@vger.rutgers.edu
> Subject: help 2.2.x + apache stabilty & lockups, ok in 2.0.36
> From: <apmail@test.internettrash.com>
> Date: Sun, 16 Apr 2000 14:31:32 -0400 (EDT)
> Sender: owner-linux-kernel@vger.rutgers.edu
>
> Hi,
>
> I saw the following previous postings from a few months ago below
> regarding frequent lockups in 2.2.x and fine months of uptime in 2.0.36
> and i have an almost identical problems as the thread below.
>
> Ive had an almost identical situation as below. back in late january
> upgraded to 2.2.12 from 2.0.36 and have had identical total lockup
> scenarioes as below... where they were once running smoothly for 6
> months
> or more at a time. now for the past 2 months ive been tryin to figure
> out
> what the problem is, as they can barely stay up for more then a week at
> a
> time or 2 at a time.
>
> this is on 2 seperate web servers, one about 15 months old(scsi, upgrade
> from 2.0.36), and one brand new(ide only) (fresh 2.2.12) ive tried &
> installed
> the latest kernels up to 2.2.15pre17 and still the same total lockup
> behavior, no messages on the screen or logs. i tried swapping network
> cards a couple of times to different manufacturers & drivers which didnt
> help. so far ive used tulip, realtek, and now eepro100, no fix.
> My only option now, per my isp suggstion is to install 'watchdog' cards,
> so that the machine will reboot by itself. which seems like a poor
> solution to fix the instability and lockups. though ill do it anyways,
> otherwise ill go nuts its extremely frustrating. not to mention the
> hours
> of downtime when it locks in the middle of the night.
>
> these are moderately busy webservers one runs about 120 apache
> simultaneous daemons, and the other about 200, serving mostly static
> content. these are raw webservers with no X running, no sound, no fancy
> cards, etc.
>
> Was anyone ever able to resolve the problems below?
>
> Below is a thread of an almost identical situtation...
>
> Thanks,
> Rob
> ------------------------------------------------------
> Author: Ward Vandewege <ward.vandewege@pandora.be>
>
> << previous in thread next in thread >>
>
> At 01:53 AM 12/19/99 -0800, you 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.
>
> I am having a similar problem with a relatively high volume webserver
> running Apache. It used to run RedHat 4.x, on a HP Kayak workstation (I
> know, it was not my decision), and was stable as a rock. Then we
> upgraded
> the machine to RH 6.0, and then RH6.1, with kernels from 2.2.5 to
> 2.2.13.
> The machine crashes irregularly - sometimes it stays up for 3 days,
> sometimes it crashes 3 times a day. Nothing in the logs, no oops,
> nothing
> on the console. We replaced the webserver by Mathopd, which gave
> slightly
> higher uptimes, but the machine kept on crashing. We replaced nics, and
> eventually replaced the hardware to a HP Netserver 60, but nothing
> helped.
> We now separated the mail/ftp service from the web service, with the
> former running on the new box. This setup is very stable: the current
> uptime is 64 days, and it gets 60000 POP logins daily (the ftp service
> is
> less important). I re-installed the old box (the HP Kayak) with a fresh
> RH6.1, installed Apache 1.3.9, using the machine as the webserver
> _only_,
> and the crashing continues. The machine is behind a FW-1 on NT (I have
> no
> control over that one :-( ), but that machine does not proxy for the web
> server.
>
> I'm stuck. Any ideas/suggestions??
>
> Ward.
-- Robert Cohen - Network Administrator Apex Internet robert@apex.net.au http://www.apex.net.au Ph (02) 6247 2000 Fax: (02) 6247 2711- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:09 EST