Re: [Freeipa-users] Fwd: FreeIPA on Fedora 19 won't work
Did we confirm that this is a bug? Was it filed? The user added this information to https://bugzilla.redhat.com/show_bug.cgi?id=953488 last week. rob Bug still appears on F19 (ran into it again installing another FreeIPA server for my lab). Will look at re-creating in a virtual machine and filing a bug report when I can. This issues has existed for a while, I set up my first freeIPA server on F17 last year and had the problem then. I suspect its unusual for people using IPA to require HTTP_PROXY/HTTPS_PROXY to be set on their machines. My setup is unusual in that the University network info-structure is externally controlled and my freeIPA setup exists within it to provide authentication for our dual boot lab. G. ___ Freeipa-users mailing list Freeipa-users@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-users
Re: [Freeipa-users] Fwd: FreeIPA on Fedora 19 won't work
Dmitri Pal wrote: On 09/29/2013 06:48 AM, Glenn Jenkins wrote: Alexander Bokovoy abokovoy@... writes: On Fri, 14 Jun 2013, Steve Dickson wrote: The $subject says it all... Any ideas what is going on here? I did fresh install right now on a up to date F19 VM and experienced no problem whatsoever. There were updates in pki-* and 389-ds-* packages over weekend. 2013-06-14T16:54:45Z DEBUG Starting external process 2013-06-14T16:54:45Z DEBUG args=/usr/sbin/pkispawn -s CA -f /tmp/tmpO2lDxI 2013-06-14T16:54:51Z DEBUG Process finished, return code=1 2013-06-14T16:54:51Z DEBUG stdout=Loading deployment configuration from /tmp/tmpO2lDxI. ^^^ The date corresponds to Friday last week, also there was issue with metadata information in Fedora 19 and Rawhide repositories which prevented proper packages propagating. Please try up to date packages from update-testing as of Monday. I think this is similar to a bug I've seen reported elsewhere I believe the underlying cause may be the HTTP_PROXY and HTTPS_PROXY variables. If these are set then the ipa install script has problems locating the dogtag server and fails. The error I see in my install log is something along the lines of certificate server failed to restart. From the point of view of the running script the failure looks the same as that produced if the script is run twice. It should be easy to re-create this bug simply by setting HTTP_PROXY and HTTPS_PROXY on a test server and running the server install. Posts in other forums suggest re-installation solves the problem, I suggest this simply removes these variables. Could the install script check for them being set and unset-reset them or simply warn the user? Did we confirm that this is a bug? Was it filed? The user added this information to https://bugzilla.redhat.com/show_bug.cgi?id=953488 last week. rob ___ Freeipa-users mailing list Freeipa-users@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-users
Re: [Freeipa-users] Fwd: FreeIPA on Fedora 19 won't work
Alexander Bokovoy abokovoy@... writes: On Fri, 14 Jun 2013, Steve Dickson wrote: The $subject says it all... Any ideas what is going on here? I did fresh install right now on a up to date F19 VM and experienced no problem whatsoever. There were updates in pki-* and 389-ds-* packages over weekend. 2013-06-14T16:54:45Z DEBUG Starting external process 2013-06-14T16:54:45Z DEBUG args=/usr/sbin/pkispawn -s CA -f /tmp/tmpO2lDxI 2013-06-14T16:54:51Z DEBUG Process finished, return code=1 2013-06-14T16:54:51Z DEBUG stdout=Loading deployment configuration from /tmp/tmpO2lDxI. ^^^ The date corresponds to Friday last week, also there was issue with metadata information in Fedora 19 and Rawhide repositories which prevented proper packages propagating. Please try up to date packages from update-testing as of Monday. I think this is similar to a bug I've seen reported elsewhere I believe the underlying cause may be the HTTP_PROXY and HTTPS_PROXY variables. If these are set then the ipa install script has problems locating the dogtag server and fails. The error I see in my install log is something along the lines of certificate server failed to restart. From the point of view of the running script the failure looks the same as that produced if the script is run twice. It should be easy to re-create this bug simply by setting HTTP_PROXY and HTTPS_PROXY on a test server and running the server install. Posts in other forums suggest re-installation solves the problem, I suggest this simply removes these variables. Could the install script check for them being set and unset-reset them or simply warn the user? G ___ Freeipa-users mailing list Freeipa-users@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-users
