Actions
Bug #16076
closedrelayd should stop when a thread panics
Status:
Released
Priority:
N/A
Assignee:
Category:
Relay server or API
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
A panicking thread may leave relayd in a broken state. In order to avoid this, it is better to stop it correctly, to make it visible a problem occured. Systemd can take care of automatically restarting it then.
In the future we might make it more specific and allow specific threads to panic.
Updated by Alexis Mousset about 5 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 5 years ago
Work in progess here: https://github.com/amousset/rudder/commit/84c63029d4abfe34903ddba0d6f0e076d94bac65
Updated by Alexis Mousset about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2564
Updated by Alexis Mousset about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|fd3d062e0ca36cad2125fcb21bdd21a21f2dd43e.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Actions