retracers reach respawn limit
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Daisy |
New
|
Undecided
|
Unassigned | ||
Bug Description
I've heard that retracers some times die and reach their restart limit e.g.
kernel: [1248124.346493] init: retracer-amd64 main process (15176) terminated with status 1
kernel: [1248124.346549] init: retracer-amd64 main process ended, respawning
kernel: [1248160.938522] init: retracer-amd64 main process (15522) terminated with status 1
kernel: [1248160.938830] init: retracer-amd64 main process ended, respawning
kernel: [1248162.532329] init: retracer-amd64 main process (15534) terminated with status 1
kernel: [1248162.532785] init: retracer-amd64 main process ended, respawning
kernel: [1248164.044925] init: retracer-amd64 main process (15537) terminated with status 1
kernel: [1248164.045121] init: retracer-amd64 main process ended, respawning
kernel: [1248165.639615] init: retracer-amd64 main process (15538) terminated with status 1
kernel: [1248165.639794] init: retracer-amd64 main process ended, respawning
kernel: [1248167.109279] init: retracer-amd64 main process (15539) terminated with status 1
kernel: [1248167.109555] init: retracer-amd64 respawning too fast, stopped
Its been suggested to increase the respawn limit count.
Related branches
- Brian Murray (community): Disapprove
- Junien Fridrick: Approve
-
Diff: 18 lines (+2/-1)1 file modifiedhooks/common (+2/-1)
| Brian Murray (brian-murray) wrote | #1 |
| Brian Murray (brian-murray) wrote | #2 |
| Brian Murray (brian-murray) wrote | #3 |
| Brian Murray (brian-murray) wrote | #4 |
Looking at the log files for the retracer in the above log snippet it was failing due to "OSError: [Errno 12] Cannot allocate memory". I don't think increasing the respawn limit count will help out in this particular case.