Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
A secure connection between two nodes broke while records were flowing. Let's see how the stream is built. The carrier moves only sealed records. Each record starts with two bytes giving its length, and then the sealed bytes. Three things can go wrong. First, the peer may have closed the stream, or you waited longer than the declared timeout, and the verdict is carrier closed. Second, a record may announce a length above the maximum allowed. That is carrier too long, and rush refuses it rather than allocating memory for something that may be an attack or a bug. Third, a record may fail to open under the session's key. That is seal tag, which means the record was altered, or it did not come from the peer you handshook with. The first slot names the step where the failure happened. Rush closes the session rather than continuing on a stream it cannot trust. Check that the peer is alive and the network is stable, then connect again.
Text from the Rush engine's error catalogue.