Red Hat Bugzilla – Bug 450214
Kerberos not starting.
Last modified: 2015-01-04 18:32:39 EST
Description of problem:Kerberos not starting after first reboot although it first started okay after installation. krb5kdc.log: Jun 05 14:02:33 directory.fronteranet.com krb5kdc[2854](info): setting up network... Jun 05 14:02:33 directory.fronteranet.com krb5kdc[2854](info): set up 0 sockets krb5kdc: no sockets set up? Version-Release number of selected component (if applicable): Server is a Fedora 9 domU How reproducible: Steps to Reproduce: 1.freeIPA install 2.reboot 3. Actual results:kinit admin Cannot contact any KDC for realm 'FRONTERANET.COM' while getting initial credentials Expected results: Additional info:Log files attached
Created attachment 308491 [details] ipaserver-install.log
Can you run this to verify that it is set up to start on boot: /sbin/chkconfig --list krb5kdc Are you using NetworkManager for your networking or the older network script? Can you start the KDC after boot-up? And finally, is ns-slapd running?
I had the same problem after installation. The system massage bus hangs during starting. I `ve followed http://www.freeipa.com/page/TroubleshootingGuide#IPA_Server_boot_problems and after this all started fine.
I was using NetworkManager. Kerberos started OK after disabling it.
ccing the NetworkManager maintainer to see if he has any ideas. The freeIPA-installed KDC isn't starting on bootup with NetworkManager but it is with network. I don't know if this is an init ordering problem or some NM option we need to set.
On F9 you may need to install updated NetworkManager packages from updates-testing because we moved NM earlier in the boot process. You could try: /sbin/chkconfig messagebus resetpriorities /sbin/chkconfig haldaemon resetpriorities /sbin/chkconfig NetworkManager resetpriorities and then ensure that there is a /etc/rc3.d/S27NetworkManager file. Since NM brings the network up asynchronously, if your service requires a network connection when it starts (which is actaully a bug in that service that it cannot listen for netlink events and notice interface changes on the fly) then you can add the line: NETWORKWAIT=yes to your /etc/sysconfig/network file to block startup for up to 10 seconds while waiting for a network connection to come up.
Eric or Andreas, can you give Dan's suggestion a shot? If it works we'll update our documentation to reflect this work-around.
I had the same problem and I can confirm that the NETWORKWAIT solution worked nicely for me.
Added Dan's comments to documentation at http://freeipa.org/page/TroubleshootingGuide