Jeroen van Meeuwen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ashley Penney wrote: > | I just wanted to drop a quick mail to the list to see if anyone else > | has tried testing cobbler on RHEL 5.3beta, and what your experiences > | were? For me it completely broke and won't allow me to fetch > | kickstart files via the web interface (giving a mod_python) error. > > I'm confused. Did it break down completely or is not being able to fetch > the kickstart files via the web interface the only real error? > > - -Jeroen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkk1mJMACgkQKN6f2pNCvwg6IQCdFLD7MsZMtij0n9Zttqkayaek > icYAoIa7b5IW97rNY9QtHQQefm25ZXii > =TgEh > -----END PGP SIGNATURE----- > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
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. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
