[Freeipa-users] FreeIPA not starting - probably 389ds cause

[Alexander Bokovoy]

On Sun, 12 Feb 2012, Marco Pizzoli wrote:
> > > Here they are.
> > > I think that it is not worth sending an attachment of over 1.2MB to the
> > > entire list, even if I don't have any personal data in them.
> > Thanks. Could you please edit /usr/sbin/ipactl and change timeout
> > parameter at lines 125 and 128 to something greater than 6? Maybe 10
> > or even 15... The parameter is seconds to time out:
> > ..
> >           wait_for_open_socket(lurl.hostport, timeout=6)
> > ..
> >           wait_for_open_ports(host, [int(port)], timeout=6)
> > ..
> >
> > Looks like your VM is so slow that ipactl simply times out to wait for
> > the directory server to respond. We've seen this before with some
> > other VMs.
> >
> 
> Good catch!
> I tried with 25, but same result :-(
> I tried with 45 and now it is up!
> 
> Please, could you confirm that the following "exited" is not bad thing:
> 
> [root at freeipa04 ~]# systemctl|grep ipa
> ipa.service               loaded active *exited*        Identity, Policy,
> Audit
> ipa_kpasswd.service       loaded active running       IPA Kerberos password
> service
*exited* is fine, it is /usr/sbin/ipactl exited after running the 
startup sequence.

Would you mind to file a ticket against FreeIPA to make this time out 
configurable in /etc/ipa/default.conf? This is something that we can't 
predict in all cases so this would be per-system setting.
-- 
/ Alexander Bokovoy