Thanks Richard and Richard - Tried to post last night by my home mail
server is blocked as a spammer for some reason (a bad spammer *is* on my
subnet somewhere...)
I had a long think about what was different between the working installs
and non-working installs and realized the one that wasn't working had a
"." in the name due to our naming convention. I tried substituting a
"-" for the "." and it worked like a charm. :-)
Thanks for the help folks. I'll file a bug report - the installer
should at least prevent you from using periods in instance names.
Travis
On Tue, 2007-10-02 at 17:04 -0600, Richard Megginson wrote:
Travis wrote:
> I agree with Graham's original idea - its almost as if the server is not
> looking in the proper location for the database. Does anyone know where
> this is set?
>
It looks for /opt/fedora-ds/alias/slapd-instancename-cert8.db - also
grep -i nscert /opt/fedora-ds/slapd-instancename/config/dse.ldif
> Thanks,
>
> Travis
>
> On Tue, 2007-10-02 at 18:25 -0400, Travis wrote:
>
>> Hi,
>>
>> No, as noted it is a completely new install, and I've already ddouble
>> checked permissions.
>>
>> Regardless - I've also tried chowning the entire tree to ldap (yes, this
>> is the user privs are being dropped to), as well as setting a+rw on the
>> entire /opt/fedora-ds tree.
>>
>> Thanks,
>>
>> Travis
>>
>>
>> On Tue, 2007-10-02 at 17:30 -0400, Rob Crittenden wrote:
>>
>>> Travis wrote:
>>>
>>>> Hi,
>>>>
>>>> We're preparing to upgrade from the initial DS release to 1.0.4-1 on
our
>>>> RHEL4 servers. In testing, we've hit a brick wall while trying to
set
>>>> up SSL. We can install the server just fine, but when clicking on
>>>> "Manage Certificates" in the console we get the following:
>>>>
>>>> could not open file slapd-$hostname-cert8.db
>>>>
>>>> We get the same type of error when trying to manage the admin server
>>>> certs.
>>>>
>>>> This is a completely fresh install, and we've double checked file
>>>> ownership, so permissions are not an issue. After working on this for
a
>>>> while, I tried installing the FC6 rpm on my FC6 desktop with the same
>>>> settings and JVM, which worked just fine...so its something specific
>>>> about the RHEL4 version or its dependencies.
>>>>
>>>> I found one other post about this kind of issue (From Nov 2006 by
Graham
>>>> Leggett), but I never saw a solution. I have even tried initializing
>>>> the DBs by hand with certutil, but this does not appear to make a
>>>> difference.
>>>>
>>>> Any advice?
>>>>
>>>>
>>> Permissions perhaps?
>>>
>>> rob
>>>
>>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>>
>> !DSPAM:10001,4702c57f55891133320659!
>>
>>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
!DSPAM:10001,4702cfc155891054640233!