Application logs showed this to be due to an OOM error, so no need to chase this further. Thanks for the quick response!
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 Thu, Jan 28, 2016 at 6:22 PM, Lukas Slebodnik <lsleb...@redhat.com> wrote: > On (28/01/16 16:25), Jeff Hallyburton wrote: > >We saw the following happen on a system today, and wanted to follow up: > > > >System became unresponsive to ssh logins with the error: > > > >ssh -v incentives01 > > > //snip > > ># cat /var/log/sssd/sssd.log > > > >(Thu Jan 28 20:15:56 2016) [sssd] [mt_svc_sigkill] (0x0010): [enervee.com > ] > >is not responding to SIGTERM. Sending SIGKILL. > > > >(Thu Jan 28 20:16:27 2016) [sssd] [talloc_log_fn] (0x0010): talloc: access > >after free error - first free may be at src/monitor/monitor.c:2760 > > > > > >(Thu Jan 28 20:16:27 2016) [sssd] [talloc_log_fn] (0x0010): Bad talloc > >magic value - access after free > > > There was a crash in sssd. It might explain why you cannot login. > Which version of sssd do you have? > > LS >
-- 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