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
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+
ProcVersionSign
Uname: Linux 4.4.0-137-generic i686
NonfreeKernelMo
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
RelatedPackageV
nautilus 1:3.18.
gvfs 1.28.2-
SambaClientRegr
SourcePackage: samba
Title: package winbind 2:4.3.11+
UpgradeStatus: Upgraded to xenial on 2017-12-25 (292 days ago)
tags: | removed: need-duplicate-check |
Thanks for filing this bug in Ubuntu.
The winbind service logged this error: d/winbind; bad; vendor preset: enabled) sysv-generator( 8) /etc/init. d/winbind start [0;1;31m( code=exited, status= 1/FAILURE) [0m
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.
[0;1;31m●[0m winbind.service - LSB: start Winbind daemon
Loaded: loaded (/etc/init.
Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-10-13 18:35:27 BST; 20ms ago
Docs: man:systemd-
Process: 9353 ExecStart=
Oct 13 18:35:23 Pinky winbind[9353]: Failed to create /var/log/ samba/cores ...00 samba/cores ...00 d.service: Control process exited, ...=1[0m d.service: Unit entered failed state.[0m d.service: Failed with result 'exit...'.[0m
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/
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]: [0;1;39mwinbin
Oct 13 18:35:27 Pinky systemd[1]: [0;1;31mFailed to start LSB: start Winbind daemon.[0m
Oct 13 18:35:27 Pinky systemd[1]: [0;1;39mwinbin
Oct 13 18:35:27 Pinky systemd[1]: [0;1;39mwinbin
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: samba/cores samba/cores/ smbd samba/cores/ nmbd
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/
36688 1 drwx------ 2 root root 2 Jul 11 18:44 /var/log/
36698 1 drwx------ 2 root root 2 Jul 11 18:44 /var/log/