[389-users] admin server under solaris not running

[Steffen Blume]

Rich Megginson wrote:
> Steffen Blume wrote:
>> Hello,
>>
>> my admin server (apache/httpd.worker) is not starting under
>> /OpenSolaris/ (/SunOS 5.11/).
>> I added the error log below. Log level is debug. The only error msg is
>> the last line from nss. I compiled 389 DS by myself.
>> Versions:
>> nss-3.12.4-with-nspr-4.8
>> 389-ds-base-1.2.4
>> mod_nss-1.0.8
>> adminutil-1.1.8
>> 389-admin-1.1.9
>>
>> --------------------------
>> [Wed Jan 06 11:13:55 2010] [debug] mod_admserv.c(2419): Entering
>> mod_admserv_post_config - pid is [6597] init count is [0]
>> [Wed Jan 06 11:13:55 2010] [debug] mod_admserv.c(2248): Entering
>> do_admserv_post_config - pid is [6597]
>> [Wed Jan 06 11:13:55 2010] [debug] mod_admserv.c(2256): Entering
>> do_admserv_post_config - init count is [1]
>> [Wed Jan 06 11:13:55 2010] [debug] mod_admserv.c(2280): [6597] Cache
>> expiration set to 600 seconds
>> [Wed Jan 06 11:13:55 2010] [debug] mod_admserv.c(2383): Added
>> StartConfigDs task entry
>> [cn=startconfigds,cn=operation,cn=tasks,cn=admin-serv-ldap,cn=389
>> administration server,cn=server
>> group,cn=ldap.mydomain.de,ou=mydomain.de,o=netscaperoot:start_config_ds:]
>>
>> for user [LocalSuper]
>> [Wed Jan 06 11:13:55 2010] [notice] Access Host filter is:
>> *.mst.uni-hannover.de
>> [Wed Jan 06 11:13:55 2010] [notice] Access Address filter is: *
>> [Wed Jan 06 11:13:55 2010] [info] mod_unique_id: using ip addr
>> xxx.xxx.xxx.xxx
>> Assertion failure: SECSuccess == rv, at sslnonce.c:156
>>   
> Do you have a core file for admin server?
No. It terminates without crashing.
> If not, can you run the admin server using a debugger?
Just tried it with gdb. But gdb prints an internal error (and crashes):

elfread.c:366: internal-error: sect_index_data not initialized
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
elfread.c:366: internal-error: sect_index_data not initialized
A problem internal to GDB has been detected,
further debugging may prove unreliable.

I looked at the nss source code, where the error occurs. Somehow the
function NSS_RegisterShutdown is called before NSS is initialized and
returns an error. I think this happens indirectly in mod_nss!?

>> --------------------------
>>
>> Any advice?
>>
>> Regards,
>> Steffen
>>
>>   
>

-- 
Dipl.-Ing. Steffen Blume        Institute of Microelectronic Systems
phone : +49-511-762-19605       Leibniz Universität Hannover
fax   : +49-511-762-19601       Appelstr. 4, 30167 Hannover, Germany
mail  : sblume at ims.uni-hannover.de