Project

General

Profile

Actions

Bug #7469

closed

/etc/init.d/rudder-jetty fails to stop jetty if it's PID file is missing

Added by Nicolas CHARLES over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:

Description

On a fresh 3.2 install, the rudder-jetty restart failed to restart jetty
The jetty was in a corrupted state, where the connection to ldap was failing. Trying to restart failed, so we resolved into killing the service with kill


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #7107: service rudder-jetty stop doesn't stop jettyRejected2015-08-14Actions
Actions #1

Updated by Nicolas CHARLES over 6 years ago

  • Assignee set to Benoît PECCATTE
  • Priority changed from N/A to 1

in this case, the jetty is so broken that we don't even have the /var/log/rudder/webapp logs (folder is empty)

Actions #2

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.2.0~beta1 to 3.2.0~rc1
Actions #3

Updated by Jonathan CLARKE over 6 years ago

Could this be related to #7515?

Actions #4

Updated by Jonathan CLARKE over 6 years ago

Either way, it's likely that #7516 will avoid this happening (the rudder-jetty packages kills all jetty processes upon removal).

However, it would probably be better to apply the same fix as #7515 to rudder-jetty's init script.

Actions #5

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from New to In progress
  • Assignee changed from Benoît PECCATTE to Jonathan CLARKE
Actions #6

Updated by Jonathan CLARKE over 6 years ago

  • Target version changed from 3.2.0~rc1 to 2.11.17
Actions #7

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/830
Actions #8

Updated by Jonathan CLARKE over 6 years ago

  • Subject changed from /etc/init.d/rudder-jetty restart does not restart jetty to /etc/init.d/rudder-jetty fails to stop jetty if it's PID file is missing
Actions #9

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.17, 3.0.12 and 3.1.5 which were released today.

Actions #12

Updated by Jonathan CLARKE over 6 years ago

  • Has duplicate Bug #7107: service rudder-jetty stop doesn't stop jetty added
Actions

Also available in: Atom PDF