On Wed, Jun 22, 2016 at 10:26:16AM -0400, Rob Crittenden wrote:
> Tomasz Torcz wrote:
> > On Tue, Jun 21, 2016 at 01:38:19PM -0400, Rob Crittenden wrote:
> > > > > > [Sat Jun 18 18:59:11.337717 2016] [wsgi:error] [pid 748083]
> > > > > > CertificateOperationError: Certificate operation cannot be
On Wed, Jun 22, 2016 at 05:01:55PM +0200, Youenn PIOLET wrote:
> Hi,
Hello Youen,
>
> Can you provide the output of :
> certutil -L -d /etc/dirsrv/slapd-/ on replicas that can't
> start the PKI?
> Your CA Cert attributes should be CT,C,C
---
$ certutil -L -d /etc/dirsrv/slapd-PIPEBREAKER-PL/
Hi,
Can you provide the output of :
certutil -L -d /etc/dirsrv/slapd-/ on replicas that can't
start the PKI?
Your CA Cert attributes should be CT,C,C
I experience the same issue as you every two replica I install. The fix is :
certutil -d /etc/dirsrv/slapd-/ -A -t "CT,C,C" -n " IPA CA" -i
Tomasz Torcz wrote:
On Tue, Jun 21, 2016 at 01:38:19PM -0400, Rob Crittenden wrote:
[Sat Jun 18 18:59:11.337717 2016] [wsgi:error] [pid 748083]
CertificateOperationError: Certificate operation cannot be completed: Unable to
communicate with CMS (Internal Server Error)
[Sat Jun 18
On Tue, Jun 21, 2016 at 01:38:19PM -0400, Rob Crittenden wrote:
> > > > [Sat Jun 18 18:59:11.337717 2016] [wsgi:error] [pid 748083]
> > > > CertificateOperationError: Certificate operation cannot be completed:
> > > > Unable to communicate with CMS (Internal Server Error)
> > > > [Sat Jun 18
Tomasz Torcz wrote:
On Sat, Jun 18, 2016 at 11:02:23PM -0400, Rob Crittenden wrote:
Most of the functions work, but 5) I cannot get Authentication→Certificates
list:
On okda, going to Certificates list yields ”Certificate operation cannot be
completed: Unable to communicate with CMS
On Sat, Jun 18, 2016 at 11:02:23PM -0400, Rob Crittenden wrote:
> >
> >Most of the functions work, but 5) I cannot get
> > Authentication→Certificates
> > list:
> >
> > On okda, going to Certificates list yields ”Certificate operation cannot be
> > completed: Unable to communicate with CMS
Tomasz Torcz wrote:
On Fri, Jun 17, 2016 at 11:32:22AM +0200, Petr Vobornik wrote:
On 27.5.2016 14:28, Tomasz Torcz wrote:
Hi,
In my home environment I'm using two-server FreeIPA configuration on Fedora.
Initially installed on fedora 19 in November 2013, it have been upgraded every
Fedora
On Fri, Jun 17, 2016 at 11:32:22AM +0200, Petr Vobornik wrote:
> On 27.5.2016 14:28, Tomasz Torcz wrote:
> > Hi,
> >
> > In my home environment I'm using two-server FreeIPA configuration on
> > Fedora.
> > Initially installed on fedora 19 in November 2013, it have been upgraded
> > every
> >
On 27.5.2016 14:28, Tomasz Torcz wrote:
> Hi,
>
> In my home environment I'm using two-server FreeIPA configuration on Fedora.
> Initially installed on fedora 19 in November 2013, it have been upgraded every
> Fedora release. It generally works OK, but somewhat degrades during operation.
>
On Mon, May 30, 2016 at 01:45:40PM +0200, Petr Spacek wrote:
> Fedora 24 is broken at the moment so there is nothing you can do before it is
> fixed & released.
>
> Sorry.
Petr, could you be more specific what is broken? We just signed F24 to be
released in current state. There were no
On 27.5.2016 14:28, Tomasz Torcz wrote:
> Hi,
>
> In my home environment I'm using two-server FreeIPA configuration on Fedora.
> Initially installed on fedora 19 in November 2013, it have been upgraded every
> Fedora release. It generally works OK, but somewhat degrades during operation.
>
Hi,
In my home environment I'm using two-server FreeIPA configuration on Fedora.
Initially installed on fedora 19 in November 2013, it have been upgraded every
Fedora release. It generally works OK, but somewhat degrades during operation.
Recently I've jumped to F24 in hope my problems will be
13 matches
Mail list logo
