Manuel Gujo via FreeIPA-users wrote: > # systemctl status dirsrv@ITEC-LAB > ● [email protected] - 389 Directory Server ITEC-LAB. > Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled; vendor > preset: disabled) > Active: active (running) since mar 2020-11-17 18:00:26 UTC; 2 months 28 > days ago > Main PID: 15817 (ns-slapd) > Status: "slapd started: Ready to process requests" > CGroup: /system.slice/system-dirsrv.slice/[email protected] > └─15817 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-ITEC-LAB -i > /var/run/dirsrv/slapd-ITEC-LAB.pid > > feb 12 17:26:03 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 3 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 1 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 2 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 3 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 1 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 2 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 3 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 1 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 2 > feb 14 03:35:04 ipa1.itec.lab ns-slapd[15817]: GSSAPI server step 3 > > # netstat -tulpn | grep LISTEN > tcp 0 0 0.0.0.0:749 0.0.0.0:* LISTEN > 1222/kadmind > tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN > 1222/kadmind > tcp 0 0 192.168.20.3:53 0.0.0.0:* LISTEN > 17818/named > tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN > 17818/named > tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN > 24121/sshd > tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN > 15869/krb5kdc > tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN > 17818/named > tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN > 24232/master > tcp6 0 0 :::749 :::* LISTEN > 1222/kadmind > tcp6 0 0 :::80 :::* LISTEN > 16122/httpd > tcp6 0 0 :::464 :::* LISTEN > 1222/kadmind > tcp6 0 0 :::53 :::* LISTEN > 17818/named > tcp6 0 0 :::22 :::* LISTEN > 24121/sshd > tcp6 0 0 :::88 :::* LISTEN > 15869/krb5kdc > tcp6 0 0 ::1:953 :::* LISTEN > 17818/named > tcp6 0 0 ::1:25 :::* LISTEN > 24232/master > tcp6 0 0 :::443 :::* LISTEN > 16122/httpd > > dirsrv is started but I don't see port 636 on this list, how can I open it > for dirsrv?
In fact it isn't listening on any port. Stop dirsrv and look in /etc/dirsrv/slapd-ITEC-LAB/dse.ldif for nsslapd-port which should be 389 and nsslapd-security which should be on. If not then fix it and restart dirsrv. That should fix it. rob _______________________________________________ FreeIPA-users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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.fedorahosted.org/archives/list/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
