Actions
Bug #7469
closed
/etc/init.d/rudder-jetty fails to stop jetty if it's PID file is missing
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
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
Updated by Nicolas CHARLES over 9 years ago
- Assignee set to Benoît PECCATTE
- Priority changed from N/A to 1 (highest)
Updated by
Updated by Jonathan CLARKE over 9 years ago
- Status changed from New to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
Updated by Jonathan CLARKE over 9 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
Updated by Jonathan CLARKE over 9 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
Updated by Jonathan CLARKE over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Updated by
Updated by Jonathan CLARKE about 9 years ago
- Has duplicate Bug #7107: service rudder-jetty stop doesn't stop jetty added
Actions