Stephen John Smoogen wrote:
On Tue, Dec 2, 2008 at 1:44 PM, Michael DeHaan
<mdehaan(a)redhat.com> 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.
--Michael