Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-30 Thread Martin Basti
On 30/10/14 06:09, Michael Lasevich wrote: Maybe I should not be doing this late at night, but I cannot find cn=IPK11 Unique IDs,cn=IPA UUID,cn=plugins,cn=config anywhere. -M IMO something bad happens during the ipa upgrade, can you remove

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-30 Thread Michael Lasevich
*sigh* Feel like I am going around in circles ipa-ldap-updater --upgrade failed with: Upgrade failed with attribute allowWeakCipher not allowed I am running 1.3.3 from mkosek-freeipa copr: 389-ds-base-libs-1.3.3.5-1.fc20.x86_64 389-ds-base-1.3.3.5-1.fc20.x86_64 yum info 389-ds-base Loaded

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-29 Thread Martin Basti
On 28/10/14 20:54, Michael Lasevich wrote: I have a pair of servers that were both installed on clean Fedora20 4.0.1 from pviktori copr repo and then upgraded from mkosek to 4.1 During update, secondary was done first and worked but primary run into trouble as described Looking under

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-29 Thread Michael Lasevich
Maybe I should not be doing this late at night, but I cannot find cn=IPK11 Unique IDs,cn=IPA UUID,cn=plugins,cn=config anywhere. -M On 10/29/14, 3:03 AM, Martin Basti wrote: On 28/10/14 20:54, Michael Lasevich wrote: I have a pair of servers that were both installed on clean Fedora20 4.0.1

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-28 Thread Martin Basti
On 28/10/14 06:14, Michael Lasevich wrote: Running into same thing, but running ipa-dnsinstall does not complete: = Configuring DNS (named) [1/8]: generating rndc key file WARNING: Your system is running out of entropy, you may experience long delays [2/8]:

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-28 Thread Michael Lasevich
I have a pair of servers that were both installed on clean Fedora20 4.0.1 from pviktori copr repo and then upgraded from mkosek to 4.1 During update, secondary was done first and worked but primary run into trouble as described Looking under cn=keys,cn=sec,cn=dns,dc=my,dc=domain,dc=com I get one

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread John Obaterspok
2014-10-27 12:19 GMT+01:00 Martin Basti mba...@redhat.com: On 26/10/14 21:39, John Obaterspok wrote: Hi, I enabled mkosek-freeipa repo for F20 and updated freeipa-server from 3.3.5 to 4.1. The yum update reported just a single error: Could not load host key: /etc/ssh/ssh_host_dsa_key

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread Martin Basti
On 27/10/14 18:53, John Obaterspok wrote: 2014-10-27 12:19 GMT+01:00 Martin Basti mba...@redhat.com mailto:mba...@redhat.com: On 26/10/14 21:39, John Obaterspok wrote: Hi, I enabled mkosek-freeipa repo for F20 and updated freeipa-server from 3.3.5 to 4.1. The yum update

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread John Obaterspok
Hello Martin, Still no go. I installed the softhsm-devel package (that only contains header files), removed the token directory, reinstalled the bind bind-pkcs11, did ipa-dns-install that completed ok (I guess): To accept the default shown in brackets, press the Enter key. Existing BIND

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread Martin Basti
On 27/10/14 19:57, John Obaterspok wrote: Hello Martin, Still no go. I installed the softhsm-devel package (that only contains header files), removed the token directory, reinstalled the bind bind-pkcs11, did ipa-dns-install that completed ok (I guess): To accept the default shown in

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread John Obaterspok
hmm... Could not connect to the Directory Server So I started it with start-dirsrv since systemctl start ipa failed. Then it was a breeze, ipa-dns-install worked fine. # systemctl --failed 0 loaded units listed. I haven't verified that it works, but I feel confident :) -- john 2014-10-27

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread Martin Basti
On 27/10/14 20:34, John Obaterspok wrote: hmm... Could not connect to the Directory Server So I started it with start-dirsrv since systemctl start ipa failed. Then it was a breeze, ipa-dns-install worked fine. # systemctl --failed 0 loaded units listed. I'm lost, does IPA work or not? are

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread John Obaterspok
Hello Martin, It works perfectly again! note, I noticed in /var/log/ipaserver-install.log that ipa-dns-installed failed due to 389 wasn't started (failed to connect). Once it was started manually the ipa-dns-installed worked fine. Thanks a lot Martin, -- john 2014-10-27 20:40 GMT+01:00

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread Martin Basti
On 27/10/14 20:50, John Obaterspok wrote: Hello Martin, It works perfectly again! note, I noticed in /var/log/ipaserver-install.log that ipa-dns-installed failed due to 389 wasn't started (failed to connect). Once it was started manually the ipa-dns-installed worked fine. Thanks a lot

Re: [Freeipa-users] F20 Problem upgrading to 4.1

2014-10-27 Thread Michael Lasevich
Running into same thing, but running ipa-dnsinstall does not complete: = Configuring DNS (named) [1/8]: generating rndc key file WARNING: Your system is running out of entropy, you may experience long delays [2/8]: setting up our own record [3/8]: adding NS

[Freeipa-users] F20 Problem upgrading to 4.1

2014-10-26 Thread John Obaterspok
Hi, I enabled mkosek-freeipa repo for F20 and updated freeipa-server from 3.3.5 to 4.1. The yum update reported just a single error: Could not load host key: /etc/ssh/ssh_host_dsa_key After reboot I had 3 services that failed to start: ipa, kadmin, named-pkcs11 Doing strace -f named-pkcs11 -u