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

[Eduardo Santos]

instalação

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.24
ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200
Uname: Linux 4.4.0-170-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Wed Dec 11 20:36:29 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2019-11-30 (17 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
NmbdLog:

RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt 1.2.32
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UbuntuFailedConnect: Yes
UpgradeStatus: No upgrade log present (probably fresh install)

[Eduardo Barretto (ebarretto)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Rafael David Tinoco (rafaeldtinoco)]

I'm afraid that provided information here is not enough for us to know why samba couldn't be started during upgrade time.

From:

https://launchpadlibrarian.net/456135925/DpkgTerminalLog.txt

Setting up samba (2:4.3.11+dfsg-0ubuntu0.16.04.24) ...
Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript smbd, action "start" failed.
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Qua 2019-12-11 20:36:29 -03; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12042 ExecStart=/etc/init.d/smbd start (code=exited, status=1/FAILURE)

Dez 11 20:36:28 edutec systemd[1]: Starting LSB: start Samba SMB/CIFS daemo.....
Dez 11 20:36:29 edutec smbd[12042]: * Starting SMB/CIFS daemon smbd
Dez 11 20:36:29 edutec smbd[12042]: ...fail!
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Control process exited, co...=1
Dez 11 20:36:29 edutec systemd[1]: Failed to start LSB: start Samba SMB/CIF...).
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Unit entered failed state.
Dez 11 20:36:29 edutec systemd[1]: smbd.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package samba (--configure):
 subprocess installed post-installation script returned error exit status 1

We dont have the exact reason why the daemon couldn't be started. Since this is an upgrade, I doubt Eduardo has a way to reproduce this again... but, if you do, please try checking journal logs for smbd.service and see what was the reason it couldn't start.

I'm marking this as incomplete. If anyone else ever face this again, please provide more information on the exact error for the daemon not to have started.

Thank you.

[Launchpad Janitor (janitor)]

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