We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We had a node that could not connect to the indy network. We saw the message in the log file on the node it was trying to connect to
aaaaaa could not transmit message to bbbbbb
This message kept repeating.
This appears to be due to a zmq.Again error.
This indicates that zmq PAIR connections may not recover from networking errors.
https://stackoverflow.com/questions/49222514/recovering-from-zmq-error-again-on-a-zmq-pair-socket
We only log a message on error, which will not recover the TCP connection
https://github.com/hyperledger/indy-plenum/blob/main/stp_zmq/zstack.py#L865
A work around is to restart the node that has displayed the message and the node attempting to connect will be able to connect.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We had a node that could not connect to the indy network. We saw the message in the log file on the node it was trying to connect to
aaaaaa could not transmit message to bbbbbb
This message kept repeating.
This appears to be due to a zmq.Again error.
This indicates that zmq PAIR connections may not recover from networking errors.
https://stackoverflow.com/questions/49222514/recovering-from-zmq-error-again-on-a-zmq-pair-socket
We only log a message on error, which will not recover the TCP connection
https://github.com/hyperledger/indy-plenum/blob/main/stp_zmq/zstack.py#L865
A work around is to restart the node that has displayed the message and the node attempting to connect will be able to connect.
The text was updated successfully, but these errors were encountered: