On 2/5/20 1:35 PM, Jochen Demmer via FreeIPA-users wrote:
Yeah I actually modified the PEM outputs because I wasn't sure if it was
sensible.
The second attribute userCertificate has the serial 21.
What about the ra-agent.key? When I put the certificate from the LDAP to
the file named ra-agent.p
Yeah I actually modified the PEM outputs because I wasn't sure if it was
sensible.
The second attribute userCertificate has the serial 21.
What about the ra-agent.key? When I put the certificate from the LDAP to
the file named ra-agent.pem, does the .key file need to be updated, too?
Thank you
On 2/3/20 9:07 AM, Jochen Demmer via FreeIPA-users wrote:
Hi,
unfortunately currently there's is no other node, which is why I'm
trying to update to Fedora 31. I used to replicate between two machines
but on got lost.
I installed a new machine which is supposed to work as my new replica
but t
Hi,
unfortunately currently there's is no other node, which is why I'm trying to
update to Fedora 31. I used to replicate between two machines but on got lost.
I installed a new machine which is supposed to work as my new replica but this
is being virtualized in bhyve / FreeNAS and this doesn't
On 2/2/20 11:30 PM, Jochen Demmer via FreeIPA-users wrote:
Hi,
this is the outputs:
[root@srv107 ipa]# openssl x509 -noout -in /var/lib/ipa/ra-agent.pem
-serial -subject -issuer -nameopt RFC2253
serial=15
subject=CN=IPA RA,O=UNIX.domain.NET
issuer=CN=Certificate Authority,O=UNIX.domain.NET
[r
Hi,
this is the outputs:
[root@srv107 ipa]# openssl x509 -noout -in /var/lib/ipa/ra-agent.pem -serial
-subject -issuer -nameopt RFC2253
serial=15
subject=CN=IPA RA,O=UNIX.domain.NET
issuer=CN=Certificate Authority,O=UNIX.domain.NET
[root@srv107 ipa]# openssl x509 -noout -in ra-agent.pem -serial
On 1/20/20 9:39 AM, Jochen Demmer via FreeIPA-users wrote:
I suffer the exact same problem and already tried to upgrade twice but
every time the update fails.
The ldap server does not listen when I check with ss or netstat.
I reverted back to Fedora 30 with snapshots every time.
Hi,
can you
I suffer the exact same problem and already tried to upgrade twice but
every time the update fails.
The ldap server does not listen when I check with ss or netstat.
I reverted back to Fedora 30 with snapshots every time.
Can someone help me to work this around. The OP writes of an IP that
chan
- Original Message -
> From: "Wulf C. Krueger via FreeIPA-users"
>
> To: freeipa-users@lists.fedorahosted.org
> Cc: "Wulf C. Krueger"
> Sent: Sunday, November 10, 2019 10:02:08 AM
> Subject: [Freeipa-users] Re: FreeIPA 4.8.1 on Fedora 31 (upgrad
On 2019-11-02 13:47, Wulf C. Krueger wrote:
my FreeIPA installation was working well on Fedora 30. After upgrading
to F31, though, it fails to start:
For posterity's sake as well as that of anyone facing the same issue:
For some reason, the IP of the host FreeIPA runs on, changed which,
admit
On 2019-11-05 13:47, Wulf C. Krueger via FreeIPA-users wrote:
I've tried starting FreeIPA again and have uploaded
the resulting new logs: https://mailstation.de/ipa-logs/new/
Well, since there don't seem to be any ideas how to salvage that
installation (logs still available in the location men
Hello Alex,
On 2019-11-04 18:20, Alex Scheel via FreeIPA-users wrote:
2019-11-02T10:57:00Z DEBUG stderr=Job for pki-tomcatd@pki-tomcat.service failed
because a timeout was exceeded.
See "systemctl status pki-tomcatd@pki-tomcat.service" and "journalctl -xe" for
details.
However, the pki-tomcat-
t;
> Cc: "FreeIPA users list" , "Alex
> Scheel" , "Alexander
> Bokovoy"
> Sent: Monday, November 4, 2019 11:50:41 AM
> Subject: [Freeipa-users] Re: FreeIPA 4.8.1 on Fedora 31 (upgraded from F30)
> fails to start
>
> On ma, 04 marras 2019,
On ma, 04 marras 2019, Wulf C. Krueger wrote:
Hello Alex,
On 2019-11-04 16:49, Alex Scheel via FreeIPA-users wrote:
These backtraces from Wulf don't end in JSS at all. In fact, JSS seems to
initalize
just fine around 2019-11-02 11:55:34 in the Tomcat debug log. This seems like a
bug
in the LD
Hello Alex,
On 2019-11-04 16:49, Alex Scheel via FreeIPA-users wrote:
These backtraces from Wulf don't end in JSS at all. In fact, JSS seems to
initalize
just fine around 2019-11-02 11:55:34 in the Tomcat debug log. This seems like a
bug
in the LDAPProfileSubsystem of Dogtag.
Thanks for chim
On ma, 04 marras 2019, Alex Scheel wrote:
- Original Message -
From: "Alexander Bokovoy via FreeIPA-users"
To: "FreeIPA users list"
Cc: "Wulf C. Krueger" , "Alexander Bokovoy"
Sent: Sunday, November 3, 2019 4:08:09 AM
Subject: [Freei
- Original Message -
> From: "Alexander Bokovoy via FreeIPA-users"
>
> To: "FreeIPA users list"
> Cc: "Wulf C. Krueger" , "Alexander Bokovoy"
>
> Sent: Sunday, November 3, 2019 4:08:09 AM
> Subject: [Freeipa-users] Re: Fre
Hello Wulf,
Oh yes, in your case, the slapd directory server is started but seems not
listening on 389/636, according to the log file. On another further look,
yes, you are right, the stack trace looks different from the one in Pagure.
As a side node, I had tried to install the jss rpm from
updat
Hello Patrick,
On 2019-11-02 20:54, Patrick Dung via FreeIPA-users wrote:
I am having the same problem about three days ago.
Related thread in:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org/thread/WLBFHI266KKHLF6G2UC4MHR4OLCLR45S/
Thanks, I saw that thread
Hello Alexander,
On 2019-11-03 10:08, Alexander Bokovoy via FreeIPA-users wrote:
This looks like https://bugzilla.redhat.com/show_bug.cgi?id=1766451
Do you have updates-testing repository enabled? It should provide an
update for jss package.
Thanks for the suggestion! Unfortunately, updating t
On la, 02 marras 2019, Wulf C. Krueger via FreeIPA-users wrote:
Hello,
my FreeIPA installation was working well on Fedora 30. After upgrading
to F31, though, it fails to start:
# ipactl start
IPA version error: data needs to be upgraded (expected version
'4.8.1-4.fc31', current version
Hello Wulf,
I am having the same problem about three days ago.
Related thread in:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org/thread/WLBFHI266KKHLF6G2UC4MHR4OLCLR45S/
Looks like the problem is related to https://pagure.io/dogtagpki/issue/3111
I am waiting for
22 matches
Mail list logo