Bug #7469
closed
/etc/init.d/rudder-jetty fails to stop jetty if it's PID file is missing
Added by Nicolas CHARLES almost 9 years ago.
Updated almost 9 years ago.
Category:
System integration
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
- Assignee set to Benoît PECCATTE
- Priority changed from N/A to 1 (highest)
in this case, the jetty is so broken that we don't even have the /var/log/rudder/webapp logs (folder is empty)
- Target version changed from 3.2.0~beta1 to 3.2.0~rc1
Could this be related to #7515?
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.
- Status changed from New to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Target version changed from 3.2.0~rc1 to 2.11.17
- 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
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- 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.
- Has duplicate Bug #7107: service rudder-jetty stop doesn't stop jetty added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by