#2774 ipactl.service fails on boot - but not if manually started
Closed: Fixed None Opened 11 years ago by rcritten.

https://bugzilla.redhat.com/show_bug.cgi?id=806424 (Fedora)

Description of problem:

The ipactl.service fails on boot, but not if it is subsequently restarted
manually on boot up



Version-Release number of selected component (if applicable):
freeipa-server-2.1.4-5.fc16.x86_64

How reproducible:
Installed freeipa as per the instructions on the Fedora web site and
ipactl.service always fails on boot up but not if restarted manually

Steps to Reproduce:
1.
2.
3.

Actual results:

It should start up

Expected results:

It does not start

Additional info:

I've worked around this by doing a systemctl enable dirsrv.target and now the
ipactl.service does start on boot. What "seems" to happen is that ipactl starts
the 389 directory server but as far as systemd is concerned that target
(dirsrv.target) isn't wanted so it immediately shuts it down. Then the
subsequent services that ipactl tries to start fail because they can't contact
the 389 directory service. By explicitly enabling the dirsrv.target - it does
not get shutdown by systemd.

With systemd supposedly being all singing - all dancing - is ipactl the correct
thing to do - or should it be properly converted so that systemd itself starts
the required services? At the very least it would appear the ipactl.service may
need a dependency on dirsrv.target adding.

Changing 3.2 priority

As Rob wrote in https://bugzilla.redhat.com/show_bug.cgi?id=806424#c12, this issue is already solved - we just forgot to close it.

Metadata Update from @rcritten:
- Issue assigned to someone
- Issue set to the milestone: FreeIPA 3.1 Stabilization

7 years ago

Login to comment on this ticket.

Metadata