Re: [SOGo] Re: SOGo upgrade issue
On 21/07/15 14:26, Steve Ankeny wrote:
On 07/18/2015 05:34 PM, Christian M. Jensen wrote:
hi.
this is just a suggestion, if the problem really just is the postinst
script
download the package using wget or other local tool
then unpack it and extract the DEBIAN folder from it like this
*NOTE* foo.deb is the package you modify
*NOTE* tmpdir is the folder you extract the deb archive to.
*NOTE* hacked.deb is the package you install!
dpkg-deb -x foo.deb tmpdir
dpkg-deb --control foo.deb tmpdir/DEBIAN
now edit the postinst script
nano tmpdir/DEBIAN/control
now pack the deb file and install it
dpkg -b tmpdir hacked.deb
dpkg -i hacked.deb
I've done this my self a few times, and might just be what you need
if you don't want to compile it
just a suggestion.
Regards
Christian Jensen
just a followup --
*Christian's suggestion was the ONLY suggestion that worked.*
(1) 'update-rc.d -f samba remove' 'apt-get -f install' didn't work
No matter the order in which I performed the procedures, it never
completed the installation.
(2) neither did 'mv /etc/init.d/samba /etc/init.d/samba_old' work
That appeared to me simply a different way of removing the 'samba'
link in '/etc/init.d/'
As it turns out --
(3) *There is an error in the Inverse 'samba' package
'/tmpdir/DEBIAN/postinst' script*
line 51 reads 'update-rc.d samba remove' but SHOULD read 'update-rc.d
-f samba remove'
The first DOES NOT WORK but the second does.
(4) removing 'samba' before installing the hacked deb package is a
mistake
The deb package requires other Samba packages, such as
'samba-common' 'samba-common-bin' etc., so those MUST be installed
before installing the hacked deb package ('samba' will fail at that
point)
THEN the hacked deb package will install properly over the failed
'samba' package.
After completing the installation --
(5) domain login worked properly (most likely because I had not
removed or disturbed 'samba')
The domain user DB was intact, and it allowed login to the domain
(machines were properly joined)
(6) HOWEVER, I had issues with logging into the SOGo web interface
(not recognizing user/password)
I will have to troubleshoot why I could not log into SOGo and/or
why the web interface would not load. Actually, although Apache was
running, I could not access the SOGo web page itself (so, there's an
issue)
I have rolled back (restored) the snapshot of my server so users can
work uninterrupted today.
Any suggestions on how to troubleshoot my e-mail/calendar server will
be appreciated. I successfully ran the 'sql-update' script, but I was
never able to test it because SOGo would not recognize user/password.
I would appreciate Inverse correcting the issue with the 'postinst'
script (it would save time)
The problem is Inverse is basing their packages on the Debian Packages,
Debian came up with that line to cure a systemd problem and probably
because (in my opinion) you have to be brain dead to use systemd, they
forgot the '-f'
Rowland
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 05:34 PM, Christian M. Jensen wrote:
hi.
this is just a suggestion, if the problem really just is the postinst
script
download the package using wget or other local tool
then unpack it and extract the DEBIAN folder from it like this
*NOTE* foo.deb is the package you modify
*NOTE* tmpdir is the folder you extract the deb archive to.
*NOTE* hacked.deb is the package you install!
dpkg-deb -x foo.deb tmpdir
dpkg-deb --control foo.deb tmpdir/DEBIAN
now edit the postinst script
nano tmpdir/DEBIAN/control
now pack the deb file and install it
dpkg -b tmpdir hacked.deb
dpkg -i hacked.deb
I've done this my self a few times, and might just be what you need if
you don't want to compile it
just a suggestion.
Regards
Christian Jensen
just a followup --
*Christian's suggestion was the ONLY suggestion that worked.*
(1) 'update-rc.d -f samba remove' 'apt-get -f install' didn't work
No matter the order in which I performed the procedures, it never
completed the installation.
(2) neither did 'mv /etc/init.d/samba /etc/init.d/samba_old' work
That appeared to me simply a different way of removing the 'samba' link
in '/etc/init.d/'
As it turns out --
(3) *There is an error in the Inverse 'samba' package
'/tmpdir/DEBIAN/postinst' script*
line 51 reads 'update-rc.d samba remove' but SHOULD read 'update-rc.d -f
samba remove'
The first DOES NOT WORK but the second does.
(4) removing 'samba' before installing the hacked deb package is a mistake
The deb package requires other Samba packages, such as 'samba-common'
'samba-common-bin' etc., so those MUST be installed before installing
the hacked deb package ('samba' will fail at that point)
THEN the hacked deb package will install properly over the failed
'samba' package.
After completing the installation --
(5) domain login worked properly (most likely because I had not removed
or disturbed 'samba')
The domain user DB was intact, and it allowed login to the domain
(machines were properly joined)
(6) HOWEVER, I had issues with logging into the SOGo web interface (not
recognizing user/password)
I will have to troubleshoot why I could not log into SOGo and/or why
the web interface would not load. Actually, although Apache was
running, I could not access the SOGo web page itself (so, there's an issue)
I have rolled back (restored) the snapshot of my server so users can
work uninterrupted today.
Any suggestions on how to troubleshoot my e-mail/calendar server will be
appreciated. I successfully ran the 'sql-update' script, but I was
never able to test it because SOGo would not recognize user/password.
I would appreciate Inverse correcting the issue with the 'postinst'
script (it would save time)
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 05:34 PM, Christian M. Jensen wrote:
hi.
this is just a suggestion, if the problem really just is the postinst
script
download the package using wget or other local tool
then unpack it and extract the DEBIAN folder from it like this
*NOTE* foo.deb is the package you modify
*NOTE* tmpdir is the folder you extract the deb archive to.
*NOTE* hacked.deb is the package you install!
dpkg-deb -x foo.deb tmpdir
dpkg-deb --control foo.deb tmpdir/DEBIAN
now edit the postinst script
nano tmpdir/DEBIAN/control
now pack the deb file and install it
dpkg -b tmpdir hacked.deb
dpkg -i hacked.deb
I've done this my self a few times, and might just be what you need if
you don't want to compile it
just a suggestion.
Regards
Christian Jensen
thx, Christian
I tried Rowland's suggestion last evening ('sudo apt-get -f install'),
and it didn't resolve the issue.
It certainly seems to me that I need a CORRECT 'samba' package, and if
it's strictly the postinst script, as the error notes, and as Rowland
suggested, then your methodology just might get me over the hump.
here were the latest steps I took --
adam@sogo:~$ sudo apt-get remove samba (no errors)
adam@sogo:~$ sudo apt-get update sudo apt-get upgrade (installed
remaining packages)
adam@sogo:~$ sudo apt-get install python-ocsmanager (package withheld above)
('python-ocsmanager' requires 'samba' which generates the following error)
Setting up samba (2:4.1.18+dfsg-3~inverse1) ...
Installing new version of config file /etc/logrotate.d/samba ...
Installing new version of config file /etc/init/smbd.conf ...
Installing new version of config file /etc/init.d/samba ...
update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)
dpkg: error processing package samba (--configure):
subprocess installed post-installation script returned error exit status 1
(edit /var/lib/dpkg/status to read install ok installed then)
adam@sogo:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
dpkg: error: parsing file '/var/lib/dpkg/status' near line 645 package
'samba':
Config-Version for package with inappropriate Status
E: Sub-process /usr/bin/dpkg returned an error code (2)
adam@sogo:~$
So, it appears to me that SOMEONE needs to edit the post-installation
script.
I will try one more time using the 'sudo update-rc.d -f samba remove'
command (as I did before)
Then I'll try your suggestion (probably this evening EDT -- NY time)
thx for the suggestion
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force) dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 As a workaround, have you tred simply to remove or rename /etc/init.d/samba to something else before running 'apt-get install -f ? This should get you around this error and one step further.. Sven Processing triggers for ureadahead (0.100.0-16) ... E: Sub-process /usr/bin/dpkg returned an error code (1) adam@sogo:~$ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/20/2015 10:24 AM, Sven Nielsen wrote: Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force) dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 As a workaround, have you tred simply to remove or rename /etc/init.d/samba to something else before running 'apt-get install -f ? This should get you around this error and one step further.. Sven Processing triggers for ureadahead (0.100.0-16) ... E: Sub-process /usr/bin/dpkg returned an error code (1) adam@sogo:~$ that was Rowland Penney's original suggestion -- (1) edit '/var/lib/dpkg/status' (2) run 'sudo update-rd.d samba remove' (3) and 'sudo apt-get -f install' I've run all three but the last time I didn't run (2) because there wasn't an error before the attempt (only after) What you cite here is the error AFTER I ran 'sudo apt-get -f install' which admittedly is the clue. And, as others have suggested, it shows the problem with the script in the Inverse 'samba' package. I'll do these tonight before attempting to download and edit myself. I think Inverse should fix their 'samba' package. Maybe a bug report should be filed? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
Am 20.07.2015 um 17:18 schrieb Steve Ankeny: On 07/20/2015 10:24 AM, Sven Nielsen wrote: Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force) dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 As a workaround, have you tred simply to remove or rename /etc/init.d/samba to something else before running 'apt-get install -f ? This should get you around this error and one step further.. Sven Processing triggers for ureadahead (0.100.0-16) ... E: Sub-process /usr/bin/dpkg returned an error code (1) adam@sogo:~$ that was Rowland Penney's original suggestion -- (1) edit '/var/lib/dpkg/status' (2) run 'sudo update-rd.d samba remove' No ;), I mean, just _manually_ rename the file with: # mv /etc/init.d/samba /etc/init.d/samba_old Sven -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/20/2015 11:51 AM, Sven Nielsen wrote: Am 20.07.2015 um 17:18 schrieb Steve Ankeny: On 07/20/2015 10:24 AM, Sven Nielsen wrote: Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force) dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 As a workaround, have you tred simply to remove or rename /etc/init.d/samba to something else before running 'apt-get install -f ? This should get you around this error and one step further.. Sven Processing triggers for ureadahead (0.100.0-16) ... E: Sub-process /usr/bin/dpkg returned an error code (1) adam@sogo:~$ that was Rowland Penney's original suggestion -- (1) edit '/var/lib/dpkg/status' (2) run 'sudo update-rd.d samba remove' No ;), I mean, just _manually_ rename the file with: # mv /etc/init.d/samba /etc/init.d/samba_old Sven noted . . . I'll try your suggestion first (then Rowland's) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **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. dpkg: error processing package winbind (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libnss-winbind:amd64: libnss-winbind:amd64 depends on winbind (= 2:4.1.18+dfsg-3~inverse1); however: Package winbind is not configured yet. dpkg: error processing package libnss-winbind:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libpam-winbind:amd64: libpam-winbind:amd64 depends on winbind (= 2:4.1.18+dfsg-3~inverse1); however: Package winbind is not configured yet. dpkg: error processing package libpam-winbind:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openchangeproxy: openchangeproxy depends on samba (= 4.1.3); however: PackNo apport report written because the error message indicates its a *followup error from a previous failure.* No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already Package samba is not configured yet. dpkg: error processing package openchangeproxy (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openchangeserver: openchangeserver depends on openchangeproxy; however: Package openchangeproxy is not configured yet. openchangeserver depends on samba (= 2:4.1.3);
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 02:56 PM, Rowland Penny wrote: On 18/07/15 19:26, Steve Ankeny wrote: On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) There may be a way to fix this, open /var/lib/dpkg/status in your favourite editor and search for the 'samba' package,
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 02:56 PM, Rowland Penny wrote: On 18/07/15 19:26, Steve Ankeny wrote: On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) There may be a way to fix this, open /var/lib/dpkg/status in your favourite editor and search for the 'samba' package,
Re: [SOGo] Re: SOGo upgrade issue
On 18-07-2015 22:50, Steve Ankeny wrote: On 07/18/2015 02:56 PM, Rowland Penny wrote: On 18/07/15 19:26, Steve Ankeny wrote: On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) There may be a way to fix this, open /var/lib/dpkg/status in your favourite
Re: [SOGo] Re: SOGo upgrade issue
On 18/07/15 21:50, Steve Ankeny wrote: On 07/18/2015 02:56 PM, Rowland Penny wrote: On 18/07/15 19:26, Steve Ankeny wrote: On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) There may be a way to fix this, open /var/lib/dpkg/status in your favourite editor
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 05:24 PM, Rowland Penny wrote: No, you are just fixing the 'samba' install there, you should have just run 'sudo apt-get -f install' Rowland gotcha (didn't understand) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland **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. dpkg: error processing package winbind (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libnss-winbind:amd64: libnss-winbind:amd64 depends on winbind (= 2:4.1.18+dfsg-3~inverse1); however: Package winbind is not configured yet. dpkg: error processing package libnss-winbind:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 07/18/2015 02:56 PM, Rowland Penny wrote: On 18/07/15 19:26, Steve Ankeny wrote: On 07/18/2015 12:53 PM, Rowland Penny wrote: On 18/07/15 15:27, Steve Ankeny wrote: On 07/01/2015 02:39 PM, Steve Ankeny wrote: thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ ok, finally gave this a try However, there are STILL errors -- (here are the steps I used in order) adam@sogo:~$ sudo apt-get remove samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind libpam-winbind openchangeproxy openchangeserver samba winbind The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Need to get 8,559 kB of archives. After this operation, 16.1 MB disk space will be freed. Do you want to continue? [Y/n]Y (completes without error) (edit 'dns-nameservers' and restart network) (reinstall packages that were REMOVED -- using -f yields same results) adam@sogo:~$ sudo apt-get install samba openchangeproxy openchangeserver winbind libnss-winbind libpam-winbind python-ocsmanager Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz Suggested packages: bind9 bind9utils ctdb ntp smbldap-tools The following NEW packages will be installed: libnss-winbind libpam-winbind openchangeproxy openchangeserver python-mapistore python-rpclib python-sievelib python-spyne python-support python-tz samba winbind The following packages will be upgraded: python-ocsmanager 1 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2,833 kB of archives. After this operation, 21.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (errors follow -- highlighted) Setting up samba (2:4.1.18+dfsg-3~inverse1) ... Installing new version of config file /etc/logrotate.d/samba ... Installing new version of config file /etc/init/smbd.conf ... Installing new version of config file /etc/init.d/samba ... *update-rc.d: /etc/init.d/samba exists during rc.d purge (use -f to force)** **dpkg: error processing package samba (--configure):** ** subprocess installed post-installation script returned error exit status 1** * OK, This error seems to be coming from the debian postinst script: if dpkg --compare-versions $2 lt-nl 2:4.1.13+dfsg-2~; then # on upgrades from wheezy to jessie, the samba init script should not stay # active, see #766690 update-rc.d samba remove fi This is from 'man update-rc.d' : REMOVING SCRIPTS When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. So, 'Installing new version of config file /etc/init.d/samba ...' installs the script The debian postinst script tries to remove the links from '/etc/rcrunlevel.d' but fails because the script exists (see line above) There is a way around this, it doesn't matter if the script exists if the links don't, so, in my opinion, whoever wrote the script should have added '-f', this would remove the links even if the script exists. Of course, this is really an artifact of using systemd. Rowland Thanks, Rowland! I knew you'd take notice (and reply) You've been a big help to me. *Is there any way for me to work around this or must I wait for Inverse?* I was hoping there might still be a way to use 'dpkg' to force reconfiguration/installation. Even downloading packages individually and using 'dpkg' is acceptable (until Inverse edits the script) There may be a way to fix this, open /var/lib/dpkg/status in your favourite editor and search for the 'samba' package,
Re: [SOGo] Re: SOGo upgrade issue
thx, I'll look at it when I'm back off my downtime On 07/01/2015 12:21 PM, Achim Gottinger wrote: Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
Hello Steve, You used purge and not remove so all configs got removed as well. Take an look in /var/lib/samba you may find backup's there done by apt/dpkg durcing upgrades. I have an bunch of backed-up-by-dpkg-on-2015-03-10T16.56.tar.gz files there. Seems these include all the necessary ldb's but they all have an suffix like backed-up-by-dpkg-on-2015-03-10T16.56 here which must be removed. achim~ Am 27.06.2015 um 11:18 schrieb Steve Ankeny: I was able to purge the Ubuntu distro Samba packages. It also purged the 'openchangeserver' and 'openchangeproxy' packages. I was able to run update/upgrade, after which I re-installed the Inverse Samba and OpenChange packages. HOWEVER, once I restarted all the services, I was unable to login to my Samba domain. Login to the domain was refused, and the SOGo web interface failed on username/password unknown Does purging Samba also purge the accounts database, and do I need to backup/restore or re-provision? I'm looking for a few other suggestions, though I may not be able to address this for a few days (vacations) On 06/23/2015 11:01 AM, Ludovic Marcotte wrote: On 23/06/2015 10:26, Steve Ankeny wrote: Will that *damage* my Samba-AD-DC or its database? Will I need to re-provision, etc? Most likely not. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 ::http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
I was able to purge the Ubuntu distro Samba packages. It also purged the 'openchangeserver' and 'openchangeproxy' packages. I was able to run update/upgrade, after which I re-installed the Inverse Samba and OpenChange packages. HOWEVER, once I restarted all the services, I was unable to login to my Samba domain. Login to the domain was refused, and the SOGo web interface failed on username/password unknown Does purging Samba also purge the accounts database, and do I need to backup/restore or re-provision? I'm looking for a few other suggestions, though I may not be able to address this for a few days (vacations) On 06/23/2015 11:01 AM, Ludovic Marcotte wrote: On 23/06/2015 10:26, Steve Ankeny wrote: Will that *damage* my Samba-AD-DC or its database? Will I need to re-provision, etc? Most likely not. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 ::http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 06/23/2015 10:04 AM, Ludovic Marcotte wrote: You probably need to remove *all* Samba packages from 14.04 before installing our packages. ok, started here -- adam@sogo:~$ sudo apt-get purge samba The following extra packages will be installed: libgnutls28 libhogweed2 libldb-dev libldb1 libnettle4 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient Suggested packages: gnutls-bin heimdal-clients The following packages will be REMOVED: libnss-winbind* libpam-winbind* openchangeproxy* openchangeserver* samba* winbind* The following NEW packages will be installed: libgnutls28 libhogweed2 libnettle4 The following packages will be upgraded: libldb-dev libldb1 libsmbclient python-ldb python-samba samba-common samba-common-bin samba-dev samba-dsdb-modules samba-libs samba-vfs-modules smbclient 12 upgraded, 3 newly installed, 6 to remove and 8 not upgraded. Removing libnss-winbind:amd64 (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... Removing libpam-winbind:amd64 (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... Removing openchangeserver (1:2.2-5) ... Purging configuration files for openchangeserver (1:2.2-5) ... Removing openchangeproxy (1:2.2-5) ... Removing winbind (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... Purging configuration files for winbind (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... Removing samba (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... samba-ad-dc stop/waiting nmbd stop/waiting Purging configuration files for samba (2:4.1.6+dfsg-1ubuntu2.14.04.7) ... [ it allowed me to keep my current 'smb.conf' ] Setting up libnettle4:amd64 (2.7.1-1) ... Setting up libhogweed2:amd64 (2.7.1-1) ... Setting up libgnutls28:amd64 (3.2.11-2ubuntu1.1) ... Setting up libldb1:amd64 (2:1.1.17-2) ... Setting up samba-libs:amd64 (2:4.1.18+dfsg-3~inverse1) ... Setting up samba-dsdb-modules (2:4.1.18+dfsg-3~inverse1) ... Setting up python-ldb (2:1.1.17-2) ... Setting up python-samba (2:4.1.18+dfsg-3~inverse1) ... Setting up samba-common (2:4.1.18+dfsg-3~inverse1) ... Setting up samba-common-bin (2:4.1.18+dfsg-3~inverse1) ... Setting up libsmbclient:amd64 (2:4.1.18+dfsg-3~inverse1) ... Setting up smbclient (2:4.1.18+dfsg-3~inverse1) ... Setting up samba-vfs-modules (2:4.1.18+dfsg-3~inverse1) ... Setting up libldb-dev (2:1.1.17-2) ... Setting up samba-dev (2:4.1.18+dfsg-3~inverse1) ... [ after which I ran 'sudo apt-get upgrade' again ] The following packages have been kept back: python-ocsmanager The following packages will be upgraded: libmapi0 libmapiproxy0 libmapistore0 libwbclient0 sogo sogo-activesync sogo-openchange 7 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. [ here's where it failed to resolve the Inverse repositories ] Err http://inverse.ca/ubuntu/ trusty/trusty libmapi0 amd64 3:2.3-zentyal11 Could not resolve 'inverse.ca' . . . . . . . E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? [ and, 'sudo apt-get update' failed to resolve Inverse.ca ] I suspect that's caused by DNS pointing to Samba-AD-DC which no longer existed. I'll try again overnight once I determine how I'll change DNS -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
Will that *damage* my Samba-AD-DC or its database? Will I need to re-provision, etc? On 06/23/2015 10:04 AM, Ludovic Marcotte wrote: You probably need to remove *all* Samba packages from 14.04 before installing our packages. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/15 15:04, Ludovic Marcotte wrote: On 23/06/2015 08:40, Steve Ankeny wrote: Would upgrading to Ubuntu 14.10 Utopic complete the upgrade? Or, purging the 'winbind' packages? You probably need to remove *all* Samba packages from 14.04 before installing our packages. The is the list of packages we provide: http://inverse.ca/ubuntu/pool/trusty/s/samba/ From a minimal install of 14.04, our packages install like a snap without any issue. That's how the ZEG is built (and is from *scratch* after every release). Thanks! OH very funny, if you have to remove the standard samba packages from a distro before trying to upgrade samba, then: A) you are not upgrading, you are installing B) inverse samba packages are broken, you can install the Sernet samba packages over the standard packages. Rowland -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/2015 10:48, Rowland Penny wrote: OH very funny, if you have to remove the standard samba packages from a distro before trying to upgrade samba, then: A) you are not upgrading, you are installing B) inverse samba packages are broken, you can install the Sernet samba packages over the standard packages. So help us improve them - you'll see how OH very funny it is to build Samba packages. The Sernet packages will not bring you what's necessary to support OpenChange. That might have changed, but wasn't the case weeks ago. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/15 16:05, Ludovic Marcotte wrote: On 23/06/2015 10:48, Rowland Penny wrote: OH very funny, if you have to remove the standard samba packages from a distro before trying to upgrade samba, then: A) you are not upgrading, you are installing B) inverse samba packages are broken, you can install the Sernet samba packages over the standard packages. So help us improve them - you'll see how OH very funny it is to build Samba packages. The Sernet packages will not bring you what's necessary to support OpenChange. That might have changed, but wasn't the case weeks ago. That is the very problem with Openchange, or it is as far as I am concerned, you need to use the inverse samba packages or Openchange will not work. In my opinion (for what it is worth) Openchange needs to be a package that can be installed with *any* regular samba packages, distro or Sernet, or a self compiled samba, it shouldn't depend on samba being compiled in a certain way. Rowland -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/2015 10:26, Steve Ankeny wrote: Will that *damage* my Samba-AD-DC or its database? Will I need to re-provision, etc? Most likely not. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/2015 11:22, Rowland Penny wrote: That is the very problem with Openchange, or it is as far as I am concerned, you need to use the inverse samba packages or Openchange will not work. In my opinion (for what it is worth) Openchange needs to be a package that can be installed with *any* regular samba packages, distro or Sernet, or a self compiled samba, it shouldn't depend on samba being compiled in a certain way. Indeed and that is why we provide the packages. It'll take *years* before OpenChange is properly packaged on most distros. Some recent distributions (like Jessie) have packages, but they are now old and half-baked (no support for rpcproxy, for example). -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
On 23/06/2015 08:40, Steve Ankeny wrote: Would upgrading to Ubuntu 14.10 Utopic complete the upgrade? Or, purging the 'winbind' packages? You probably need to remove *all* Samba packages from 14.04 before installing our packages. The is the list of packages we provide: http://inverse.ca/ubuntu/pool/trusty/s/samba/ From a minimal install of 14.04, our packages install like a snap without any issue. That's how the ZEG is built (and is from *scratch* after every release). Thanks! -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
El 23/06/15 a les 14:40, Steve Ankeny ha escrit: Is anyone else having problems with the Inverse Samba packages not upgrading on Ubuntu 14.04? Since I don't need outlook integration, I'm just avoiding the inverse samba packages with this in /etc/apt/preferences.d/00_avoid_inverse_samba Package: samba* libldb1 libsmbclient python-ldb python-samba smbclient Pin: origin inverse.ca Pin-Priority: -1 that's not a solution if you need outlook integration though. Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007 -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
Is anyone else having problems with the Inverse Samba packages not upgrading on Ubuntu 14.04? There seems to be a problem as shown by Rowland Penny (Samba) below. Can Inverse confirm? Would upgrading to Ubuntu 14.10 Utopic complete the upgrade? Or, purging the 'winbind' packages? Were the Inverse packages built on the Utopic kernel? At this point, I cannot complete the SOGo upgrade. On 06/19/2015 02:26 PM, Steve Ankeny wrote: 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
Re: [SOGo] Re: SOGo upgrade issue
So, anyone using OpenChange/SOGo is dependent on the Inverse Samba packages for the foreseeable future? It seems to me that places a lot of responsibility on Inverse for maintaining not only SOGo packages but Samba, OpenChange and whatever other packages become necessary. And, it ultimately limits user choices. No more self-compiled installations; no more installations from distro-provided packages, etc? I am troubled by the possibility of having to purge my existing Samba packages lest I *damage* my domain. I'll have a backup, so I can easily restore my existing system, but the possibility of having to re-provision remains. Are there specific steps to backup the existing Samba DB? Can it be exported/imported after-the-fact? On 06/23/2015 11:27 AM, Ludovic Marcotte wrote: On 23/06/2015 11:22, Rowland Penny wrote: That is the very problem with Openchange, or it is as far as I am concerned, you need to use the inverse samba packages or Openchange will not work. In my opinion (for what it is worth) Openchange needs to be a package that can be installed with *any* regular samba packages, distro or Sernet, or a self compiled samba, it shouldn't depend on samba being compiled in a certain way. Indeed and that is why we provide the packages. It'll take *years* before OpenChange is properly packaged on most distros. Some recent distributions (like Jessie) have packages, but they are now old and half-baked (no support for rpcproxy, for example). -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 ::http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
On 06/19/2015 02:26 PM, Steve Ankeny wrote: 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.) understanding that I'm ignorant of the build process used by Inverse . . . However, could it be the Inverse packages were built on a system with a different kernel? -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
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 -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
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
Re: [SOGo] Re: SOGo upgrade issue
thx for the response (1) It's about a six month installation, and it's an active directory (Samba-AD-DC) (2) My apt sources are the standard Ubuntu Trusty and Inverse sources. (3) Perhaps I need to pin the Inverse repository? (4) I'll take a look at the Digital Ocean suggestion later today (as I'll be out several hours) Thanks, again, for your suggestions. On 06/14/2015 08:26 AM, b-users.sogo...@grmbl.net wrote: Steve, On Sat, Jun 13, 2015 at 05:02:12PM -0400, Steve Ankeny wrote: 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? If this is a fresh install of a machine and this is happening then it all depends on where your apt sources point to. Check if you have standard apt-sources or more specific ones. If there's data you don't want to mess with, sping up a Digital Ocean droplet for a few hours ($0.50) and test it and see what's different. https://grmbl.net/digitalocean B -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Re: SOGo upgrade issue
. . . 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. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Re: SOGo upgrade issue
Steve, On Sat, Jun 13, 2015 at 05:02:12PM -0400, Steve Ankeny wrote: 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? If this is a fresh install of a machine and this is happening then it all depends on where your apt sources point to. Check if you have standard apt-sources or more specific ones. If there's data you don't want to mess with, sping up a Digital Ocean droplet for a few hours ($0.50) and test it and see what's different. https://grmbl.net/digitalocean B -- users@sogo.nu https://inverse.ca/sogo/lists
