Error Help :Bad configuration detected: Received AliveMessage from a peer with the same PKI-ID as myself: tag:EMPTY alive_msg:<membership:<endpoint
|
Mayank Agrawal
Hi guys please help me out with an issue , I am tring to start the network ,I am getting error like inside the peer container logs : Duiing the initial after docker peer up commands. Fabric version 1.4.6 Orderer type : Solo Ubuntu 16.04 All continer running in same machine. For peer0.org1 : 2020-08-17 15:56:04.463 UTC [gossip.discovery] isSentByMe -> ERRO 030 Bad configuration detected: Received AliveMessage from a peer with the same PKI-ID as myself: tag:EMPTY alive_msg:<membership:<endpoint:"peer1.org1.immume.com:9051" pki_id:"\226^w\266i\272\255\266\310|x7\236\376C6A\263\355a\356|\326.\367b .DpD\001" > timestamp:<inc_num:1597679764311752754 seq_num:3 > identity:"\n\007Org1MSP\022\222\006-----BEGIN CERTIFICATE-----\nMIICFjCCAb2gAwIBAgIRAPDqHnWySZgDOI7lNmhhhgIwCgYIKoZIzj0EAwIwcTEL\nMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG\ncmFuY2lzY28xGDAWBgNVBAoTD29yZzEuaW1tdW1lLmNvbTEbMBkGA1UEAxMSY2Eu\nb3JnMS5pbW11bWUuY29tMB4XDTIwMDcyNzE3NTYwMFoXDTMwMDcyNTE3NTYwMFow\nWjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh\nbiBGcmFuY2lzY28xHjAcBgNVBAMMFUFkbWluQG9yZzEuaW1tdW1lLmNvbTBZMBMG\nByqGSM49AgEGCCqGSM49AwEHA0IABMswACwlBVisnlcLTTbPyfdJdh4l1qUwnfLi\n2xZUJ/NhljeHcedRXB3DZPHarVjD7VKJP+eOMwgO5nYjWAEKT/2jTTBLMA4GA1Ud\nDwEB/wQEAwIHgDAMBgNVHRMBAf8EAjAAMCsGA1UdIwQkMCKAIKJ3rJGwTHIGvyd3\n30zq8mq3oQBS2k1EElVL+Bv5dTfvMAoGCCqGSM49BAMCA0cAMEQCIHeqQHLqIysm\nj7MtBGQ5yJ+0uUIK/NbY1huRNL3VygdlAiB5xgHrgAjyQQxmKZ3rNMeUav6ZUdl6\nsCDX2ufB39N+Mw==\n-----END CERTIFICATE-----\n" > 2020-08-17 15:56:34.450 UTC [gossip.discovery] isSentByMe -> ERRO 031 Bad configuration detected: Received AliveMessage from a peer with the same PKI-ID as myself: tag:EMPTY alive_msg:<membership:<endpoint:"peer1.org1.immume.com:9051" pki_id:"\226^w\266i\272\255\266\310|x7\236\376C6A\263\355a\356|\326.\367b .DpD\001" > timestamp:<inc_num:1597679764311752754 seq_num:16 > > FOr peer1.org1 2020-08-17 15:56:04.389 UTC [fsblkstorage] LoadPreResetHeight -> INFO 025 Loading Pre-reset heights 2020-08-17 15:56:04.389 UTC [fsblkstorage] preRestHtFiles -> INFO 026 Dir [/var/hyperledger/production/ledgersData/chains/chains] missing... exiting 2020-08-17 15:56:04.389 UTC [fsblkstorage] LoadPreResetHeight -> INFO 027 Pre-reset heights loaded 2020-08-17 15:56:04.440 UTC [comm.grpc.server] 1 -> INFO 028 unary call completed grpc.service=gossip.Gossip grpc.method=Ping grpc.request_deadline=2020-08-17T15:56:06.402Z grpc.peer_address=172.18.0.3:38096 grpc.peer_subject="CN=peer0.org1.immume.com,L=San Francisco,ST=California,C=US" grpc.code=OK grpc.call_duration=111.817µs 2020-08-17 15:56:04.448 UTC [comm.grpc.server] 1 -> INFO 029 streaming call completed grpc.service=gossip.Gossip grpc.method=GossipStream grpc.request_deadline=2020-08-17T15:56:14.442Z grpc.peer_address=172.18.0.3:38096 grpc.peer_subject="CN=peer0.org1.immume.com,L=San Francisco,ST=California,C=US" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=5.492037ms 2020-08-17 15:56:04.466 UTC [gossip.discovery] isSentByMe -> ERRO 02a Bad configuration detected: Received AliveMessage from a peer with the same PKI-ID as myself: tag:EMPTY alive_msg:<membership:<endpoint:"peer0.org1.immume.com:7051" pki_id:"\226^w\266i\272\255\266\310|x7\236\376C6A\263\355a\356|\326.\367b .DpD\001" > timestamp:<inc_num:1597679764288919590 seq_num:4 > identity:"\n\007Org1MSP\022\222\006-----BEGIN CERTIFICATE-----\nMIICFjCCAb2gAwIBAgIRAPDqHnWySZgDOI7lNmhhhgIwCgYIKoZIzj0EAwIwcTEL\nMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG\ncmFuY2lzY28xGDAWBgNVBAoTD29yZzEuaW1tdW1lLmNvbTEbMBkGA1UEAxMSY2Eu\nb3JnMS5pbW11bWUuY29tMB4XDTIwMDcyNzE3NTYwMFoXDTMwMDcyNTE3NTYwMFow\nWjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh\nbiBGcmFuY2lzY28xHjAcBgNVBAMMFUFkbWluQG9yZzEuaW1tdW1lLmNvbTBZMBMG\nByqGSM49AgEGCCqGSM49AwEHA0IABMswACwlBVisnlcLTTbPyfdJdh4l1qUwnfLi\n2xZUJ/NhljeHcedRXB3DZPHarVjD7VKJP+eOMwgO5nYjWAEKT/2jTTBLMA4GA1Ud\nDwEB/wQEAwIHgDAMBgNVHRMBAf8EAjAAMCsGA1UdIwQkMCKAIKJ3rJGwTHIGvyd3\n30zq8mq3oQBS2k1EElVL+Bv5dTfvMAoGCCqGSM49BAMCA0cAMEQCIHeqQHLqIysm\nj7MtBGQ5yJ+0uUIK/NbY1huRNL3VygdlAiB5xgHrgAjyQQxmKZ3rNMeUav6ZUdl6\nsCDX2ufB39N+Mw==\n-----END CERTIFICATE-----\n" > 2020-08-17 15:56:34.448 UTC [gossip.discovery] isSentByMe -> ERRO 02b Bad configuration detected: Received AliveMessage from a peer with the same PKI-ID as myself: tag:EMPTY alive_msg:<membership:<endpoint:"peer0.org1.immume.com:7051" pki_id:"\226^w\266i\272\255\266\310|x7\236\376C6A\263\355a\356|\326.\367b .DpD\001" > timestamp:<inc_num:1597679764288919590 seq_num:3 > identity:"\n\007Org1MSP\022\222\006-----BEGIN CERTIFICATE-----\nMIICFjCCAb2gAwIBAgIRAPDqHnWySZgDOI7lNmhhhgIwCgYIKoZIzj0EAwIwcTEL\nMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNhbiBG\ncmFuY2lzY28xGDAWBgNVBAoTD29yZzEuaW1tdW1lLmNvbTEbMBkGA1UEAxMSY2Eu\nb3JnMS5pbW11bWUuY29tMB4XDTIwMDcyNzE3NTYwMFoXDTMwMDcyNTE3NTYwMFow\nWjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcTDVNh\nbiBGcmFuY2lzY28xHjAcBgNVBAMMFUFkbWluQG9yZzEuaW1tdW1lLmNvbTBZMBMG\nByqGSM49AgEGCCqGSM49AwEHA0IABMswACwlBVisnlcLTTbPyfdJdh4l1qUwnfLi\n2xZUJ/NhljeHcedRXB3DZPHarVjD7VKJP+eOMwgO5nYjWAEKT/2jTTBLMA4GA1Ud\nDwEB/wQEAwIHgDAMBgNVHRMBAf8EAjAAMCsGA1UdIwQkMCKAIKJ3rJGwTHIGvyd3\n30zq8mq3oQBS2k1EElVL+Bv5dTfvMAoGCCqGSM49BAMCA0cAMEQCIHeqQHLqIysm\nj7MtBGQ5yJ+0uUIK/NbY1huRNL3VygdlAiB5xgHrgAjyQQxmKZ3rNMeUav6ZUdl6\nsCDX2ufB39N+Mw==\n-----END CERTIFICATE-----\n" > I am unable to identify the erorr , please help me out.The same kind of error in both the peer0.org2 & peer1.org2 is found. Yaml for peer0.org1 version: '2' networks: polarbear: services: peer0.org1.immume.com: hostname: peer0.org1.immume.com image: hyperledger/fabric-peer:1.4.6 container_name: peer0.org1.immume.com dns_search: . # extends: # file: docker-compose-couch-org1.yaml # service: couchdb1 environment: - PEER_HOST=peer0.org1.immume.com - PEER_NAME=peer0.org1.immume.com - CORE_PEER_ID=peer0.org1.immume.com - CORE_PEER_LOCALMSPID=Org1MSP # - CORE_PEER_GOSSIP_ENDPOINT=org1-Mypeer.com:7051 - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.immume.com:9051 - CORE_PEER_LISTENADDRESS=0.0.0.0:7051 - CORE_PEER_ADDRESS=peer0.org1.immume.com:7051 - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7053 - CORE_PEER_CHAINCODEADDRESS=peer0.org1.immume.com:7053 - CORE_PEER_PROFILE_ENABLED=true - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock # the following setting starts chaincode containers on the same # bridge network as the peers # https://docs.docker.com/compose/networking/ # - COMPOSE_PROJECT_NAME=polarbear - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=hyperledgerscrach2_polarbear - CORE_LOGGING_LEVEL=DEBUG - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.immume.com:7051 - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false # The following setting skips the gossip handshake since we are # are not doing mutual TLS # - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto/peer/msp - CORE_PEER_TLS_ENABLED=true - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/crypto/peer/tls/server.key - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/crypto/peer/tls/server.crt - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto/peer/tls/ca.crt # -- About Couch -- - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb1:5984 # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD # provide the credentials for ledger to connect to CouchDB. The username and password must # match the username and password set for the associated CouchDB. - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=root - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=root - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/admin/msp working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start ports: - 7051:7051 - 7053:7053 #host(system public_access):container_port volumes: - /var/run/:/host/var/run/ #Backup of the peer ledger # - ./Backup/peer0Org1:/var/hyperledger/production/ # Update the path of our chaincode to map with docker - ./chaincode/:/opt/gopath/src/github.com/chaincode # Update the path for our --cafile in channel create with orderer msp tlscacertpemfile to map with docker - ./crypto-config/ordererOrganizations/orderer.immume.com/orderers/orderer.orderer.immume.com/msp/tlscacerts/:/etc/hyperledger/orderer/msp/tlsca # Update the path of our admin msp to map with docker - ./crypto-config/peerOrganizations/org1.immume.com/users/Admin@.../msp/:/etc/hyperledger/admin/msp # Update the path of our location to map with docker - ./crypto-config/peerOrganizations/org1.immume.com/peers/peer0.org1.immume.com/:/etc/hyperledger/crypto/peer networks: - polarbear couchdb1: container_name: couchdb1 image: hyperledger/fabric-couchdb:0.4.18 # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password # for CouchDB. This will prevent CouchDB from operating in an "Admin Party" mode. environment: - COUCHDB_USER=root - COUCHDB_PASSWORD=root # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service, # for sella map it to utilize Fauxton User Interface in dev environments. ports: - "5984:5984" networks: - polarbear yaml for peer1.org1.yaml version: '2' networks: polarbear: services: peer1.org1.immume.com: hostname: peer1.org1.immume.com image: hyperledger/fabric-peer:1.4.6 container_name: peer1.org1.immume.com dns_search: . # extends: # file: docker-compose-couch-org1.yaml # service: couchdb1 environment: - PEER_HOST=peer1.org1.immume.com - PEER_NAME=peer1.org1.immume.com - CORE_PEER_ID=peer1.org1.immume.com - CORE_PEER_LOCALMSPID=Org1MSP # - CORE_PEER_GOSSIP_ENDPOINT=org1-Mypeer.com:7051 - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.immume.com:7051 - CORE_PEER_LISTENADDRESS=0.0.0.0:9051 - CORE_PEER_ADDRESS=peer1.org1.immume.com:9051 - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:9053 - CORE_PEER_CHAINCODEADDRESS=peer1.org1.immume.com:9053 - CORE_PEER_PROFILE_ENABLED=true - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock # the following setting starts chaincode containers on the same # bridge network as the peers # https://docs.docker.com/compose/networking/ # - COMPOSE_PROJECT_NAME=polarbear - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=hyperledgerscrach2_polarbear - CORE_LOGGING_LEVEL=DEBUG - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.immume.com:9051 - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false # The following setting skips the gossip handshake since we are # are not doing mutual TLS # - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/crypto/peer/msp - CORE_PEER_TLS_ENABLED=true - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/crypto/peer/tls/server.key - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/crypto/peer/tls/server.crt - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/crypto/peer/tls/ca.crt # -- About Couch -- - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb1:5984 # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD # provide the credentials for ledger to connect to CouchDB. The username and password must # match the username and password set for the associated CouchDB. - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=root - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=root - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/admin/msp working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start ports: - 9051:9051 - 9053:9053 #host(system public_access):container_port volumes: - /var/run/:/host/var/run/ #Backup of the peer ledger # - ./Backup/peer1Org1:/var/hyperledger/production/ # Update the path of our chaincode to map with docker - ./chaincode/:/opt/gopath/src/github.com/chaincode # Update the path for our --cafile in channel create with orderer msp tlscacertpemfile to map with docker - ./crypto-config/ordererOrganizations/orderer.immume.com/orderers/orderer.orderer.immume.com/msp/tlscacerts/:/etc/hyperledger/orderer/msp/tlsca # Update the path of our admin msp to map with docker - ./crypto-config/peerOrganizations/org1.immume.com/users/Admin@.../msp/:/etc/hyperledger/admin/msp # Update the path of our location to map with docker - ./crypto-config/peerOrganizations/org1.immume.com/peers/peer1.org1.immume.com/:/etc/hyperledger/crypto/peer networks: - polarbear couchdb1: container_name: couchdb1 image: hyperledger/fabric-couchdb:0.4.18 # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password # for CouchDB. This will prevent CouchDB from operating in an "Admin Party" mode. environment: - COUCHDB_USER=root - COUCHDB_PASSWORD=root # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service, # for sella map it to utilize Fauxton User Interface in dev environments. ports: - "5984:5984" networks: - polarbear There are no error in orderer(solo),ca-org1,ca-org2 logs.
|
|
|