On Mon, 14 Nov 2011, Dan Scott wrote:
> >> >           Loaded: error (Reason: No such file or directory)
> >> >           Active: inactive (dead)
> >> Right - see http://directory.fedoraproject.org/wiki/Howto:systemd#FAQ
> > Yes, the target is dirsrv.target, not dirsrv.service, while instances
> > are dirsrv@NAME.service. That is life.
> :) Nice and consistent with other 'services'. Do you know if it's
> possible for 'systemctl status dirsrv.service' to return nothing,
> instead of saying that it's dead? This would help reduce the
> confusion.
No, this is 'as designed' behaviour of systemd -- it loads list of 
services it knows once and then answers negatively to anything else 
unless it knows the service.

I think the idea was to make targets as synchronization points to 
which other services can rely in their ordering. As there is no single 
dirsrv.service, dirsrv.target is used to allow behaviour close to 
'service dirsrv <action>'

> > before, the keytab should be in place already and with proper
> > ownership (dirsrv:dirsrv).
> Thanks. I'd just figured this out and fixed my /etc/sysconfig/dirsrv
> file. The two servers seem to be working and syncing now.
> I've run into something else now though:
> djscott@pc35:~$ ipa host-del pc60
> ipa: ERROR: Certificate operation cannot be completed: Unable to
> communicate with CMS (Not Found)
> Could this be related? Or should I start a new thread to try and solve it.

Please start new thread. This most likely something that Dogtag 
expects in Fedora 16 which wasn't persisting from old install, as in 
bug #741458.

/ Alexander Bokovoy

Freeipa-users mailing list

Reply via email to