[cobalt-users] RaQ4i - New Error After Apache Update

[Scott F <scott_falco@xxxxxxxxx>]

Hi All,

Over the weekend I installed the latest Apache update
to one of our RaQ4i's as well as the SNMP Update found
on the "unofficial" update site -
http://pkg.nl.cobalt.com/packages/raq/4/. The
following night at around 5AM, I logged in to find log
rotation stuck and pegging the CPU to the ceiling. No
matter WHAT I tried, I couldn't kill off the
processes, so I ended up rebooting the machine. Once
back-up, I went in and zeroed the logs and then ran
log rotate from command line just to ease my fears
which seemed to go off without a hitch (like it
wouldn't since I had just zeroed the logs for it). The
following night/morning, I checked back on the server
at 5AM, and it was dead in the water. It took
RackShack the next 24 hours (literally) to pull and
restore the box. Luckily, this box is mostly for play,
and testing (sad when you have to lease a spare just
to test updates on, but RS has some good prices). So
since there were no additional software on the box
except for Cobalt updates/patches (with the exception
of the one SNMP Update), this was obviously directly
related. The guys at RS told me that (and I quote)
"There's been problems with the Apache update. It's
brought down a number of servers." I figured, since I
didn't run ASP or PHP on the box, nor had I tried to
update ASP to 3.6 which I read was causing problems,
I'd go ahead and try the Apache update since it had
been around for 3 weeks or so.

Soooo.... Once the box was wiped and the OS replaced,
I thought I'd try it again, *thinking* the problem
might be related to the SNMP update I installed the
same night as the Apache update.. So I went up the
list and installed all the patches on a fresh box. The
good news is that the box is still up and running, but
again, it has no domain's on it so it's not like it's
under any kind of stress. --BUT-- I have started
noticing the following error in my logs:

modprobe: can't locate module char-major-4

Upon checking the archives, I can see that within the
last week someone else is complaining about the same. 

http://list.cobalt.com/pipermail/cobalt-users/2001-August/051395.html

I can only assume it has to be the Apache update. But
someone else pointed out a possible fix, but I've yet
to mess with it (really tired of going in and fixing
this stuff after updates) -

http://list.cobalt.com/pipermail/cobalt-users/2001-April/040610.html

So just FYI - that's my experiences with the update
and I'm sticking to it (or should I say it stuck it to
me)!

Cheers!
Scott

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com