sssd on zesty fails to start ( : Unavailable)

Bug #1664785 reported by Omen Wild on 2017-02-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sssd (Ubuntu)

Bug Description

I have a fresh install of zesty (alpha 2, but full dist-upgrade as of this afternoon), and sssd 1.15.0-3ubuntu2 fails to launch. systemctl reports:

Feb 14 16:20:05 phys-adtest-zesty systemd[1]: Starting System Security Services Daemon...
Feb 14 16:20:05 phys-adtest-zesty sssd[1831]: ldb_init_module() in ../source4/dsdb/samdb/ldb_modules/password_hash.c version[1.1.27]: gpgme_check_version(1.8.0) not available, gpgme_check_version(NULL) => '1.7.
Feb 14 16:20:05 phys-adtest-zesty sssd[1831]: ldb: failed to initialise module /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/ : Unavailable
Feb 14 16:20:05 phys-adtest-zesty sssd[1831]: ldb: failed to initialise module /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba : Unavailable
Feb 14 16:20:05 phys-adtest-zesty sssd[1831]: SSSD couldn't load the configuration database [5]: Input/output error.

The library exists, and strace shows it being opened. A few system calls later, /usr/lib/x86_64-linux-gnu/ is opened and then the gpgme_check_version() error is printed and sssd exits.

libgpgme11:amd64 1.7.0-1, the newest available in zesty, is installed. I am unable to find a PPS with a newer libgpgme to test with.


ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: sssd 1.15.0-3ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Tue Feb 14 16:24:45 2017
InstallationDate: Installed on 2017-02-14 (0 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
 PATH=(custom, no user)
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)

Hi Omen,
thank you for your report and your help to make Ubuntu better!

I was trying to set up a local sssd and krb5-kdc following and some experiments to reproduce.

But is seems my kerberos-foo isn't enough.

If you happen to have no external dependency to a real AD, but instead could provide some steps to reproduce on just a zesty system that might help a lot.

On the .so file you listed, I happened to see that this exists for me but is not owned by a package.
Maybe it is created on install:
dpkg -S /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/
dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/
root@zesty-tests:~# ll /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/
-rw-r--r-- 1 root root 59304 Jan 27 01:20 /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/samba/

Is it the same case for you?

Sorry I can't help, I really need to prep-script a AD/sssd/samba setup once I find time.
This could be useful every now and then.

Hoping for the next who comes by triaging.

Timo Aaltonen (tjaalton) wrote :

I guess this just needs a rebuild against the new samba/ldb.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sssd - 1.15.0-3ubuntu4

sssd (1.15.0-3ubuntu4) zesty; urgency=medium

  * Rebuild against new samba/libldb. (LP: #1664785)

 -- Timo Aaltonen <email address hidden> Sun, 05 Mar 2017 13:30:40 +0200

Changed in sssd (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers