> On 21 Dec 2020, at 20:54, Oleg Cohen <oleg.cohen@xxxxxxxxxxxxxxxx> wrote: > > Hi William, > > Thank you for replying! > > Here is the info: > > Starting with /sbin/start-dirsrv > > Description: Red Hat Enterprise Linux Server release 7.8 (Maipo) > Release: 7.8 > Codename: Maipo > > 389-ds-base-1.4.0.13-20180729.el7.centos.x86_64 Curious about how you are using 1.4.0 on rhel 7. Regardless, with 1.4.0, you should be using the systemctl unit files - start-dirsrv is no longer supported, and will not setup selinux contexts properly for you. Neither will it do many other things correctly. So I think you should look for systemd unit files there. Curiously, did you *also* use setup-ds.pl too? Because that's no longer supported either ... you need to use dscreate. Finally, 1.4.0 is a pretty old release, so if you are doing "custom builds" really consider looking at 1.4.3 or higher. Thanks! > > Best regards, > Oleg > >> On Dec 20, 2020, at 11:26 PM, William Brown <wbrown@xxxxxxx> wrote: >> >> Hey there, >> >>> On 19 Dec 2020, at 21:59, Oleg Cohen <oleg.cohen@xxxxxxxxxxxxxxxx> wrote: >>> >>> Greetings, >>> >>> I have a server that suddenly can be started due to the following error: >>> >>> PR_Bind() on All Interfaces port 389 failed: Netscape Portable Runtime error -5966 (Access Denied.) >> >> What method are you using to start the server? >> >> Can you also confirm your linux distro/platform and the 389-ds version? >> >>> >>> I disabled selinux to try and also checked that the policy on the port set during install is still there. >>> >>> Wonder if anyone has encountered a similar issue and if there are any ways to further troubleshoot and fix the problem. >>> >>> Thank you! >>> Oleg >>> >>> -- >>> Oleg Cohen | Principal | A S S U R E B R I D G E >>> Office: +1 617 564 0737 | Mobile: +1 617 455 7927 | Fax: +1 888 409 6995 >>> Email: Oleg.Cohen@xxxxxxxxxxxxxxxx | www.assurebridge.com >>> _______________________________________________ >>> 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx >>> To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx >>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx >> >> — >> Sincerely, >> >> William Brown >> >> Senior Software Engineer, 389 Directory Server >> SUSE Labs, Australia >> _______________________________________________ >> 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs, Australia _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
