The dashboard server does not record its own pid, so 'iw server stop' and 'iw server status' answer about a dead process #573

New issue

Open

opened 2026-09-16 13:35:39 +00:00 by claude · 0 comments

claude commented

2026-09-16 13:35:39 +00:00

Member

The dashboard daemon does not write its own pid to ~/.local/share/iw/server/server.pid when it is started directly (java -jar out/dashboard/assembly.dest/out.jar ...). The file keeps whatever pid wrote it last, so both iw server stop and iw server status act on a process that no longer exists.

Evidence: the file said 1926605 while the live server was 678181. Across one session on 2026-09-13/14 the live server was successively 2912439, 3914383 and 2476667, and the pid file named 1926605 throughout.

Workaround used each time — read the live pid from the listening socket instead of the file:

ss -ltnpH | grep ':9876' | grep -oP 'pid=\K[0-9]+'

Impact: a restart driven through iw server stop either does nothing, or signals whatever process has since been given that pid.

Found while closing the dashboard-control-plane effort's slice 11.

The dashboard daemon does not write its own pid to `~/.local/share/iw/server/server.pid` when it is started directly (`java -jar out/dashboard/assembly.dest/out.jar ...`). The file keeps whatever pid wrote it last, so both `iw server stop` and `iw server status` act on a process that no longer exists. **Evidence:** the file said `1926605` while the live server was `678181`. Across one session on 2026-09-13/14 the live server was successively `2912439`, `3914383` and `2476667`, and the pid file named `1926605` throughout. **Workaround used each time** — read the live pid from the listening socket instead of the file: ``` ss -ltnpH | grep ':9876' | grep -oP 'pid=\K[0-9]+' ``` **Impact:** a restart driven through `iw server stop` either does nothing, or signals whatever process has since been given that pid. Found while closing the `dashboard-control-plane` effort's slice 11.