) [sssd] [talloc_log_fn] (0x0010): Bad talloc magic value - unknown value
Bug #1871321 reported by
Luis Gomez
This bug report is a duplicate of:
Bug #1883614: sssd got killed due to segfault in ubuntu 16.04 .
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sssd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Xenial |
New
|
Undecided
|
Unassigned |
Bug Description
Once a month the server OS crashes and when users are trying to log in it will deny access. After reboot the problem resolves itself.
Error
[sssd] [talloc_log_fn] (0x0010): Bad talloc magic value - unknown value
Kernel
4.4.0-31-generic
Updates available
377 packages can be updated.
227 updates are security updates.
New release '18.04.4 LTS' available.
- Is there a way to know the risks to update to a newer version of sssd?
- Can you please advise us on how to tackle this usse?
Kr,
Luis Gomez
affects: | pkg-website → sssd (Ubuntu) |
To post a comment you must log in.
Hi Luis,
I can derive from your info in [2] that you are on Xenial, so I'll mark that for now.
Do you happen to know if it also occurs on other releases?
Two things will commonly be needed to get any further on this.
1. your setup details, how did you setup sssd and your authentication exactly. Are there particular actions to trigger this bug or is it just time/logins that have to pass? If possible the best usually is if you are able to outline the steps needed to set up a clean new VM with Ubuntu to reach the bad state
2. Since it reports a crash is there any crash that you could report [1] ?
[1]: https:/ /help.ubuntu. com/community/ ReportingBugs# Reporting_ a_crash /answers. launchpad. net/ubuntu/ +question/ 689804
[2]: https:/
The message somehow felt familiar, but I couldn't find a case I touched that seemed like a full match. Looking further I found the old case I had in mind ... /bugs.launchpad .net/ubuntu/ +source/ sssd/+bug/ 1883614
=> https:/
I think I can mark this a dup and if you want you can chime in on the other bug that is already a few steps further in the debug-process but fell dead back then.