xenial verification:
Reproducing the crash:
ubuntu@xenial-sssd-1684295:~$ pidof sssd_be
3516
ubuntu@xenial-sssd-1684295:~$ id localuser
(stuck for 30s or more)
uid=1001(localuser) gid=1001(localuser) groups=1001(localuser)
syslog shows the crash:
Nov 13 13:05:55 xenial-sssd-1684295 systemd[1]:
@pam-s, as soon as you can confirm this patch fixes your problem (feel
free to use my PPA packages), please let us know so we can proceed with
the SRU.
My test case reproduces the segfault, but I would like to be sure it
also fixes it in your environment before continuing.
Thanks again
**
** Description changed:
[Impact]
+ In this particular configuration, when ldap_rfc2307_fallback_to_local_users
is set to true in /etc/sss/sssd.conf and a local user is a member of an ldap
group and does not exist in the directory (other scenarios are possible), the
sssd_be process segfaults
It's only xenial that is affected, that is, version 1.13.4 and perhaps
earlier. Trusty, zesty and higher are OK.
** Description changed:
- This is Ubuntu 16.04.2 LTS
+ [Impact]
- sssd is configured to connect to two domains, our TPAD directory and
- Active Directory. sssd starts up at boot
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
This PPA has my test packages:
https://launchpad.net/~ahasenack/+archive/ubuntu/sssd-bad-initgroups-
results-1684295/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1684295
Title:
I got a small reproducer case. With a simple "id " command I get
sssd_be to segfault, and with the above patch applied it no longer
segfaults and also produces the correct result. I'll use that for the
SRU test plan.
--
You received this bug notification because you are a member of Ubuntu
Server
I believe this is the upstream issue:
https://pagure.io/SSSD/sssd/issue/3045
The patch is
https://pagure.io/SSSD/sssd/c/5a0fb268e836e600d864ded7de5d935946ae6c61
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => High
** Tags
Thanks, I can track this down more easily now.
(gdb) bt
#0 sysdb_attrs_get_el_ext (attrs=attrs@entry=0x0,
name=name@entry=0x7f1e14bb504c "stamp", alloc=alloc@entry=true,
el=el@entry=0x7ffc041e48a8) at ../src/db/sysdb.c:326
#1 0x7f1e2d283d0d in sysdb_attrs_get_el (attrs=attrs@entry=0x0,
I think the best way forward here is to get a core dump, so we can have
a better idea of where the crash is happening.
I induced a crash in my test sssd container, and since I have apport installed,
a crash file was produced in /var/crash:
# ll /var/crash/
total 644
drwxrwxrwt 2 root root
Looking at this again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1684295
Title:
sssd fails with 'Exiting the SSSD. Could not restart critical service
[tpad].
To manage
Thanks for these
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1684295
Title:
sssd fails with 'Exiting the SSSD. Could not restart critical service
[tpad].
To manage
Continuing on this bug is fine, thanks for getting back to us with a
simplified configuration file. I reopened the bug so that it will be
picked up again.
** Changed in: sssd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks for filing this bug in Ubuntu.
This one will be a bit complex for me to reproduce locally, as your
sssd.conf file has a lot of customizations and multiple servers for each
domain. It would be best if we could reduce this complexity as much as
possible and still reproduce the problem.
Have
14 matches
Mail list logo
