package samba 2:4.4.5+dfsg-2ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[nghtwlkr]

Cannot get samba to share to my network. tried a fresh install which failed to start

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: samba 2:4.4.5+dfsg-2ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 samba:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Nov 29 21:28:58 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-11-29 (0 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
NmbdLog:

RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.1
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

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

[Joshua Powers (powersj)]

From log:

Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory

[Joshua Powers (powersj)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This looks similar to LP: #1610361, however in this case it is fatal as the service fails to start (unless I'm following the wrong error message).

On a clean install of Yakkety with the same version of samba (2:4.4.5+dfsg-2ubuntu5) I also get the message, however it is non-fatal and the service starts as expected. I dumped in your smb conf that is attached, and restarted just fine as well.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

[Launchpad Janitor (janitor)]

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