package samba 2:4.6.7+dfsg-1ubuntu3.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Markward Kufleitner]

While Update through "sudo apt-get upgrade"

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: samba 2:4.6.7+dfsg-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Wed Nov 22 01:03:27 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5.1
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
TestparmExitCode: 0
Title: package samba 2:4.6.7+dfsg-1ubuntu3.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UbuntuFailedConnect: Yes
UpgradeStatus: Upgraded to artful on 2017-09-19 (63 days ago)

[Andreas Hasenack (ahasenack)]

Thanks for filing this bug in Ubuntu.

You have configured your smb.conf so that the samba services use specific network addresses and interfaces:
[global]
 bind interfaces only = Yes
 interfaces = 192.168.10.0/8 192.168.20.0/8 eth0

The nmbd service failed to bind to an address in the 192.168.20.0/8 network (that's a weird block, btw: 192.168.10.0/8 and 192.168.20.0/8 are the same because of the /8 mask and mean 192.0.0.0/8):
  bind failed on port 137 socket_addr = 192.168.20.0.
    Failed to open nmb socket on interface 192.168.20.0 for port 137. Error was Die angeforderte Adresse kann nicht zugewiesen werden
  STATUS=daemon failed to start: NMBD failed when creating subnet lists, error code 13

You should make sure that:
a) the CIDR is what you want: you are specifying 192.0.0.0/8 essentially
b) the listed interface exists when samba starts up: eth0
c) once you sorted out (a) above, also make sure that the network is available when samba starts

Please verify your configuration as per above and try again:
sudo apt update
sudo apt -f install

I'll leave this bug in the "incomplete" state until then.

Thanks!

[Markward Kufleitner (c-infv-9)]

I purged samba and all related packages and deleted smb.conf and reinstalled samba. Now all is working like it should.

I have two Fritz!Boxes tied together over VPN, one network is 192.168.10.0 und the other 192.168.20.0. My intention was to have samba access to windows boxes in 192.168.20.0 network too. But that never worked out.

So it is right, that this bug report was because of a faulty smb.conf, so it can be closed now.

The problem of my two networks I have to figure out by myself.

[Andreas Hasenack (ahasenack)]

Thanks for getting back to us with this explanation, much appreciated.