Investigate Process Filtering #9

New issue

Open

opened 2026-01-27 14:13:55 +00:00 by rawan · 1 comment

rawan commented

2026-01-27 14:13:55 +00:00

Member

Issue: Service Blocked Indefinitely with `.process_filter()` and `.kill_others()`

Problem Summary

When using .process_filter("embedderd") combined with .kill_others(), the zinit service gets stuck in a blocked state indefinitely during startup.

To reproduce:

1- run zinit-server
2- run embedderd --start
3- run zinit list

Root Cause

Deadlock between parent and service process:

embedderd --start runs (Process A)
Process A registers itself with zinit using .process_filter("embedderd")
Zinit starts a new instance (Process B) as a managed service
The process filter detects BOTH processes match "embedderd"
kill_others() tries to kill conflicting processes but creates a deadlock:
- Process A is waiting for Process B to start
- Process B can't fully start because Process A is still running (detected as conflict)
- Neither process can proceed, resulting in permanent block

Why This Happens

.process_filter() monitors ALL processes matching the pattern
The parent process (still running) is considered a "conflict"
Zinit's conflict resolution doesn't handle self-registering services properly

Workaround

Remove .process_filter("embedderd") - only use .kill_others() for port-based conflict detection

## Issue: Service Blocked Indefinitely with `.process_filter()` and `.kill_others()` ### Problem Summary When using `.process_filter("embedderd")` combined with `.kill_others()`, the zinit service gets stuck in a blocked state indefinitely during startup. ### To reproduce: 1- run zinit-server 2- run `embedderd --start` 3- run `zinit list` ### Root Cause **Deadlock between parent and service process:** 1. `embedderd --start` runs (Process A) 2. Process A registers itself with zinit using `.process_filter("embedderd")` 3. Zinit starts a new instance (Process B) as a managed service 4. The process filter detects BOTH processes match "embedderd" 5. `kill_others()` tries to kill conflicting processes but creates a deadlock: - Process A is waiting for Process B to start - Process B can't fully start because Process A is still running (detected as conflict) - Neither process can proceed, resulting in permanent block ### Why This Happens - `.process_filter()` monitors ALL processes matching the pattern - The parent process (still running) is considered a "conflict" - Zinit's conflict resolution doesn't handle self-registering services properly ### Workaround Remove `.process_filter("embedderd")` - only use `.kill_others()` for port-based conflict detection ![image](/attachments/79966583-8908-40d4-bf91-04ca20cd3d2f) ![image](/attachments/c6172c32-13d4-45f4-9b40-37144ff72ce0) ![image](/attachments/1e4a971b-8f93-432e-b49b-6c2291cc82f4)

image.png

39 KiB

image.png

288 KiB

image.png

21 KiB