Sorry to reply to my own message, but I have come across some
information which might narrow down the search.
>From the Directory Server Console GUI, if I open up (by
double-clicking):
Server Group
389 Administration Server
admin-serv-us1lxas111(this is the hostname)
configuration
make no changes, and just click on the OK button at the bottom, I get an
error message that says "Unknown error with naming attribute"
________________________________
From: fedora-directory-users-bounces at redhat.com
[mailto:fedora-directory-users-bounces at redhat.com] On Behalf Of
Fairchild, Anthony
Sent: Wednesday, December 23, 2009 10:43 AM
To: fedora-directory-users at redhat.com
Subject: [389-users] Cannot start Admin server - host_ip_init():
Hello,
I have installed 389 Directory Server (v 1.2.2) and Admin Server
(v1.1.8) on RHEL 5.4, and in the process of getting SSL/TLS configured I
have somehow gotten the administration server into a state where it will
not start. When I run the init script it fails, and the
/var/log/dirsrv/admin-serv/error file has the following entry:
[Wed Dec 23 10:15:32 2009] [crit] host_ip_init(): PSET failure: Could
not retrieve access hosts attribute (past error = ) Configuration failed
Googling the problem led me to
http://directory.fedoraproject.org/wiki/Howto:AdminServerLDAPMgmt -
which contains directions for modifying the nsAdminAccessAddresses and
nsAdminAccessHosts entries, which I did. The entries are currently as
follows:
nsAdminAccessAddresses: *
nsAdminAccessHosts:
Which from my reading of the documentation suggests that access is
unrestricted, but starting the server still fails. Does anybody out
there have a suggestion as to what it is I have broken?
--
Anthony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20091223/b5501c67/attachment.html
