On 06/19/2015 01:35 PM, Steve Ankeny wrote:
On 06/13/2015 05:02 PM, Steve Ankeny wrote:
. . . doing a bit of research . . .
Others have had this error in the past. The following looks interesting.
Samba: subprocess post-installation script returned error exit
status 1
<http://languor.us/samba-subprocess-post-installation-script-returned-error-exit-status-1>
The suggestion above was to "create a blank smb.conf in /etc/samba,
then purge and reinstall samba"
During the upgrade, it suggested I keep my current 'smb.conf' I
currently have the 'dcerpc' lines commented. Perhaps, I should
uncomment those since they call the OpenChange and 'mapiproxy' functions?
I inserted the 'dcerpc' comments as I was unable to login after a
reboot of my 'samba-ad-dc,' and the problem was perceived to be the
calls to a 'broken' OpenChange (which applies to OpenChange before
this upgrade)
Using a blank 'smb.conf' might not find my domain parameters to
complete the configuration.
If I purge my 'samba' db, will it delete all my user and machine
accounts? That's a worry!
Another suggestion might be to install an upgrade between my current
'samba' file and the Inverse package. I've been concerned about the
installed version since before starting this upgrade to Samba 4.1.18
Are there any suggestions? Has anyone else ran into this situation?
Should I ask the Samba list?
On 06/13/2015 12:01 PM, Steve Ankeny wrote:
Problems seem to start here . . .
dpkg: error processing package samba (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of winbind:
winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however:
Package samba is not configured yet.
I asked the Samba mailing list, and they suggested the problem was the
differences between the Ubuntu and Inverse packages. They suggested I
change the installed status and attempt to "force" installation.
That failed, however, and now I wonder where to go from here?
Is 'winbind' actually needed for my installation? It is not running
on my Samba-AD-DC
adam@sogo:~$ sudo initctl list | egrep 'samba|smb|mnb|winbind'
winbind stop/waiting
smbd stop/waiting
reload-smbd stop/waiting
samba-ad-dc start/running, process 807
here are the packages installed on my server
adam@sogo:~$ sudo dpkg-query -l | egrep 'samba|smb|nmb|winbind'
ii libnss-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii libpam-winbind:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii libsmbclient:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii libwbclient0:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii python-samba 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-common 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-common-bin 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-dev 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-dsdb-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-libs:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii samba-vfs-modules 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii smbclient 2:4.1.6+dfsg-1ubuntu2.14.04.7
ii winbind 2:4.1.6+dfsg-1ubuntu2.14.04.7
Since the suggestion above is to purge Samba, it would be better to
purge 'winbind' instead.
The error involves the post-install script which the Samba mailing
list considers the problem.
Is there a source for the Samba 2:4.1.18+dfsg packages with a
different post-install script? Or, will purging the 'winbind'
packages resolve my issue with upgrading my Samba-AD-DC installation?
Any suggestions?
thx
Rowland Penny recreated my problem in a VM (similar to my setup)
here's the content of his e-mail --
OK, there appears to be something wrong with the inverse samba packages,
I created a VM, installed latest Ubuntu 14.04 server, updated this,
installed samba:
apt-get install samba samba-common samba-common-bin samba-dev
samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind
python-samba libnss-winbind libpam-winbind libsmbclient libwbclient0
didn't do anything else except added:
deb http://inverse.ca/ubuntu-nightly trusty trusty
To /etc/apt/sources.list
ran 'apt-get update' and then 'apt-get upgrade'
This lead to:
The following packages have been kept back:
libldb-dev libldb1 libnss-winbind libpam-winbind libsmbclient
libwbclient0
linux-generic-lts-utopic linux-headers-generic-lts-utopic
linux-image-generic-lts-utopic python-ldb python-samba samba
samba-common
samba-common-bin samba-dev samba-dsdb-modules samba-libs
samba-vfs-modules
smbclient winbind
The following packages will be upgraded:
libparse-pidl-perl libtalloc-dev libtalloc2 libtdb-dev libtdb1
libtevent0
python-talloc python-tdb tdb-tools
9 to upgrade, 0 to newly install, 0 to remove and 20 not to upgrade.
Need to get 468 kB of archives.
After this operation, 253 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Installed the packages and then ran 'apt-get update' and then 'apt-get
upgrade' again
Calculating upgrade... Done
The following packages have been kept back:
libldb-dev libldb1 libnss-winbind libpam-winbind libsmbclient
libwbclient0
linux-generic-lts-utopic linux-headers-generic-lts-utopic
linux-image-generic-lts-utopic python-ldb python-samba samba
samba-common
samba-common-bin samba-dev samba-dsdb-modules samba-libs
samba-vfs-modules
smbclient winbind
0 to upgrade, 0 to newly install, 0 to remove and 20 not to upgrade.
I 'think' I could probably force the upgrade with 'apt-get
dist-upgrade', but I also think I wouldn't be running Trusty any more
due to the installation of the Utopic kernel.
therefore, Inverse packages *must* be borked, if they will not cleanly
upgrade standard distro packages.
Rowland
I think the Samba mailing list has gone the second mile in trying to
help me upgrade Samba.
I'm needing a resolution from Inverse or an alternative source for the
Samba packages.
thx
(I'm patient! I know it's the weekend.)
--
[email protected]
https://inverse.ca/sogo/lists
