libnyanpasu/clash-nyanpasu · error

failed to start service, exit code: {}, signal: {:?}

Error message

failed to start service, exit code: {}, signal: {:?}

What it means

start_service ran the service starter with elevated privileges (RunasCommand on Windows, sudo on macOS) and the child process exited non-zero, meaning the nyanpasu service was not started. This is an ExitStatus check on the spawned privileged command: failure usually indicates the elevation prompt was denied, the service is not installed, or the service binary failed during startup.

Source

Thrown at backend/tauri/src/core/service/control.rs:199

    })
    .await??;
    if !child.success() {
        anyhow::bail!(
            "failed to start service, exit code: {}, signal: {:?}",
            child.code().unwrap_or(-1),
            {
                #[cfg(unix)]
                {
                    child.signal().unwrap_or(0)
                }
                #[cfg(not(unix))]
                {
                    0
                }
            }
        );
    }
    Ok(())
}

View on GitHub (pinned to f7dbce2997)

Solutions

1. Retry and accept the UAC/sudo elevation prompt.
2. Confirm the service is installed first (install_service) before starting; an uninstalled service makes start fail.
3. Run the service binary manually with the `start` argument as administrator to capture detailed output.
4. Check OS service logs (Windows Event Log / launchd) for the service's startup failure reason.

When it happens

Trigger: Thrown at backend/tauri/src/core/service/control.rs:199 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of libnyanpasu/clash-nyanpasu@f7dbce2997 (2026-09-08). Data as JSON: /api/errors/9be69588219c6fed. Report an issue: GitHub.