nmbd hangs on service start if only the loopback interface is configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Debian) |
Fix Released
|
Unknown
|
|||
samba (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
dist-upgrade from 16.04.1 to 16.10. Removed/purge package to finish upgrade and then tried to install again with same error.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: samba (not installed)
ProcVersionSign
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
samba:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Thu Oct 20 10:54:15 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-09-20 (396 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageV
nautilus 1:3.20.3-1ubuntu3
gvfs 1.28.2-1ubuntu2
SambaClientRegr
SourcePackage: samba
Title: package samba (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-10-20 (1 days ago)
Changed in samba (Debian): | |
status: | Unknown → New |
Changed in samba (Debian): | |
status: | New → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
I am able to reproduce this as follows:
lxc launch ubuntu:yakkety samba-test
lxc exec samba-test bash
apt-get update && apt-get -y install samba
systemctl stop nmbd
ifdown eth0
systemctl start nmbd
It seems that nmbd hangs indefinitely waiting on a network interface, even if the loopback interface is up.
I think this is a bug because laptop users may have samba installed but don't always have a network available (apart from loopback).