Ticket was cloned from Red Hat Bugzilla (product Red Hat Directory Server): Bug 887147
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: =============================== If the mapping of hostname and IP address in /etc/hosts file is not correct then setup-ds-admin.pl -ddd fails with error :: Creating the configuration directory server . . . Error: failed to open an LDAP connection to host dhcp201-130.englab.pnq.redhat.com' port '389' as user 'cn=Directory Manager'. Error: unknown. Failed to create the configuration directory server Exiting . . . Log file is '/tmp/setup7nSULU.log' Leaving no clue in logs that it is the multi-homed or multi-interface hosts or mapping issue in /etc/hosts file. Should we have related error log message for this? I mean to say the below message displayed as error on screen should be more discriptive and relative to the actual error:: Error: failed to open an LDAP connection to host 'dhcp201-130.englab.pnq.redhat.com' port '389' as user 'cn=Directory Manager'. Error: unknown. Failed to create the configuration directory server
0001-Ticket-47498-Error-Message-for-Failed-to-create-the-.patch 0001-Ticket-47498-Error-Message-for-Failed-to-create-the-.patch
Nice!
To ssh://git.fedorahosted.org/git/389/admin.git 463ed9a..7c7b49a master -> master commit 7c7b49a7b50c60a5eb5a32cf5d757f4fc7e5612d Author: Rich Megginson rmeggins@redhat.com Date: Wed Oct 2 16:17:39 2013 -0600
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 389-admin,console 1.1.36
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/835
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.