[Freeipa-users] FreeIPA not starting - probably 389ds cause
Marco Pizzoli
marco.pizzoli at gmail.com
Sun Feb 12 13:15:07 UTC 2012
Hi Alexander,
On Sat, Feb 11, 2012 at 11:54 PM, Alexander Bokovoy <abokovoy at redhat.com>wrote:
> On Sat, 11 Feb 2012, Marco Pizzoli wrote:
> > Hi,
> > Today I booted my FreeIPA 2.1.4 system on Fedora16 and now I'm failing in
> > having it started.
> >
> > [root at freeipa01 ~]# systemctl | grep ipa
> > ipa.service loaded failed failed Identity, Policy,
> > Audit
> >
> > /var/log/messages
> > [cut]
> > Feb 11 12:15:13 freeipa01 systemd[1]: PID file /run/sendmail.pid not
> > readable (yet?) after start.
> > Feb 11 12:15:13 freeipa01 ntpd_intres[821]: host name not found:
> > 0.fedora.pool.ntp.org
> > Feb 11 12:15:13 freeipa01 ntpd_intres[821]: host name not found:
> > 1.fedora.pool.ntp.org
> > Feb 11 12:15:13 freeipa01 ntpd_intres[821]: host name not found:
> > 2.fedora.pool.ntp.org
> > Feb 11 12:15:14 freeipa01 systemd[1]: PID file /run/sm-client.pid not
> > readable (yet?) after start.
> > Feb 11 12:15:29 freeipa01 ipactl[998]: Failed to read data from Directory
> > Service: Unknown error when retrieving list of services from LDAP: [Errno
> > 111] Connection refused
> > Feb 11 12:15:29 freeipa01 ipactl[998]: Shutting down
> > Feb 11 12:15:29 freeipa01 ipactl[998]: Starting Directory Service
> > Feb 11 12:15:29 freeipa01 systemd[1]: ipa.service: main process exited,
> > code=exited, status=1
> > Feb 11 12:15:29 freeipa01 systemd[1]: Unit ipa.service entered failed
> state.
> > Feb 11 12:15:29 freeipa01 systemd[1]: Startup finished in 2s 327ms 887us
> > (kernel) + 4s 398ms 198us (initrd) + 40s 949ms 673us (userspace) = 47s
> > 675ms 758us.
> > [cut]
> >
> > /var/log/dirsrv/slapd-<my_user_dir>/errors
> > [cut]
> > [11/Feb/2012:12:15:27 +0100] - 389-Directory/1.2.10.a6 B2011.353.1631
> > starting up
> > [11/Feb/2012:12:15:27 +0100] - Detected Disorderly Shutdown last time
> > Directory Server was running, recovering database.
> >
> > /var/log/dirsrv/slapd-<my_pki_dir>/errors
> > [cut]
> > [11/Feb/2012:12:15:27 +0100] - 389-Directory/1.2.10.a6 B2011.353.1631
> > starting up
> > [11/Feb/2012:12:15:27 +0100] - Detected Disorderly Shutdown last time
> > Directory Server was running, recovering database.
> >
> > dmesg output
> > [cut]
> > [ 17.440200] systemd-tmpfiles[743]: Successfully loaded SELinux
> database
> > in 14ms 981us, size on heap is 485K.
> > [ 17.593118] systemd-tmpfiles[743]: Two or more conflicting lines for
> > /var/run/dirsrv configured, ignoring.
> > [ 17.593225] systemd-tmpfiles[743]: Two or more conflicting lines for
> > /var/lock/dirsrv configured, ignoring.
> > [cut]
> >
> > Any help?
> Did you try 'ipactl start' afterwards?
>
Yes, same as before.
> I'm not sure what has caused 389-ds database issue but from the log
> excerpts it looks like 389-ds was able to fix those.
>
> Fedora 16 stable updates got freeipa 2.1.4-5 and 389-ds 1.2.10-rc1
> tonight.
>
Now, I did a full upgrade of the system but I'm encountering quite the same
problem.
The interesting thing is that the 389-ds upgrade produced a log full of
interesting info about what the problem is.
Please find my log here: http://pastebin.com/ueH87Q05
I'm running a system with less than 1GB RAM
[root at freeipa01 ~]# free -m
total used free shared buffers cached
Mem: 869 758 110 0 42 561
-/+ buffers/cache: 154 714
Swap: 2015 0 2015
I'm curious to know if is an opportunity to recover the system. If no, I
have no problems in erase and recreate.
Thanks again
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/freeipa-users/attachments/20120212/408bdb8e/attachment.htm>
More information about the Freeipa-users
mailing list