Bug#926657: openldap: slapd process failure is not detected by systemd

[Heitor R. Alves de Siqueira]

Package: openldap
Severity: normal

Dear Maintainer,

The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating the unit file using the systemd-sysv-generator(8) utility. The
generated unit file contains Type=forking and RemainAfterExit=yes directives.

If the slapd daemon process exits due to some failure (e.g., it receives a
SIGTERM or SIGKILL), the failure is not detected properly by systemd. The
service is still reported as active even though the child (daemon) process has
exited with a signal.

Bug#900397: Possible regression

[Heitor R. Alves de Siqueira]

Hi,

Just FYI, there's a bug in Ubuntu that prevents iscsid to restart
properly due to the ExecStop directive in iscsid.service. This only
happens if iscsid.socket is being used, so making iscsid socket
activated might introduce this bug in Debian.
The fix is to remove ExecStop from the iscsid service and let systemd
handle termination. For more details, refer to LP 1821255 [0].

Thanks,
Heitor

[0] https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1821255

Bug#922705:

[Heitor R. Alves de Siqueira]

Some more information about the crash kernel parameters:

Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.

The "reset_devices" parameter hints the drivers that they may be
booting from a non-healthy condition and need to issue a reset to the
adapter. Drivers that currently implement this feature are (kernel
v4.19): hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.