package slapd 2.4.31-1+nmu2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Adhi Dazz]

I'm installing Samba 4.4.2 (latest) from samba website, and after that install slapd,
after install come out this error signal.

I think it's a bug, hopefully someone will be able to fix it soon

Description: Ubuntu 14.04.2 LTS
Release: 14.04
Version: slapd 2.4.31-1+nmu2ubuntu8.1

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: slapd 2.4.31-1+nmu2ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Sat Jul 4 11:33:42 2015
DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.1:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-07-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: openldap
Title: package slapd 2.4.31-1+nmu2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Ryan Tandy (rtandy)]

The dpkg terminal output unfortunately doesn't show why slapd failed to start. Please check /var/log/syslog for the relevant slapd output.

You mentioned you installed Samba-4. If you are running Samba's AD DC, that would probably bind the LDAP port (389/tcp), which would prevent slapd from starting since it wants to use the same port. Is that what's happening here?

[Adhi Dazz (adhisatoe)]

I've reinstall samba4 from apt-get method (backward to Samba Version 4.1.6-Ubuntu), and the problem fixed.

Apparently this bug will only show up if you download the latest samba package (Samba Version 4.4.2), and install it yourself (./configure && make && make install)

So fyi, many of the Samba AD users still use this method will not be able to install and configure slapd because of latest samba.
Hope you can fixed this in the update.

     On Tuesday, 7 July 2015, 3:32, Ryan Tandy <email address hidden> wrote:

 The dpkg terminal output unfortunately doesn't show why slapd failed to
start. Please check /var/log/syslog for the relevant slapd output.

You mentioned you installed Samba-4. If you are running Samba's AD DC,
that would probably bind the LDAP port (389/tcp), which would prevent
slapd from starting since it wants to use the same port. Is that what's
happening here?

** Changed in: openldap (Ubuntu)
      Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1471370

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  I'm installing Samba 4.4.2 (latest) from samba website, and after that install slapd,
  after install come out this error signal.

  I think it's a bug, hopefully someone will be able to fix it soon

  Description:    Ubuntu 14.04.2 LTS
  Release:    14.04
  Version: slapd 2.4.31-1+nmu2ubuntu8.1

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Sat Jul  4 11:33:42 2015
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.1:subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error exit status 1
  InstallationDate: Installed on 2015-07-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1471370/+subscriptions

[Ryan Tandy (rtandy)]

On Tue, Jul 07, 2015 at 03:26:30AM -0000, Adhi Dazz wrote:
>I've reinstall samba4 from apt-get method (backward to Samba Version
>4.1.6-Ubuntu), and the problem fixed.

OK, and what do you have running on port 389 right now, samba or slapd?

(one way to find this: sudo netstat -lntp | grep -w 389)

>Apparently this bug will only show up if you download the latest samba
>package (Samba Version 4.4.2), and install it yourself (./configure &&
>make && make install)

Before I spend a bunch of time doing that, it would be very helpful to
see the /var/log/syslog excerpt showing why slapd failed to start, like
I asked for earlier. Is it possible for you to provide that?

Thanks for your help!

[Adhi Dazz (adhisatoe)]

this is the result of port 389
# sudo netstat -lntp | grep -w 389
tcp        0      0 0.0.0.0:389             0.0.0.0:*               LISTEN      1219/samba
tcp6       0      0 :::389                  :::*                    LISTEN      10511/slapd

although i'm root, here is what i got after running the command
# /var/log/syslog excerpt
bash: /var/log/syslog: Permission denied

#nano # /var/log/syslog
Jul  7 07:46:23 4ecapsvsg6 smbd[1216]: [2015/07/07 07:46:23.682182,  0] ../lib/util/debug.c:597(reopen_logs_internal)
Jul  7 07:46:23 4ecapsvsg6 smbd[1216]:   Unable to open new log file '/var/log/samba4/log.smbd': No such file or directory
Jul  7 07:46:23 4ecapsvsg6 smbd[1216]: [2015/07/07 07:46:23.682506,  0] ../lib/util/debug.c:597(reopen_logs_internal)
Jul  7 07:46:23 4ecapsvsg6 smbd[1216]:   Unable to open new log file '/var/log/samba4/log.smbd': No such file or directory
Jul  7 07:46:23 4ecapsvsg6 smbd[1216]:   Could not find child 29017 -- ignoring
That information is the earliest i can retrieve, the procedure i did yesterday 8pm is somehow not inside the logs :(Looking back history the reasons i undo the whole domain AD things is because of :
domain provisioning error ldb: unable to stat module /usr/lib/x86_64-linux-gnu/samba/ldb
But after i reboot the error somehow connected to slapd, so i report the error from gui notification in ubuntu.

That's all i can inform
Regards,
Adhi N. Wirawan

     On Tuesday, 7 July 2015, 12:10, Ryan Tandy <email address hidden> wrote:

 On Tue, Jul 07, 2015 at 03:26:30AM -0000, Adhi Dazz wrote:
>I've reinstall samba4 from apt-get method (backward to Samba Version
>4.1.6-Ubuntu), and the problem fixed.

OK, and what do you have running on port 389 right now, samba or slapd?

(one way to find this: sudo netstat -lntp | grep -w 389)

>Apparently this bug will only show up if you download the latest samba
>package (Samba Version 4.4.2), and install it yourself (./configure &&
>make && make install)

Before I spend a bunch of time doing that, it would be very helpful to
see the /var/log/syslog excerpt showing why slapd failed to start, like
I asked for earlier. Is it possible for you to provide that?

Thanks for your help!

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1471370

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  I'm installing Samba 4.4.2 (latest) from samba website, and after that install slapd,
  after install come out this error signal.

  I think it's a bug, hopefully someone will be able to fix it soon

  Description:    Ubuntu 14.04.2 LTS
  Release:    14.04
  Version: slapd 2.4.31-1+nmu2ubuntu8.1

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Sat Jul  4 11:33:42 2015
  DuplicateSignature: package:slapd:2.4....

[Ryan Tandy (rtandy)]

On Tue, Jul 07, 2015 at 04:25:57AM -0000, Adhi Dazz wrote:
>this is the result of port 389
># sudo netstat -lntp | grep -w 389
>tcp        0      0 0.0.0.0:389             0.0.0.0:*               LISTEN      1219/samba
>tcp6       0      0 :::389                  :::*                    LISTEN      10511/slapd

Interesting. 'samba-tool domain provision' in trusty does the same thing
for me, too: only sets up IPv4, so then slapd starts on IPv6 only, which
is the same result you have there.

That's a surprising behaviour by slapd, at least, although I'd have to
look deeper before declaring it a bug.

(Either way, I still don't think it's a good idea to try and run both a
Samba AD DC and slapd on the same server.)

>although i'm root, here is what i got after running the command
># /var/log/syslog excerpt
>bash: /var/log/syslog: Permission denied

That was not intended as a literal command. Sorry for the confusion.

>That information is the earliest i can retrieve, the procedure i did
>yesterday 8pm is somehow not inside the logs :(

The logs are rotated daily. Yesterday's logs are in /var/log/syslog.1,
the logs from the day before are in /var/log/syslog.2.gz (gzip
compressed), and so on.

[Launchpad Janitor (janitor)]

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