Actions
Bug #6712
closed
service rudder-jetty status doesn't tell if service is up and running
Added by Nicolas CHARLES almost 9 years ago. Updated over 6 years ago.
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
27
Name check:
Fix check:
Regression:
Description
When we run service rudder-jetty status, we have a lot of nice information on configurations of rudder-jetty, but it misses the point of telling if rudder-jetty is running :(
Updated by Nicolas CHARLES almost 9 years ago
actually, when it is running it says
Jetty running pid=3019
but when it is not running, it fails to say so.
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.12 to 2.10.15
Same in 2.10 !
Updated by Matthieu CERDA
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.15 to 2.10.16
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.16 to 2.10.17
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.17 to 2.10.18
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.18 to 2.10.19
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.19 to 2.10.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.20 to 277
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 277 to 2.11.18
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Jonathan CLARKE about 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority set to 14
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 3.1.25 to 387
Updated by Nicolas CHARLES over 6 years ago
- Status changed from New to Rejected
In 4.1, we have the exit code, saying if it's running (0) or not running (1)
with systemd, the message is quite clear on the output also, not so clear with init scripts
rejecting has we have the information
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 387 to 3.1.25
Actions