Project

General

Profile

Bug #10498

Stopping slapd fails if pid file is empty

Added by Janos Mattyasovszky about 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
40

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

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

Associated revisions

Revision feb3ea66 (diff)
Added by Benoît PECCATTE over 1 year ago

Fixes #10498: Stopping slapd fails if pid file is empty

History

#1

Updated by François ARMAND about 2 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
#2

Updated by Benoît PECCATTE about 2 years ago

  • Priority set to 17
#3

Updated by Alexis MOUSSET about 2 years ago

  • Category set to System integration
#4

Updated by Benoît PECCATTE almost 2 years ago

  • Priority changed from 17 to 16
#5

Updated by Benoît PECCATTE almost 2 years ago

  • Priority changed from 16 to 31
#6

Updated by Benoît PECCATTE almost 2 years ago

  • Effort required set to Small
  • Priority changed from 31 to 35
#7

Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 35 to 43
#8

Updated by Benoît PECCATTE over 1 year ago

  • Target version set to 4.1.10
  • Priority changed from 43 to 41
#9

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
#10

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1503
#11

Updated by Rudder Quality Assistant over 1 year ago

  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
#12

Updated by Benoît PECCATTE over 1 year ago

  • Status changed from Pending technical review to Pending release
#13

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released
  • Priority changed from 41 to 40

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF