Juniper implemented the pipe as a singleton (to prevent data leaking). This means that you can run only one pipe command @the same time. So if there is anyone else connected (or you with a second connection) that is already using a pipe than you can have these error messages

-Tim

Tim is 100% correct. One a single user can run the pipe command at any given time. Tell the other user to get off and stop hogging the pipe command.

There was a bug if a user is disconnected or in some state the pipe command would be “locked” by that user until the firewall was rebooted.

Juniper implemented the pipe as a singleton (to prevent data leaking). This means that you can run only one pipe command @the same time. So if there is anyone else connected (or you with a second connection) that is already using a pipe than you can have these error messages