[MINOR] stop_single_service schedules timeout for already-dead processes #34

New issue

Open

opened 2026-05-11 10:52:02 +00:00 by thabeta · 1 comment

thabeta commented

2026-05-11 10:52:02 +00:00

Owner

Problem

When send_signal_to_group fails with ESRCH (process already dead), stop_single_service still schedules a stop timeout. The timeout will fire and attempt to SIGKILL a dead process -- harmless but generates noise in logs.

Impact

Noisy logs. Wasted timer resources.

Files

crates/my_init_server/src/supervisor/api.rs -- stop_single_service

Suggested Fix

Check if the signal send failed with ESRCH and skip the timeout in that case.

## Problem When `send_signal_to_group` fails with ESRCH (process already dead), `stop_single_service` still schedules a stop timeout. The timeout will fire and attempt to SIGKILL a dead process -- harmless but generates noise in logs. ## Impact Noisy logs. Wasted timer resources. ## Files - `crates/my_init_server/src/supervisor/api.rs` -- `stop_single_service` ## Suggested Fix Check if the signal send failed with ESRCH and skip the timeout in that case.

thabeta added the

bug

label

2026-05-11 10:53:00 +00:00

salmaelsoly commented

2026-05-11 13:36:08 +00:00

Member

Classification: valid-bug — stop_single_service schedules a stop timeout even when ESRCH indicates process already dead, wasting timer resources and generating noisy logs.

> Classification: valid-bug — stop_single_service schedules a stop timeout even when ESRCH indicates process already dead, wasting timer resources and generating noisy logs.