Package: 389-ds Version: 1.3.5.17-2 Severity: important Dear Maintainer,
after installing 389-ds on a fresh Debian Stable install, it will not start and leaves apt in an unfinished state. The first thing I noticed was wrong was that the directory /var/log/dirserv/admin-serv is not created. After creating the directory, the manual command apache2 -k start -f /etc/dirserv/dirserv-admin/httpd.conf will not give any error messages, yet it does not start. Trying to manually configure 389-admin with dpkg --configure 389-admin does exactly the same as when installing it through apt. A web search claimed that disabling mpm_event and enable mpm_worker would fix the issue, after testing this on my system it made no difference. Regards Jon -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages 389-ds depends on: ih 389-admin 1.1.43-1+b1 ii 389-admin-console 1.1.12-1 ii 389-console 1.1.18-2 ii 389-ds-base 1.3.5.17-2 iu 389-ds-console 1.2.16-1 iu 389-dsgw 1.1.11-2+b3 389-ds recommends no packages. 389-ds suggests no packages. -- no debconf information
