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

[Franco Runza]

Sorry but my knowlege of Linux is quite restricted . I am not able to aid you more than this.
Best Greetings Franco runza

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Feb 2 08:02:40 2017
DpkgHistoryLog:
 Start-Date: 2017-02-02 08:01:56
 Commandline: aptdaemon role='role-commit-packages' sender=':1.106'
 Upgrade: libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.1, 3.4.10-4ubuntu1.2), ntfs-3g:amd64 (1:2015.3.14AR.1-1build1, 1:2015.3.14AR.1-1ubuntu0.1), humanity-icon-theme:amd64 (0.6.10, 0.6.10.1), libgnutls30:amd64 (3.4.10-4ubuntu1.1, 3.4.10-4ubuntu1.2), libxpm4:amd64 (1:3.5.11-1, 1:3.5.11-1ubuntu0.16.04.1)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-06-23 (589 days ago)
InstallationMedia: It
NmbdLog:

RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-22 (285 days ago)
WindowsFailedConnect: Yes

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Hi,
it seems that you have samba installed but not (or bad) configured.
That you can see that the services smbd/nmbd won't start in your log:
  Fev 02 08:02:40 hostname systemd[1]: Failed to start LSB: start Samba SMB/CIFS daemon (smbd).
  Fev 02 08:02:40 hostname systemd[1]: smbd.service: Failed with result 'exit-code'.

Now on the upgrade of these packages they get restarted to pick up the fixes, and due to the likely broken config they can't start. Which in turn makes the upgrade go bad.

Either start checking what exactly fails with:
systemctl status smbd.service
systemctl status nmbd.service

And fix up whatever the issue is.

Or - if maybe you don't even want samba as a service to share files ignore that your config is broken and uninstall it. I've often seen bugs like that by people playing with it in the past, but then ignoring it as they don't want it. But later on on upgrade an issue like this is popping up. Maybe yours is such a case.

[Launchpad Janitor (janitor)]

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

[jignesh (ethical16)]

Sorry My Knowledge on software side is very limited so will not be able to put it into words. But Cannot connect to a printer on a windows servor is the issue which was possible in earlier versions.