Welcome to the Linux Foundation Forum!

Error Starting Peer1: Error while loading installation package for ccname=ccForAll, ccversion=1.0

koakh
koakh Posts: 11
in LFS272 Class Forum - Discontinued

Hello

I have a error starting my peer1 container after I installed/instantiated chaincode of lab4
(peer0 is working without problems)

**Error while loading installation package for ccname=ccForAll, ccversion=1.0. Err=open /var/hyperledger/production/chaincodes/ccForAll.1.0: no such file or directory
**

$ docker-compose up peer1.org1.example.com
...
peer1.org1.example.com    | 2019-11-02 17:54:24.807 UTC [gossip.service] func1 -> INFO 02d Elected as a leader, starting delivery service for channel allarewelcome
peer1.org1.example.com    | 2019-11-02 17:54:24.817 UTC [gossip.privdata] StoreBlock -> INFO 02e [allarewelcome] Received block [1] from buffer
peer1.org1.example.com    | 2019-11-02 17:54:24.872 UTC [committer.txvalidator] Validate -> INFO 02f [allarewelcome] Validated block [1] in 53ms
peer1.org1.example.com    | 2019-11-02 17:54:24.873 UTC [cceventmgmt] HandleStateUpdates -> INFO 030 Channel [allarewelcome]: Handling deploy or update of chaincode [ccForAll]
peer1.org1.example.com    | 2019-11-02 17:54:24.874 UTC [ccprovider] ExtractStatedbArtifactsForChaincode -> INFO 031 Error while loading installation package for ccname=ccForAll, ccversion=1.0. Err=open /var/hyperledger/production/chaincodes/ccForAll.1.0: no such file or directory
peer1.org1.example.com    | 2019-11-02 17:54:24.875 UTC [cceventmgmt] HandleChaincodeDeploy -> INFO 032 Channel [allarewelcome]: Chaincode [Name=ccForAll, Version=1.0, Hash=[]byte{0xeb, 0xcc, 0xdb, 0x27, 0x24, 0x7f, 0xaa, 0x8f, 0xeb, 0xc6, 0xcd, 0xb1, 0x7a, 0x28, 0x8d, 0xaf, 0xcd, 0xb2, 0x1d, 0x64, 0x84, 0xcf, 0xaf, 0xcb, 0xcf, 0x8a, 0x46, 0xea, 0xcb, 0xf9, 0xdb, 0xfd}] is not installed hence no need to create chaincode artifacts for endorsement
peer1.org1.example.com    | 2019-11-02 17:54:24.937 UTC [gossip.state] commitBlock -> ERRO 033 Got error while committing(unexpected Previous block hash. Expected PreviousHash = [ee1d786474662a92950a5841b38d6b6d52e3d4775f01ce4ef4e9990eb2e64807], PreviousHash referred in the latest block= [67ab54ef38739d1c80598c44f930a7059f5ed1b6a036f4de3f093abb72e406aa]

any help to solve this issue without delete container and related volumes will me appreciated

thanks

Comments

  • koakh
    koakh Posts: 11

    Hello again

    after solve above problems dropping peer1 and restart it,
    (I don't like that strategy, but without some help and advise it's my only option)

    after I join channel it always crash with

    peer1.org1.example.com    | 2019-11-02 19:07:24.080 UTC [gossip.state] commitBlock -> ERRO 032 Got error while committing(unexpected Previous block hash. Expected PreviousHash = [ee1d786474662a92950a5841b38d6b6d52e3d4775f01ce4ef4e9990eb2e64807], PreviousHash referred in the latest block= [67ab54ef38739d1c80598c44f930a7059f5ed1b6a036f4de3f093abb72e406aa]

    this is not a easy debug task, but that the way we learn, struggling and solving problems :)

    any help, you know ;)

  • koakh
    koakh Posts: 11

    I dropped both containers couchdbOrg1Peer1 and peer1.org1.example.com, and restart both but same error, after I join peer1 to channel allarewelcome it always crash with same annoying error

    peer1.org1.example.com    | 2019-11-02 19:31:29.203 UTC [couchdb] CreateDatabaseIfNotExist -> INFO 059 Created state database allarewelcome_lscc
peer1.org1.example.com    | 2019-11-02 19:31:29.206 UTC [committer.txvalidator] Validate -> INFO 05a [allarewelcome] Validated block [1] in 459ms
...
peer1.org1.example.com    | 2019-11-02 19:31:29.258 UTC [gossip.state] commitBlock -> ERRO 05c Got error while committing(unexpected Previous block hash. Expected PreviousHash = [ee1d786474662a92950a5841b38d6b6d52e3d4775f01ce4ef4e9990eb2e64807], PreviousHash referred in the latest block= [67ab54ef38739d1c80598c44f930a7059f5ed1b6a036f4de3f093abb72e406aa]
...
peer1.org1.example.com    | 2019-11-02 19:31:29.261 UTC [gossip.state] deliverPayloads -> PANI 05d Cannot commit block to the ledger due to unexpected Previous block hash. Expected PreviousHash = [ee1d786474662a92950a5841b38d6b6d52e3d4775f01ce4ef4e9990eb2e64807], PreviousHash referred in the latest block= [67ab54ef38739d1c80598c44f930a7059f5ed1b6a036f4de3f093abb72e406aa]

    after some debug I found that peer1 has a stalled/old genesis block :(
    I stop service stack, and enter in both containers and remove both genesis blocks just to be consistent, start service stack again and re-fetch a new fresh genesis block, join channel, install chaincode and it works ate last

    $ docker-compose stop
$ docker-compose run peer0.org1.example.com bash
$ rm allarewelcome.block 
$ docker-compose run peer1.org1.example.com bash
$ rm allarewelcome.block 
$ docker-compose up

    I leave here my debugs and findings with hope that is useful other struggler's like me LOL

    thanks guys

Categories

Upcoming Training