package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

Bug #1787202 reported by Charles Marslett
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was not accessing the shared volume, I was doing a project source code build (entirely local) when the message popped up. I did have two large shared volumes open, though.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CIFSMounts:

Date: Wed Aug 15 06:50:22 2018
ErrorMessage: installed samba package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-19 (56 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Charles Marslett (charles-marslett) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Joshua Powers (powersj) wrote :

From terminal log:

Aug 15 06:50:21 T7600 nmbd[13617]: bind failed on port 137 socket_addr = 192.168.3.254.
Aug 15 06:50:21 T7600 nmbd[13617]: Error = Cannot assign requested address

Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to file a bug report.

Looks like something is already running on that port or some other issue was preventing the service from starting.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Changed in samba (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in samba (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.