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? Regards, Graham — -- 389-users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
