On Mon, Nov 14, 2011 at 10:19, Alexander Bokovoy <aboko...@redhat.com> wrote:
> On Mon, 14 Nov 2011, Dan Scott wrote:
>> I've just upgraded a server from Fedora 15 to 16 and I'm having
>> problems starting the dirsrv process:
>> Nov 14 09:38:27 fileserver1 ipactl: Failed to read data from
>> Directory Service: Unknown error when retrieving list of services from
>> LDAP: [Errno 2] No such file or directory
>> Nov 14 09:38:27 fileserver1 ipactl: Shutting down
>> Nov 14 09:38:27 fileserver1 ipactl: Starting Directory Service
>> Nov 14 09:38:27 fileserver1 systemd: ipa.service: main process
>> exited, code=exited, status=1
>> Nov 14 09:38:27 fileserver1 systemd: Unit ipa.service entered failed
>> The /var/log/dirsrv/slapd-EXAMPLE-COM/errors file contains no new
>> entries since Friday 11th.
>> Any ideas how I can get this fixed? How can I find out which 'file or
>> directory' is missing?
> Looks like LDAP socket is not yet available at the time we try to
> contact it. I think this was fixed in Fedora 16 package with this
> Could you make sure 'systemctl start dirsrv.target' actually starts
> slapd for EXAMPLE-COM? If not, please show output of
> ls -l /etc/systemd/system/dirsrv.target.wants
'systemctl start dirsrv.target' doesn't appear to do anything, nothing
shown on the command line and the logs don't change. The directory is
[root@fileserver1 schema]# ls -l /etc/systemd/system/dirsrv.target.wants/
> It may be that we would need to make a small upgrade script that
> re-installs proper systemd instances for dirsrv.target as those are
> produced during ipa-server-install and cannot be done automatically on
> upgrade without proper intervention yet.
Is this related to this:
Or is it to do with the dependencies of FreeIPA startup?
In any case, the process is still failing to start. Do I need to
create a link in dirsrv.target.wants to somewhere?
Freeipa-users mailing list