** Summary changed: - service slapd stop fails + Reading /proc/$(pidof slapd)/exe fails inside a docker container
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1376548 Title: Reading /proc/$(pidof slapd)/exe fails inside a docker container Status in “docker.io” package in Ubuntu: New Status in “openldap” package in Ubuntu: Invalid Bug description: In "Ubuntu 14.04.1 LTS" amd64 with slapd package version "2.4.31-1+nmu2ubuntu8", "OpenLDAP server (slapd)", executing the following standard service command fails to have effect. # service slapd stop * Stopping OpenLDAP slapd [ OK ] # ps -ef | grep slapd | grep -v grep openldap 196 1 0 02:00 ? 00:00:00 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d i.e. it reports all is OK but it failed to stop the running process which continues with the same pid. The problem is clouded by the --oknodo option in /etc/init.d/slapd. This is responsible for the erroneous report. stop_slapd() { reason="`start-stop-daemon --stop --quiet --oknodo --retry TERM/10 \ --pidfile "$SLAPD_PIDFILE" \ --exec $SLAPD 2>&1`" } Removing --oknodo demonstrates a failure with exit code 1. The role of oknodo should be reconsidered here. Further experimentation shows that the --exec option is not working. Since the init script is checking for $SLAPD_PIDFILE and exiting if empty, I suggest just dropping "--exec $SLAPD" from the init script. It is superfluous and the "service slapd stop" command will work after its removal. SLAPD_PIDFILE is correctly identified on my system. Mine is a stock standard fresh slapd install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1376548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
