Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
Rush could not decide whether to trust a wire session, because the information it uses to decide was unreadable. Let's see what it relies on. Two files sit beside your device key: the Namewise roster, which lists the citizens, and the pins file, which remembers their keys. Each line must be one of a few exact shapes, such as citizen, citizen dot node followed by sixty-four hex digits, citizen dot endpoint with an address and port, or the pin forms. If even one line is not understood, rush refuses the whole file, because a half-understood roster is worse than none: it might trust the wrong node. The same refusal happens if your home directory is not set, or if the session door, or tungsten, rejected the being or one of the gates. The second slot names the file and the line, or the refusal itself. Open the named file, find the line, and correct it to one of the declared shapes. Then try the session again, and rush will be able to judge it.
Text from the Rush engine's error catalogue.