On 09/20/2011 07:45 AM, Chris Ober wrote:
I've read that, and I believe I've followed the steps shown there, but
it doesn't solve my problem.
let's start with perms/ownership
ls -al /etc/dirsrv/slapd-instance
grep nsslapd-localuser /etc/dirsrv/slapd-instance/dse.ldif
see what the server cert name is
grep -i personality /etc/dirsrv/slapd-instance/dse.ldif
next, look at certutil
certutil -d /etc/dirsrv/slapd-instance -L
certutil -d /etc/dirsrv/slapd-instance -L -n "name of CA cert"
certutil -d /etc/dirsrv/slapd-instance -L -n "name of server cert"
On 9/19/11 2:47 PM, Rich Megginson wrote:
> On 09/19/2011 12:26 PM, Chris M. Ober wrote:
>> Hello all,
>> I've installed 389 to replace an ancient server that is on its last
>> legs. I got everything configured and working, until just now. I
>> generated and signed ssl keys to use ldaps, and it seemed to accept
>> everything. It told me to restart the service, which it wouldn't
>> allow me to do from the console. From the command line `service
>> dirsrv restart` gave me an error I can't figure out. The error is:
>> [root@ceto2 ~]# service dirsrv start
>> Starting dirsrv:
>> ceto2...[19/Sep/2011:14:07:19 -0400] - SSL alert: Security
>> Initialization: Unable to authenticate (Netscape Portable Runtime
>> error -8192 - An I/O error occurred during security authorization.)
>> [19/Sep/2011:14:07:19 -0400] - ERROR: SSL Initialization Failed.
>> *** Warning: 1 instance(s) failed to start
>> I haven't been able to find anything on google to help me solve
>> this. Any idea what is going wrong?
>> Thank you,
>> 389 users mailing list