Understood. Unfortunately, this event has been diagnosed and mitigated, so re-occurance is unlikely. Will respond to this thread if we see any repeats however, totally understand the need for further information here.
Jeff Jeff Hallyburton Strategic Systems Engineer Bloomip Inc. Web: http://www.bloomip.com Engineering Support: supp...@bloomip.com Billing Support: bill...@bloomip.com Customer Support Portal: https://my.bloomip.com <http://my.bloomip.com/> On Fri, Jan 29, 2016 at 5:44 PM, Jakub Hrozek <jhro...@redhat.com> wrote: > On Fri, Jan 29, 2016 at 01:49:15PM +0100, Lukas Slebodnik wrote: > > On (28/01/16 18:37), Jeff Hallyburton wrote: > > >Application logs showed this to be due to an OOM error, so no need to > chase > > >this further. Thanks for the quick response! > > > > > Even though it was OOM. > > I would still be interested in version of sssd. > > "access after free error" is bed error. > > > > Do you have a coredump. It might be stored > > by abrt or systemd-coredumpd (coredumpctl) > > This problem reminds me of: > https://fedorahosted.org/sssd/ticket/2886 > > Sadly, that one was also a one-time condition and we could never get to > the root cause from the corefile. > > I agree with Lukas the core would be nice to see.. > > -- > Manage your subscription for the Freeipa-users mailing list: > https://www.redhat.com/mailman/listinfo/freeipa-users > Go to http://freeipa.org for more info on the project >
-- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project