James Roman wrote:
In case any one runs into this error while trying to create a replica:
Starting dirsrv:
REALM-COM...[15/Sep/2009:09:39:18 -0400] dse - The entry cn=schema in
file /etc/dirsrv/slapd-REALM-COM/schema/##xx.ldif is invalid, error
code 21 (Invalid syntax) - object class nsA
In case any one runs into this error while trying to create a replica:
Starting dirsrv:
REALM-COM...[15/Sep/2009:09:39:18 -0400] dse - The entry cn=schema in
file /etc/dirsrv/slapd-REALM-COM/schema/##xx.ldif is invalid, error
code 21 (Invalid syntax) - object class nsAIMpresence: Unknown
James Roman wrote:
Yes the valicert.com certificate did get installed in the DS cert
database and then subsequently failed to install in the web server
database. I can't find any output to indicate why it was missed. The
answer to your next question is yes, I did specify the same PKCS12
certi
Yes the valicert.com certificate did get installed in the DS cert
database and then subsequently failed to install in the web server
database. I can't find any output to indicate why it was missed. The
answer to your next question is yes, I did specify the same PKCS12
certificate file and pin
James Roman wrote:
I installed the 1.2.2-1 version from the test repo. I get really close
to the end, but it is still bombing when trying to set the trust
permissions on the web server cert. For some reason the final cert in
the chain did not get installed into the /etc/httpd/alias directory. A
I installed the 1.2.2-1 version from the test repo. I get really close
to the end, but it is still bombing when trying to set the trust
permissions on the web server cert. For some reason the final cert in
the chain did not get installed into the /etc/httpd/alias directory. All
worked fine for
James Roman wrote:
OK I am still running into a similar problem when installing the replica
server. It appears that the problem stems from the chained CA
certificates from GoDaddy again. On the replica server, all the certs
appear to be installed properly. The script is choking when modifying
OK I am still running into a similar problem when installing the replica
server. It appears that the problem stems from the chained CA
certificates from GoDaddy again. On the replica server, all the certs
appear to be installed properly. The script is choking when modifying
the trust arguments.
James Roman wrote:
Can anyone elaborate on the options for the ipa-replica-prepare command?
I have a third party signed certificate for both my master and replica
server. Am I supposed to provide the PKCS12 file for the master server
or the replica? If it is looking for the master server, I rea
Can anyone elaborate on the options for the ipa-replica-prepare command?
I have a third party signed certificate for both my master and replica
server. Am I supposed to provide the PKCS12 file for the master server
or the replica? If it is looking for the master server, I really don't
want the
10 matches
Mail list logo
