Cannot start Admin server - host_ip_init():

[Fairchild, Anthony]

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?

[Fairchild, Anthony]

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: [e-mail]
[mailto:[e-mail]] On Behalf Of
Fairchild, Anthony
Sent: Wednesday, December 23, 2009 10:43 AM
To: [e-mail]
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?

[Marc Sauton]

You may also want to check some directory and file permissions for 
/etc/dirsrv/admin-serv/adm.conf
M.

On 12/23/2009 08:21 AM, Fairchild, Anthony wrote:
> 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:* [e-mail] 
> [mailto:[e-mail]] *On Behalf Of 
> *Fairchild, Anthony
> *Sent:* Wednesday, December 23, 2009 10:43 AM
> *To:* [e-mail]
> *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
>
> --
> 389 users mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

Cannot start Admin server - host_ip_init(): - SOLVED

[Fairchild, Anthony]

I came across the solution to this one (lots of digging + a little bit
of luck).

In the /etc/dirsrv/admin-serv/local.conf file, there was a
'configuration.nsAdminAccessAddresses:' entry, but no entry labeled
'nsAdminAccessHosts:'. After manually adding that entry, the
Administration server started up successfully and I was able to continue
with getting SSL working.

The root cause of this appears to be me making too many changes at once,
and possibly skipping a step or two in the directions, which resulted in
me shutting down the admin server without saving some changes somewhere
- that's my current guess anyway, I'm still pretty new to this.

Thanks for the suggestion.