On 03/15/2018 11:36 AM, Julian Kippels wrote:
Hi,
since the last update (using RHEL 7, updated from 389-ds-1.3.6.1-21 to
389-ds-1.3.6.1-28) I cannot login as user admin in the administration
console anymore.
Looking at the logs I see this error message popping up every time I
try to log in since then:
[Thu Mar 15 13:09:35.046721 2018] [:crit] [pid 12027:tid 140250663868160] buildUGInfo():
unable to initialize TLS connection to LDAP host ldap-master.rz.uni-duesseldorf.de port
389: 4
What I find confusing, nowhere have I ever configured any encrypted
connections, because the whole setup is tucked away in a private vlan with
no access to the internet. How come the admin server suddenly wants
to use TLS? And how can I disable this and get back the old behaviour?
This is odd
since you did not update the admin server (in fact there
have not been any admin server updates in some time).
What error is the console login page reporting?
What is the administrative url in the login page, is it http:// or https://?
What is in admin server config files:
/etc/dirsrv/admin-serv/adm.conf
/etc/dirsrv/admin-serv/console.conf
Can you run the console is debug mode, reproduce error, and send the
output?:
389-console -D 9
What is in the DS access log? /var/log/dirsv/slapd-YOUR_INSTANCE/access
What is in the DS errors log?
Thanks,
Mark
Thanks in advance
Julian
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org