failed to install via apt-get... package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1

[Andrew Van Donselaar]

i ran apt-get -y install libnss-winbind libpam-winbind and got the error listed in the summary

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 winbind:amd64: Install
 libnss-winbind:amd64: Install
 libpam-winbind:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Sep 24 12:15:34 2018
ErrorMessage: installed winbind package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-09-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3ubuntu0.1
SambaClientRegression: No
SourcePackage: samba
Title: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Andreas Hasenack (ahasenack)]

Thanks for filing this bug in Ubuntu.

The attached logs don't help much:
Job for winbind.service failed because the control process exited with error code.
See "systemctl status winbind.service" and "journalctl -xe" for details.
invoke-rc.d: initscript winbind, action "start" failed.
● winbind.service - Samba Winbind Daemon
   Loaded: loaded (/lib/systemd/system/winbind.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-09-24 12:15:34 CDT; 5ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 7936 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 7936 (code=exited, status=1/FAILURE)

Sep 24 12:15:34 LCBHS0363 systemd[1]: Starting Samba Winbind Daemon...
Sep 24 12:15:34 LCBHS0363 systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Sep 24 12:15:34 LCBHS0363 systemd[1]: winbind.service: Failed with result 'exit-code'.
Sep 24 12:15:34 LCBHS0363 systemd[1]: Failed to start Samba Winbind Daemon.

Could you please attach the samba and winbind logs from /var/log/samba/*, as well as your config file /etc/samba/smb.conf? The logs should have more information about the failure.

[Andreas Hasenack (ahasenack)]

btw, I took the same steps in a brand new bionic container, and winbind is running just fine in the end. It could be a configuration issue in your smb.conf.

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]