server-stop

To stop a PM2 dev server without leaving orphan processes on Windows, you must kill the PM2 root process and then sweep surviving children like FOUNDATION.exe or cargo.exe. This guarantees no orphan processes hold the database or block restarts.

FOUNDATION.exe survives a PM2 stop because PM2 only kills the npm root process, leaving the spawned Windows process tree orphaned. You must manually check Get-Process FOUNDATION and force kill it to release the database lock.

To clean up orphan cargo processes after stopping a dev server, check for surviving cargo watchers and kill them only if their path is under the repo's target directory. Never kill unrelated cargo builds that belong to other projects.

The best way to verify a PM2 server shutdown is complete is to check both pm2 jlist for the absence of the process and Get-Process FOUNDATION to confirm no surviving executables remain. This ensures a fully clean shutdown.

You should stop your dev server and clean up orphan child processes when transitioning between development workflows or when a clean shutdown is required. This prevents database locks and ensures the next server start is not blocked by lingering processes.

Yes, you can use PM2 to manage and stop a Rust and Node.js dev server stack. PM2 handles the root npm process, but you must manually sweep the spawned Windows child tree including cargo.exe and FOUNDATION.exe to ensure a clean shutdown.