supersonic feet

I’ve spent a good portion of my weekend banging my head against the desk after getting the hare-brained idea, following my success in setting up Apache 1.3.x with mod_proxy and Mongrel, to get Apache 2.2 running on my server so that I could then use mod_proxy_balancer and therefore mongrel_cluster.

As anyone who’s ever asked the question “How easy is it to install Apache 2 on a cPanel server?” knows, the answer has always been “don’t bother”. In the past couple of weeks however, CPanel finally added support for Apache 2 in their latest EDGE builds. After a quick bit of reading of the cPanel forums, it seemed people had it working well enough and so I embarked, without much forethought, on the upgrade.

A day or so and many, many hours of frustration later and I have it working, so I thought I’d round up my experience as before to try and save some poor souls the same experience. (more…)

The site was down overnight after I took the leap and started updating to Apache 2.2, support for which has finally been added to CPanel EDGE builds.

Once I had everything installed and updated, DNS was broken. I’ve just been sifting through the CPanel forum trying all kinds of ‘fix’ scripts and in the end, 15 seconds after submitting a support ticket to my hosts I found the solution by way of:

yum update bind-libs

Was some kind of problem that quite a lot of people seem to have had when updating CPanel.

Anyway, seems to be working now - I just need to find out how to recompile Apache to get mod_proxy and mod_proxy_balancer enabled without breaking CPanel (the whole point of this was to get Mongrel clustering).