[Bug 1699019] Re: package winbind 2:4.5.8+dfsg-0ubuntu0.17.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

ChristianEhrhardt 1699019 at bugs.launchpad.net
Fri Jun 23 08:14:56 UTC 2017


>From the log:
Setting up winbind (2:4.5.8+dfsg-0ubuntu0.17.04.2) ...
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; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-06-20 11:06:03 IST; 24ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 29259 ExecStart=/usr/sbin/winbindd $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 29259 (code=exited, status=1/FAILURE)

Jun 20 11:06:03 abhishek winbindd[29259]: invalid permissions on directory '…700
Jun 20 11:06:03 abhishek winbindd[29259]: Failed to create /var/log/samba/co…700
Jun 20 11:06:03 abhishek winbindd[29259]: Unable to setup corepath for winbi…ory
Jun 20 11:06:03 abhishek winbindd[29259]: invalid permissions on directory '…700
Jun 20 11:06:03 abhishek winbindd[29259]: Failed to create /var/log/samba/co…700
Jun 20 11:06:03 abhishek winbindd[29259]: Unable to setup corepath for winbi…ory


Unfortunately that output got trimmed, but on your system you should get a better readable one via
$ systemctl winbind status

You should then try to fixx up your local configuration - as it seems
some non-default directory configurations were set.

>From what I can read there is seems like a broken setup in regard to some related paths.
The history of dpkg mentions winbind was installed but an upgrade on "2017-06-02  10:12:11" failed.

Was winbind installed and configured fine and runnign before that?
Because if it was installed and not properly configured then all following upgrades will fail as they need to restart the service on upgrade.
So if it was never working (or was not needed) please remove the package - that will unblock your upgrades in general to pass correctly then.

-- 
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/1699019

Title:
  package winbind 2:4.5.8+dfsg-0ubuntu0.17.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in samba package in Ubuntu:
  Incomplete

Bug description:
  Hi please help me regarding this bug to get solved.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: winbind 2:4.5.8+dfsg-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jun 20 11:06:03 2017
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationDate: Installed on 2016-07-05 (349 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package winbind 2:4.5.8+dfsg-0ubuntu0.17.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UbuntuFailedConnect: Yes
  UpgradeStatus: No upgrade log present (probably fresh install)

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



More information about the foundations-bugs mailing list