Samba 4 failed to update with ProvisioningError: guess_names: 'realm =' was not specified in supplied /etc/samba/smb.conf. Please remove the smb.conf file and let provision generate it

Bug #857394 reported by QVELLC
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
samba4 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Downloading an update package samba4 failed to download

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: samba4
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 23 09:20:34 2011
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: samba4
Title: package samba4 4.0.0~alpha17~git20110807.dfsg1-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)

Revision history for this message
QVELLC (ceo-3) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba4 (Ubuntu):
status: New → Confirmed
Robert Roth (evfool)
summary: - package samba4 4.0.0~alpha17~git20110807.dfsg1-1ubuntu1 failed to
- install/upgrade: ErrorMessage: subprocess installed post-installation
- script returned error exit status 1
+ Samba 4 failed to update with ProvisioningError: guess_names: 'realm ='
+ was not specified in supplied /etc/samba/smb.conf. Please remove the
+ smb.conf file and let provision generate it
Revision history for this message
mebuntu (salsa-temps) wrote :

This affects me using amd64 version of Oneiric

Revision history for this message
Rhubeni Lopes de Andrade (rhube-itsasecret) wrote :

As I reported in bug # 860981 (a duplicate of this):

To fix this bug, set the value 'realm =' to a valid value in smb.conf
The failure occurred precisely because of that generated by the installation smb.conf leave this value blank.

After making this setting, just try to start the service. That done, with me it worked without problems.
The parameter must be a valid domain.

Revision history for this message
Dallman Ross (spamless) wrote :

This has been driving me nuts for a week too. Glad to see this here. However, I'm still not sure what to set it to. I don't run a domain on my host. The workgroup already is named something (other than "workgroup"). Since I'm not advertising my host as a valid domain, how can I set "realm" to a valid domain?

Be that as it may, I did get samba4 to work the other day after much screwing around. And I don't even have a "realm =" phrase in the current smb.conf. But the error still makes itself heard when update-manager runs.

Revision history for this message
Iain Alexander (netean) wrote :

don't know if this is correct in terms of how the code/samba works, but this fixed it for me (adding realm on its own did NOT)

This is the start of my smb.conf
I removed the reference to the domain controller and added security = share

It's now stopped erroring all the time
Note: my workgroup is unimaginatively called "One"

# Global parameters
[global]
 workgroup = One
 realm = One
 netbios name = KLaptop11-10
 security = share

[netlogon]
 path = /var/lib/samba/sysvol/scripts
 read only = No

[sysvol]
 path = /var/lib/samba/sysvol
 read only = No

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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