Again the sssd got crashed, not seeing any issue with the machine,System
resources were/are free …less than 30% utilized…
Aug 7 10:06:12 gamma14 sssd: Killing service [myOrg], not responding to pings!
Aug 7 10:06:22 gamma14 systemd[1]: sssd.service: Main process exited,
code=dumped, status=6/ABRT
Aug 7 10:06:22 gamma14 sssd[pam]: Shutting down
Aug 7 10:06:22 gamma14 sssd[nss]: Shutting down
Aug 7 10:06:24 gamma14 systemd[1]: sssd.service: Unit entered failed state.
Aug 7 10:06:24 gamma14 systemd[1]: sssd.service: Failed with result
'core-dump'.
Aug 7 10:09:02 gamma14 CRON[1031]: (root) CMD ( [ -x
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Aug 7 10:10:01 gamma14 CRON[1586]: (root) CMD (/usr/sbin/icsisnap
/var/lib/icsisnap)
root@gamma14:/var/log/sssd# cat sssd.log
(Fri Aug 7 10:06:12 2020) [sssd] [talloc_log_fn] (0x0010): Bad talloc magic
value - unknown value
I found these logs, except these no other suspicious logs found
anywhere.
Core dumps is not generated because ,
|10:47:56|kamals@gamma14:[crash]> ulimit -a
core file size (blocks, -c) 0
core file size of "0" means that core files won't get generated at all.
Please confirm "Bad talloc magic value - unknown value" if this is the issue
and what does it mean ?
** Changed in: sssd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883614
Title:
sssd got killed due to segfault in ubuntu 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1883614/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
