13, 2015 1:53:13 PM
> Subject: Re: [Freeipa-users] 389DS segfaults after upgrade FC 21 -> 22
>
> Dear all,
>
> Am 13.11.15 um 05:36 schrieb Prashant Bapat:
> > Is there a way for you to try F23. Its the latest anyway if thats the
> > reason you're upgrading.
> &
Dear all,
Am 13.11.15 um 05:36 schrieb Prashant Bapat:
> Is there a way for you to try F23. Its the latest anyway if thats the
> reason you're upgrading.
>
> I recently did this couple of times in a test setup (aws and
> virtualbox). I have 4.1.4 (F21) in production. Was trying upgrade from
> F21
Is there a way for you to try F23. Its the latest anyway if thats the
reason you're upgrading.
I recently did this couple of times in a test setup (aws and virtualbox). I
have 4.1.4 (F21) in production. Was trying upgrade from F21->F22 and
F22->F23 this would give me freeipa 4.2.3. Things went ve
On 11.11.2015 11:57, Torsten Harenberg wrote:
Dear all,
on our secondary IPA server (running 4.1.4) we did an upgrade of FC from
21 to 22, as 21 is running out of support.
The upgrade process itself went smoothly, however, 386DS segfaults now:
ns-slapd[1427]: segfault at 7fffe301413e ip
Dear all,
on our secondary IPA server (running 4.1.4) we did an upgrade of FC from
21 to 22, as 21 is running out of support.
The upgrade process itself went smoothly, however, 386DS segfaults now:
ns-slapd[1427]: segfault at 7fffe301413e ip 7fffeeb1fa08 sp
7fffd3d8 error 4 in libdb-
