Closed Bug 509909 Opened 16 years ago Closed 15 years ago

php-pecl-memcache > 2.2.3-2.rhel5.i386 breaks sumo and mozillaservice stage

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
All
task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Assigned: oremj)

References

()

Details

fox2mike: stephend|TV: [Wed Aug 12 01:13:36 2009] [error] [client 10.2.81.4] PHP Fatal error: Class 'Memcache' not found in /data/www/support-stage.mozilla.com/webroot/lib/cache/memcachelib.php on line 39 Also, so is http://mozillaservice.stage.mozilla.com/: "Please check the Kohana documentation for information about the following error. system/libraries/drivers/Cache/Memcache.php [29]: The memcache PHP extension must be loaded to use this driver."
Looking into this.
Assignee: server-ops → shyam
Could be the most likely cause : Aug 11 23:08:12 Updated: php-pecl-memcache-2.2.5-1.el5.i386 Stuff was updated across the board before a kernel upgrade and the box was rebooted.
I've reverted to php-pecl-memcache-2.2.3-2.rhel5.i386 and it seems to be fine now. We need to look into this and see why the latest version does not work.
Summary: SUMO staging is down → php-pecl-memcache > 2.2.3-2.rhel5.i386 breaks sumo and mozillaservice stage
Webdev folks, Any idea on this? Laura?
php-pecl-memcache-2.2.3-2.rhel5.i386 is the RPM currently in our internal RHWAS repo, which would be the one compiled against the newer version of php from the RHWAS repo. The 2.2.5 version was probably compiled against the older php. This likely means there's a newer php-pecl-memcache for RHWAS that we haven't picked up.
If there's a newer one let's try it. Fallback then would be putting the new RPM on sumotools so we can try and diagnose.
Jeremy, I think what's on there was built by us, what's getting pulled in, is from epel php-pecl-memcache.i386 2.2.5-1.el5 epel Can you take a look at this please? Thanks!
Assignee: shyam → oremj
Rebuild 2.2.5 against our version of php and installed on stage.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Looks good to me on http://mozillaservice.stage.mozilla.com/home/index/en_US and http://support-stage.mozilla.org/, which were affected before by the upgrade. Verified FIXED, as best I can tell.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.