Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 20682

Summary: after running the newest RH update CD things are broken on 20 servers.
Product: [Retired] Red Hat Linux Reporter: bmeyer <bmeyer>
Component: modutilsAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-11-11 18:49:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bmeyer 2000-11-11 18:49:42 UTC 
I recently ran ./install-updates on about 2 or so RH6.2 servers. After the 
rpm rpm was updates, each and every machine would just site while trying 
to upgrade 'kernel'
I would get three lines of:
kernel ####################
kernel ####################
kernel ####################
and system CPU would be abour 99%.
When I would (after an hour) kill the process, the screen would fill with 
*.so no found (where *=the name of the files which would fill several 
screen fulls)

issuing: rpm --rebuilddb would allow the next issuance of ./install-
updates to run to complettion.

Today, I rebooted one of the server after I physcilally moved it to a new 
rack. When it comes up I get an:
modprobe: modprobe: can't open dependencies file /lib/modules/2.2/14-
5.0/modules.dep.

This is correct as that direcotry no longer seems to exist. Oddly this 
server ran ever since the upgrade though I never did reboot. 
The only commonalities between all the servers is, They are all RH62 with 
the previous update CD being run on them, and they all have bastille-linux 
(wwwbastille-linux.org) haveing been run on them. (a security hardening 
script).
Comment 1 Bill Nottingham 2001-07-06 23:02:01 UTC 
This was a bug in the updates CD. It should *never* upgrade the kernel;
this has been fixed in more recent update CD cuts.