[389-users] Re: 389ds refuses to start up after a reboot on CentOS7

[William Brown]

On Sun, 2016-07-17 at 19:30 +0200, Graham Leggett wrote:
>  Hi all,
>  
>  I am having some unexpected behaviour from 389ds v1.3.4.0-32 on CentOS7 and I need to
> check if this looks familiar to anybody.
>  
>  After installing 389ds and configuring it successfully, and proving successfully that I
> can connect to it and that it contains data, I restarted the machine to prove the server
> comes up on reboot. 389ds refused to come up.
>  
>  Attempts to bring the server up manually using “systemctl start dirsrv.target” have no
> effect.
>  
>  What eventually got the service to start was “systemctl restart dirsrv@instancename”, but
> this hasn’t solved the start-at-boot problem.
>  
>  Does anyone have an accurate guide on 389ds and systemd?
>   
Yes, I have seen this issue.

It's actually a bug in the design of the .service files for the 1.3.4
release of 389-ds. 

This is fixed in 1.3.5.

The manual fix is:

cp /usr/lib/systemd/system/dirsrv@.service /etc/systemd/system/

Then to the file /etc/systemd/system/dirsrv@.service append:

[Install]
WantedBy=dirsrv.target


Assert the file /usr/lib/systemd/system/dirsrv.target contains:

[Install]
WantedBy=multi-user.target

Now you can do:

systemctl enable dirsrv.target
systemctl enable dirsrv(a)instance.target.


Hope this helps.


PS: You'll need to remove /etc/systemd/system/dirsrv@.service when you
upgrade to 1.3.5.



-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Brisbane