You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2018. It is now read-only.
I have changed PEER_ID in the compose files, then I tried to run with PBFT.
While deploying a chaincode on node1, the nodes do not synchronized.
Here is the WARN message i see on logs :
node1_1 | 08:56:35.018 [consensus/pbft] recvViewChange -> WARN 7eb Replica 0 found incorrect signature in view-change message: Could not verify message from vp0 (unknown peer)
I do not have any vp0 anymore in my config files. Actually, node1 is the new name of vp0
If I run the network on NOOPS consensus , I have no problem
Here is the config of peer-secure-pbft-base.yaml :
I have changed PEER_ID in the compose files, then I tried to run with PBFT.
While deploying a chaincode on node1, the nodes do not synchronized.
Here is the WARN message i see on logs :
node1_1 | 08:56:35.018 [consensus/pbft] recvViewChange -> WARN 7eb Replica 0 found incorrect signature in view-change message: Could not verify message from vp0 (unknown peer)
I do not have any vp0 anymore in my config files. Actually, node1 is the new name of vp0
If I run the network on NOOPS consensus , I have no problem
Here is the config of peer-secure-pbft-base.yaml :
and full-peer-ca.yaml :
The text was updated successfully, but these errors were encountered: