[Bug 1776809] Re: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1

Andreas Hasenack andreas at canonical.com
Thu Jun 14 13:53:53 UTC 2018


Thanks for filing this bug in Ubuntu.

>From the logs:
Setting up winbind (2:4.7.6+dfsg~ubuntu-0ubuntu2) ...
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 "restart" failed.
● winbind.service - Samba Winbind Daemon
   Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-06-10 08:43:06 -04; 33ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 6229 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 6229 (code=exited, status=1/FAILURE)

jun 10 08:43:06 ubuntu-desktop systemd[1]: Starting Samba Winbind Daemon...
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Failed with result 'exit-code'.
jun 10 08:43:06 ubuntu-desktop systemd[1]: Failed to start Samba Winbind Daemon.
dpkg: error processing package winbind (--configure):
 installed winbind package post-installation script subprocess returned error exit status 1

Unfortunately that doesn't tell why winbind failed to start, only that
it did. Since there is no smb.conf attached to this bug, I can't check
that it does not contain errors.

I suggest the following:
- inspect the logs in /var/log/samba/log* to see if they have more information about the problem. These logs were not attached to this bug so I can't check.
- inspect your smb.conf for syntax errors, specially around the winbind parameters. Or run the testparm utility to do some basic checks for you.

I will mark this bug as incomplete until more information becomes
available. Thanks.

** Changed in: samba (Ubuntu)
       Status: New => Incomplete

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

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

Status in samba package in Ubuntu:
  Incomplete

Bug description:
  winbind does not start

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 10 08:43:15 2018
  ErrorMessage: installed winbind package post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2016-07-25 (687 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   nautilus 1:3.26.3-0ubuntu4
   gvfs     1.36.1-0ubuntu1
  SambaClientRegression: Yes
  SourcePackage: samba
  Title: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (23 days ago)

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



More information about the foundations-bugs mailing list