Actions
Bug #12001
closed
There is no error message on stderr when a service fails to start on Rudder 4.3
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
29
Name check:
Fix check:
Regression:
Description
On debian 9, running
service rudder-jetty restart
doesn't output anything, even if exit code is 1
And this is pretty confusing !
Updated by Nicolas CHARLES almost 7 years ago
- Description updated (diff)
Nicolas CHARLES wrote:
And this is pretty confusing !
Updated by Benoît PECCATTE almost 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 32
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.3.0~beta1 to 4.3.0~rc1
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.3.0~rc1 to 4.3.0~rc2
Updated by Alexis Mousset almost 7 years ago
- Assignee deleted (
Alexis Mousset) - Target version changed from 4.3.0~rc2 to Ideas (not version specific)
We cannot do much about this for now, it is the way systemd works.
Updated by Benoît PECCATTE about 6 years ago
- Status changed from New to Rejected
- Priority changed from 32 to 29
This is a system problem, not a rudder problem.
Actions