On Tue, Dec 2, 2008 at 2:58 PM, Michael DeHaan <[EMAIL PROTECTED]> wrote: > Stephen John Smoogen wrote: >> On Tue, Dec 2, 2008 at 1:44 PM, Michael DeHaan <[EMAIL PROTECTED]> wrote: >> >>> Jeroen van Meeuwen wrote: >>> >> >> >>> What we've found out is that if Apache connects to itself within >>> mod_python via a mod_proxy URL, bad things happen. >>> >>> So if you change >>> >>> 127.0.0.1/cobbler_api (Apache proxied XMLRPC endpoint) to just >>> >>> 127.0.0.1:25151 (python directly) >>> >>> everything works great. >>> >>> Rather than hard code the port, I'm going to make it read the settings >>> file to get the port number, but basically that's the workaround. >>> >>> I suspect this /is/ a bug in mod_python and/or mod_proxy though I'm not >>> sure the extent of it's seriousness and am ultimately ok with the >>> workaround. >>> >> >> >From the httpd rpm changelog.. I would say it is in the mod_proxy code >> (the RPM has multiple changelogs for mod_proxy backporting from future >> versions). I opened a bug against this... hope it helps. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=474230 >> >> > > Should be fixed on devel today, FWIW. > > If you're wanting to run Cobbler on RHEL 5.3, wait until 1.4 which > should come out this month if you like. >
I am guessing that this breakage is going to affect more than cobbler so I figured a bug report would be better for a long term fix. There is also a mod_proxy bug report for it segfaulting so its good to at least test with 5.3 to make sure final doesn't come out with things like that. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
