I can confirm this bug on Zesty.

As far as I understand the situation, the following is the case.

The package leases the service in a un-configured state. There is no 
/etc/dirsrv/admin-serv/adm.conf and /var/log/dirsrv/admin-serv/ does not exist.
This is why the service doesn't start. The service is started by automatic 
dh_helpers code, and that is why the package doesn't install.

389-admin.postinst 
#!/bin/sh
set -e
# Automatically added by dh_systemd_enable
if deb-systemd-helper debian-installed dirsrv-admin.service; then
        # This will only remove masks created by d-s-h on package removal.
        deb-systemd-helper unmask dirsrv-admin.service >/dev/null || true

        if deb-systemd-helper --quiet was-enabled dirsrv-admin.service; then
                # Create new symlinks, if any.
                deb-systemd-helper enable dirsrv-admin.service >/dev/null || 
true
        fi
fi


Removing that automated code is one way. Let the user enable the service once 
he has been set it up correctly. setup-ds-admin is as far as I know the command 
to use for creating this config.


However, that is not expected behaviour in debian. The 'correct' fix would be 
to pre-configure the service in a way that allows it to start sucesfully. I 
don't know this software enough to make a judgment if that is feasible.

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-admin in Ubuntu.
https://bugs.launchpad.net/bugs/1652476

Title:
  package 389-admin 1.1.43-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in 389-admin package in Ubuntu:
  Confirmed

Bug description:
  package 389-admin 1.1.43-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: 389-admin 1.1.43-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   libpam-cgfs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Dec 25 03:21:17 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-26 (28 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: 389-admin
  Title: package 389-admin 1.1.43-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/389-admin/+bug/1652476/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-389-directory-server
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-389-directory-server
More help   : https://help.launchpad.net/ListHelp

Reply via email to