package samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Fabio Selvatico]

original samba.conf used initially and samba did not start, so changed samba.conf to be simpler and readable. After the modification of samba.conf samba started succesfully, but at reboot appears the system error reported here.
My initial scope was to have samba client working OK in order to use an smb resource shared by my modem/router via USB and the smb service enabled on that usb disk connected to the modem/router. Other clients (windows and previous ubuntu 14) connected OK with this smb resource.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.11
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Oct 16 13:08:15 2017
ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
InstallationDate: Installed on 2017-10-10 (7 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
NmbdLog:

OtherFailedConnect: Yes
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.11 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Andreas Hasenack (ahasenack)]

Thanks for filing this bug in Ubuntu.

This crash report might come from the previous start attempt, when you had an incorrect smb.conf file. The smb.conf file attached to this bug right now is correct syntatically, even though testparm(1) gives some warnings about it.

Looking at the attached smb.conf file, if that is still the file you have on that machine, I can see that you are specifying explicit network interfaces for samba to use: lo and enp6s0. If that enp6s0 interface is not up by the time samba is starting, samba won't start. That could happen, for example, if this is a desktop system and that network interface is managed by network-manager. It could only be activated after you login.

The attached logs unfortunately don't tell why the service failed to start. If you could please attach the log files from /var/log/samba/ we might be able to tell why that happened.

Is the service running normally now?

Thanks

[Launchpad Janitor (janitor)]

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