Project

General

Profile

Actions
Copy link

Bug #14565

closed

rudder-slapd/rudder-jetty pid file is not present in Rudder 5 preventing restart of service and causing error at upgrade

Added by Nicolas CHARLES over 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
5.0.18
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
29
Name check:
Fix check:
Regression:

Description

On a Rudder 5.0, after booting, the /var/rudder/run/slapd.pid file is not present, so service rudder-slapd restart fails
It causes upgrade error, and is really not easy to debug

This causes #14558

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #14558: Errors and warnings while upgrading from 4.3 to 5.0 on centos7RejectedActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #14558: Errors and warnings while upgrading from 4.3 to 5.0 on centos7 added
Actions
Copy link
 #2

Updated by François ARMAND over 5 years ago

  • Subject changed from rudder-slapd pid file is not present in Rudder 5., preventing restart of service and causing error at upgrade to rudder-slapd pid file is not present in Rudder 5 preventing restart of service and causing error at upgrade
  • User visibility changed from First impressions of Rudder to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 100 to 52
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 5 years ago

sometimes it's there, sometimes it's not
can't find what causes it

Actions
Copy link
 #4

Updated by François ARMAND over 5 years ago

  • Subject changed from rudder-slapd pid file is not present in Rudder 5 preventing restart of service and causing error at upgrade to rudder-slapd/rudder-jetty pid file is not present in Rudder 5 preventing restart of service and causing error at upgrade

On a fresh install of Rudder 5.0.9 (nightly 2019-04-02), I get the same problem with jetty:

centos7lite_server: Stopping Jetty: ERROR: no pid found at /var/rudder/run/rudder-jetty.pid
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 52 to 51
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 51 to 50
Actions
Copy link
 #9

Updated by Alexis Mousset over 5 years ago

  • Category set to Packaging
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 50 to 49
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 49 to 48
Actions
Copy link
 #12

Updated by Benoît PECCATTE about 5 years ago

  • Effort required set to Medium
  • Priority changed from 48 to 31
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #14

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 31 to 30
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 30 to 29
Actions
Copy link
 #16

Updated by Alexis Mousset over 4 years ago

  • Status changed from New to Rejected

No more pid files needed for restart, we use systemd everywhere.

Actions
Copy link

Also available in: Atom PDF