package samba-common-bin 2:4.13.5+dfsg-2ubuntu2 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1

Bug #1943994 reported by RonRN18
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was having a new problem with samba no longer working on 21.04 with latest updates. Apparently, a previous update on 21.04 borked samba. As this is on a non-essential VM, I snapshoted prior to performing a "sudo do-release-upgrade -d", to try out the latest daily build of 21.10. This is the result.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: samba-common-bin 2:4.13.5+dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CIFSMounts:

CasperMD5CheckResult: pass
Date: Fri Sep 17 10:02:52 2021
ErrorMessage: installed samba-common-bin package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-08-24 (24 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421)
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt 2.3.9
SambaClientRegression: No
SourcePackage: samba
Title: package samba-common-bin 2:4.13.5+dfsg-2ubuntu2 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to impish on 2021-09-17 (0 days ago)

Revision history for this message
RonRN18 (bigron) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

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

Going through the logs was not enough for me to identify what is happening. Could you please also provide the logs from the samba service? Also any customized config you might have.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
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".

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
Glenn Ray Pace (ray-pace) wrote :

The do-release-upgrade installer reported this issue as a bug. I am completing the bug report that in upgrader opened.

Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

As per the provided DpkgTerminalLog.txt, I can see:

Setting up samba-common-bin (2:4.13.5+dfsg-2ubuntu2) ...
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts' for parameter 'name resolve order'
Error loading services.
dpkg: error processing package samba-common-bin (--configure):
 installed samba-common-bin package post-installation script subprocess returned error exit status 1

In the smb.conf man page, you will find that the possible values for "name resolve order" are: "lmhosts", "host", "wins" and "bcast". In this case, it really seems that there is a configuration error, with a value of "hosts" set in that field.

Since the samba-common-bin postinst script does check for issues in the configuration file, your installation fails.

Changing that value from "hosts" to "host" may suffice to fix your problem.

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.