Re: [389-users] New 389 ds install - cannot logon to adm console

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/30/2010 02:32 PM, Trisooma wrote:
>    On 11/30/2010 10:23 PM, Rich Megginson wrote:
>> On 11/30/2010 02:20 PM, trisooma wrote:
>>> If i am reading the code correctly (and looking at the logging
>>> below), the
>>> line that has a severity of 'crit' should dump info for the ldap
>>> server we
>>> are connecting to.
>>> In my case (and Eric's too) only 'ldap://:389' is printed; sometimes
>>> even
>>> with an odd number like 23395496 (see Eric's first post).
>>>
>>> [Tue Nov 30 22:01:43 2010] [crit] openLDAPConnection(): util_ldap_init
>>> failed for ldap://:389
>>> [Tue Nov 30 22:01:43 2010] [warn] Unable to open initial
>>> LDAPConnection to
>>> populate LocalAdmin tasks into cache.
>>> [Tue Nov 30 22:01:44 2010] [notice] Apache/2.2.17 (Unix) configured --
>>> resuming normal operations
>>> [Tue Nov 30 22:01:44 2010] [crit] openLDAPConnection(): util_ldap_init
>>> failed for ldap://:389
>>> [Tue Nov 30 22:01:44 2010] [warn] Unable to open initial
>>> LDAPConnection to
>>> populate LocalAdmin tasks into cache.
>>>
>>> The code that logs this error looks like this
>>> [mod_admserv/mod_admserv.c:517]
>>>
>>>           ap_log_error(APLOG_MARK, APLOG_CRIT, 0 /* status */, NULL,
>>>                        "openLDAPConnection(): util_ldap_init failed for
>>> ldap%s://%s:%d",
>>>                        data->secure ? "s" : "",
>>>                        data->host, data->port);
>>>
>>> It seems that the struct 'data' is not filled with the correct values.
>> That's why I asked for your /etc/dirsrv/admin-serv/adm.conf -
>> http://lists.fedoraproject.org/pipermail/389-users/2010-November/012548.html
> My bad, see
> http://lists.fedoraproject.org/pipermail/389-users/2010-November/012551.html
First, upgrade to the latest versions of these components from the 
testing repo
yum upgrade --enablerepo=updates-testing 389-admin 389-ds-base 389-adminutil

Then, run
setup-ds-admin.pl -u

Then try

ldapsearch -x -LLL -H ldap://icicle.phasma.nl:389/ -D 
"uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" -w 
youradminpassword -s base -b "cn=389 Administration Server,cn=Server 
Group,cn=icicle.phasma.nl,ou=phasma.nl,o=NetscapeRoot"

and

ldapsearch -x -LLL -H ldap://icicle.phasma.nl:389/ -D 
"uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" -w 
youradminpassword -s base -b "cn=admin-serv-icicle,cn=389 Administration 
Server,cn=Server Group,cn=icicle.phasma.nl,ou=phasma.nl,o=NetscapeRoot"

>>> BTW. this code was taken from 389-admin-1.1.12.a2
>>>
>>> I hope this helps,
>>>
>>> Regards,
>>>
>>> Trisooma
>>>
>>> -- 
>>> 389 users mailing list
>>> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
>>> https://admin.fedoraproject.org/mailman/listinfo/389-users
> --
> 389 users mailing list
> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users


[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux