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

Bug #1797721 reported by Pinky
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Software Updater used to work perfectly but now it fails with the message in the summary.
When Software Updater informs me there are updates I now use 'Ubuntu Software' to do them as it completes without failing.
Can I remove Samba and all its components and reinstall it?
I have an NTFS partition which I can still read from Ubuntu.

I am using Ubuntu 16.04.5 LTS.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: winbind 2:4.3.11+dfsg-0ubuntu0.16.04.17
ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
Uname: Linux 4.4.0-137-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Sat Oct 13 18:35:27 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 nautilus 1:3.18.4.is.3.14.3-0ubuntu6
 gvfs 1.28.2-1ubuntu1~16.04.2
SambaClientRegression: Yes
SourcePackage: samba
Title: package winbind 2:4.3.11+dfsg-0ubuntu0.16.04.17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-12-25 (292 days ago)

Revision history for this message
Pinky (andytris) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Thanks for filing this bug in Ubuntu.

The winbind service logged this error:
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 - LSB: start Winbind daemon
   Loaded: loaded (/etc/init.d/winbind; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-10-13 18:35:27 BST; 20ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 9353 ExecStart=/etc/init.d/winbind start (code=exited, status=1/FAILURE)

Oct 13 18:35:23 Pinky winbind[9353]: Failed to create /var/log/samba/cores ...00
Oct 13 18:35:23 Pinky winbind[9353]: Unable to setup corepath for winbindd:...ss
Oct 13 18:35:23 Pinky winbind[9353]: invalid permissions on directory '/var...00
Oct 13 18:35:23 Pinky winbind[9353]: Failed to create /var/log/samba/cores ...00
Oct 13 18:35:23 Pinky winbind[9353]: Unable to setup corepath for winbindd:...ss
Oct 13 18:35:27 Pinky winbind[9353]: ...fail!
Oct 13 18:35:27 Pinky systemd[1]: winbind.service: Control process exited, ...=1
Oct 13 18:35:27 Pinky systemd[1]: Failed to start LSB: start Winbind daemon.
Oct 13 18:35:27 Pinky systemd[1]: winbind.service: Unit entered failed state.
Oct 13 18:35:27 Pinky systemd[1]: winbind.service: Failed with result 'exit...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package winbind (--configure):
 subprocess installed post-installation script returned error exit status 1

Unfortunately the messages are truncated, but it seems that you have incorrect permissions set in /var/log/samba. The full error can be displayed by running "sudo systemctl status winbind", or by inspecting /var/log/samba/log*.

The /var/log/samba directory structure should look like this:
    35114 9 drwxr-x--- 3 root adm 8 Jul 11 18:52 /var/log/samba/
    36687 1 drwx------ 4 root root 4 Jul 11 18:44 /var/log/samba/cores
    36688 1 drwx------ 2 root root 2 Jul 11 18:44 /var/log/samba/cores/smbd
    36698 1 drwx------ 2 root root 2 Jul 11 18:44 /var/log/samba/cores/nmbd

Changed in samba (Ubuntu):
status: New → Incomplete
Revision history for this message
Pinky (andytris) wrote :

Probably solved.
I have fixed the permissions and 2 updates have gone through without crashing out.
I looks like the fix has worked, thank you.
It remains a mystery how the permissions apparently spontaneously changed!
I will confirm again after some more substantial updates have gone through.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Ok, thanks for getting back to us with this information. I'll leave this bug in the "incomplete" state for the time being, and it will close itself if there is no future activity.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in samba (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.