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

trisooma trisooma at xs4all.nl
Tue Nov 30 21:20:49 UTC 2010


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.

BTW. this code was taken from 389-admin-1.1.12.a2

I hope this helps,

Regards,

Trisooma




More information about the 389-users mailing list