unix_bind_failed

Summary

admin failed to bind unix socket `{0}`

Help

ensure the directory exists, the path is writable, and no other process holds the socket

Details

When this fires

UnixServer::bind in nanook-admin/src/unix.rs couldn't create the [admin].socket path. The bind step removes a stale socket file first, but it cannot create missing parent directories, write into a read-only location, or steal a socket another live process is holding.

What to check

• Make sure the parent directory exists and the agent user can write to it:

install -d -m 0755 -o nanook -g nanook /run/nanook

• See if another nanook (or stale instance) still has it open:

ss -lxp | grep nanook.sock
fuser /run/nanook/admin.sock

• If the path already exists as a regular file (not a socket), remove it.