Closed Bug 581266 Opened 14 years ago Closed 14 years ago

Update glibc on newer buildbot masters

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: bhearsum)

References

Details

(Whiteboard: [buildmasters])

In bug 532501 we upgraded the glibc rpm to glibc-2.5-42.el5_4.3 to fix python crashing under buildbot. We get glibc-2.5-12 from when cloning a new linux 32bit VM.

This fix is not on 
* production-master01
* production-master03
* test-master01
* test-master02

It is on
* production-master
* production-master02
* talos-master02

Buildbot just crashed out on test-master01 so I'm going to update there.
CentOS5 is now updating to 2.5-49.el5_5.2, so I've copied the following from production-master02:/var/cache/yum/updates/packages/
glibc-2.5-42.el5_4.3.i686.rpm        
glibc-common-2.5-42.el5_4.3.i386.rpm 
glibc-devel-2.5-42.el5_4.3.i386.rpm  
glibc-headers-2.5-42.el5_4.3.i386.rpm
to ~root on test-master01, then applied them with 
 rpm -U glibc-2.5-42.el5_4.3.i686.rpm glibc-common-2.5-42.el5_4.3.i386.rpm glibc-devel-2.5-42.el5_4.3.i386.rpm glibc-headers-2.5-42.el5_4.3.i386.rpm

Rebooted.
Summary: Update glibc on buildbot masters → Update glibc on newer buildbot masters
Whiteboard: [buildmasters]
I'll volunteer for this. Needs to happen during a downtime, though.
Assignee: nobody → bhearsum
Blocks: 581098
I've installed the upgraded glibc* packages on the masters now. Will reboot them at some point during the downtime window this morning.
Reboots were done this morning.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
I've restarted munin-node (service munin-node start) and fixed chkconfig (chkconfig --levels 2345 munin-node on) on pm01 and pm03; and verified the other masters in comment #0 are already OK.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.