admin_start
Diagnostic `nanook::cli::admin_start`
Summary
admin server failed to start
Details
When this fires
nanook run couldn't bring the admin server up. It wraps the inner failure from AuthLayer::from_cfg or the listener bind/spawn step in commands/run.rs. Common roots: [admin].addr is in use, the socket path's parent doesn't exist, or the configured authorized_keys file can't be read.
What to check
The inner diagnostic carries the concrete cause (EADDRINUSE, ENOENT, perms, bad key). For port conflicts, ss -ltn shows what's holding the address. For auth failures, see the nanook::cli::auth code.