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

Bug #1776809 reported by Roberto
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

winbind does not start

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jun 10 08:43:15 2018
ErrorMessage: installed winbind package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-07-25 (687 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 nautilus 1:3.26.3-0ubuntu4
 gvfs 1.36.1-0ubuntu1
SambaClientRegression: Yes
SourcePackage: samba
Title: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-21 (23 days ago)

Revision history for this message
Roberto (r-dos-ramos) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Thanks for filing this bug in Ubuntu.

From the logs:
Setting up winbind (2:4.7.6+dfsg~ubuntu-0ubuntu2) ...
Job for winbind.service failed because the control process exited with error code.
See "systemctl status winbind.service" and "journalctl -xe" for details.
invoke-rc.d: initscript winbind, action "restart" failed.
● winbind.service - Samba Winbind Daemon
   Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-06-10 08:43:06 -04; 33ms ago
     Docs: man:winbindd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 6229 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 6229 (code=exited, status=1/FAILURE)

jun 10 08:43:06 ubuntu-desktop systemd[1]: Starting Samba Winbind Daemon...
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
jun 10 08:43:06 ubuntu-desktop systemd[1]: winbind.service: Failed with result 'exit-code'.
jun 10 08:43:06 ubuntu-desktop systemd[1]: Failed to start Samba Winbind Daemon.
dpkg: error processing package winbind (--configure):
 installed winbind package post-installation script subprocess returned error exit status 1

Unfortunately that doesn't tell why winbind failed to start, only that it did. Since there is no smb.conf attached to this bug, I can't check that it does not contain errors.

I suggest the following:
- inspect the logs in /var/log/samba/log* to see if they have more information about the problem. These logs were not attached to this bug so I can't check.
- inspect your smb.conf for syntax errors, specially around the winbind parameters. Or run the testparm utility to do some basic checks for you.

I will mark this bug as incomplete until more information becomes available. Thanks.

Changed in samba (Ubuntu):
status: New → Incomplete
Revision history for this message
Roberto (r-dos-ramos) wrote :

Hello Andreas,

Checking with testparm as you recommended showed me the problem,

Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts' for parameter 'name resolve order'
Error loading services.

The problem was in the line "name resolve order" of the smb.conf file. It had this:

name resolve order = bcast hosts lmhosts wins

I deleted the word "hosts" and now winbind starts ok. Don't really know why this happened (the "hosts" word I mean), since I haven't messed with smb.conf in quite a while, but since 18.04 upgrade I had this issue, but it seems to be fixed now.

Thanks for your help.

PS: i attached the smb.conf just in case you want to check.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for your reply Roberto - glad Andreas could help you, but in that case this is more a support case than a bug.
Marking the bug as invalid (no need to wait for it to expire).

Changed in samba (Ubuntu):
status: Incomplete → Invalid
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.