I have given the package in comment #13 a try. it takes a couple weeks
for the problem to get bad enough to trip the monitor we have set up for
it, but today is that day:

```
$ dpkg -l | grep sssd
ii  sssd                                1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- metapackage
ii  sssd-ad                             1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- Active Directory back end
ii  sssd-ad-common                      1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- PAC responder
ii  sssd-common                         1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- common files
ii  sssd-ipa                            1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- IPA back end
ii  sssd-krb5                           1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- Kerberos back end
ii  sssd-krb5-common                    1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- Kerberos helpers
ii  sssd-ldap                           1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- LDAP back end
ii  sssd-proxy                          1.13.4-1ubuntu1.11~ppa1                 
   amd64        System Security Services Daemon -- proxy back end
```

we see today:

```
$ ps axf | grep sssd_be
15972 pts/0    S+     0:00              \_ grep --color=auto sssd_be
  445 ?        S      0:08  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
65342 ?        S      0:03 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
29323 ?        S      0:01 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 4004 ?        S      0:00  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
58378 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
58502 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
29326 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 3000 ?        S      0:00  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
29354 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 3703 ?        S      0:00  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
29481 ?        S      0:01 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 3304 ?        S      0:00  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
48643 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 2592 ?        S      0:00  \_ /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
49513 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 2726 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 2934 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 3169 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
 4395 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sssd/sssd_be --domain 
starbucks.net --uid 0 --gid 0 --debug-to-files
```

So as of this package problem still exists.

Additionally, I hear from my infrastructure departments this is a
companywide problem, it is not specific to my nodes. It apparently has
something to do with  AD sites with multiple sub-domains.

We've tried other config fixes like
```
ad_enabled_domains = starbucks.net
ignore_group_members = true
```

But nothing helps. Our RHEL and CentOS boxes have 1.16 which contain the
fix, they do not experience this problem. However we're not using as
many of those boxes anymore.

it will be sometime before our 18.04 image is ready for deployment, so
it is discouraging that this is WONTFIX.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676328

Title:
  sssd_be is leaking memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1676328/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to