Project

General

Profile

Actions
Copy link

Bug #10498

closed

Stopping slapd fails if pid file is empty

Added by Janos Mattyasovszky about 7 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
System integration
Target version:
4.1.10
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
40
Name check:
Fix check:
Regression:

Description

If the pid file for slapd is empty, the init script fails.
Here is the trace:

+ message info '[INFO] Halting OpenLDAP...'
+ '[' Linux = Linux ']'
+ logger -p local4.info -s -t rudder-slapd -i '[INFO] Halting OpenLDAP...'
<166>Mar 24 07:34:57 rudder-slapd[1394]: [INFO] Halting OpenLDAP...
+ '[' '!' -r /var/rudder/run/slapd.pid ']'
++ cat /var/rudder/run/slapd.pid
+ PID=
+ kill -INT
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
+ i=0
+ '[' -e /proc/ ']'
+ '[' 0 -eq 30 ']'
++ expr 0 + 1
+ i=1
[...]

Note: slapd was actually running.

# pgrep -f /opt/rudder/libexec/slapd
17492

After writing the PID to the file it did stop.

Found in: rudder-inventory-ldap-4.1.0.rc2.git201703230121-1.SLES.12.x86_64

Subtasks 1 (0 open — 1 closed)

Bug #12121: Wrong condition to check if PID directory exists when stopping ldapReleasedBenoît PECCATTEActions
Actions
Copy link

Also available in: Atom PDF