package samba 2:4.3.11+dfsg-0ubuntu0.16.04.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Franco Runza]

i don't khow , same problem as always

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.7
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 29 11:32:23 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-06-23 (736 days ago)
InstallationMedia: It
NmbdLog:

RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-22 (432 days ago)
WindowsFailedConnect: Yes

[Christian Ehrhardt  (paelzer)]

Hi Franco,
you seem to be affected by that issue for quite a while - unfortunately some of the logs that were attached are no more covering how it started :-/.

I'll give you the summary what happened and you can decide which way you want to go:

1. what is breaking
   On install/upgrade of the samba package it fails to restart the samba service
2. why is that required
   When updating a service the daemons have to be restarted to pick up the change.
   While doing so things can fail e.g. because the upgrade no more supports the old config, but
   actually that case is very rare.
3. what is happening more likely
   Most of the times these kind of issues occur if services are installed, but not properly
   configured. The users might have experimented with it but eventually didn't care and left it
   in a broken state so that the service isn't able to restart (e.g. broken config file)
4. Solution
   4a. fix the samba config so you can properly restart the service, very very likely the upgrade
       then works as well.
       $ systemctl restart smbd
       $ systemctl status smbd
       # once goot do your upgrades
   4b. if you didn't configure it, you likely don't care so you might as well just remove the
       package. Of course that will stop bothering about not being able to upgrade it.

Please pick your way to resolve, if you run into troubles along that set the bug back to new.

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

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

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then 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.

[Andreas Hasenack (ahasenack)]

Thanks for attaching smb.conf. The "share" parameter has an incorrect value:

$ testparm ./smb.conf
Load smb config files from ./smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
WARNING: Ignoring invalid value 'share' for parameter 'security'
Error loading services.

For this version of samba, "security = share" is no longer a valid configuration. Valid values for the "security" parameter are auto, user, domain or ads.

[Launchpad Janitor (janitor)]

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