Closed kamraanki closed 8 years ago
Usually this happens when something bad happened to your original deployment of chaincode. (even if the rest call said it was successful) Try deploying again.
@dshuffma-ibm i tried it to deploy again and again always got the same message.
could you post the logs of when you deploy? also are you using the latest cp-web code?
closing, issue seems abandoned
OUT - /scripts/start.sh -network_id a188020e3aba4ad39c4e266e498163f2 -peer_id vp0 -chaincode_host prod-us-02-chaincode-swarm-vp0.us.blockchain.ibm.com -chaincode_port 3380 -network_name us.blockchain.ibm.com -port_discovery 30002 -port_rest 5002 -port_event 31002 -peer_enrollid peer0 -chaincode_tls true -peer_tls true -num_peers 4
OUT - Enrollment secret is not passed calculating the default
OUT - CORE_PEER_ID="vp0",CORE_PEER_NETWORKID="a188020e3aba4ad39c4e266e498163f2",CORE_PEER_ADDRESSAUTODETECT="false",CORE_PEER_LISTENADDRESS="0.0.0.0:30002",CORE_REST_ADDRESS="0.0.0.0:5002",CORE_CLI_ADDRESS="0.0.0.0:30404",CORE_PEER_VALIDATOR_EVENTS_ADDRESS="0.0.0.0:31002",CORE_PEER_ADDRESS="a188020e3aba4ad39c4e266e498163f2-vp0.us.blockchain.ibm.com:30002",CORE_LOGGING_PEER="warning",CORE_LOGGING_CRYPTO="warning",CORE_LOGGING_STATUS="warning",CORE_LOGGING_STOP="warning",CORE_LOGGING_LOGIN="warning",CORE_LOGGING_VM="debug",CORE_LOGGING_CHAINCODE="debug",CORE_PEER_LOGGING_LEVEL="warning",CORE_VM_ENDPOINT="tcp://prod-us-02-chaincode-swarm-vp0.us.blockchain.ibm.com:3380",CORE_VM_DOCKER_TLS_ENABLED="true",CORE_VM_DOCKER_TLS_CERT_FILE="/certs/chaincode_host/cert.pem",CORE_VM_DOCKER_TLS_KEY_FILE="/certs/chaincode_host/key.pem",CORE_VM_DOCKER_TLS_CA_FILE="/certs/chaincode_host/ca.pem",CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE="us.blockchain.ibm.com",CORE_PEER_TLS_ENABLED="true",CORE_PEER_TLS_CERT_FILE="/certs/peer/cert.pem",CORE_PEER_TLS_KEY_FILE="/certs/peer/key.pem",CORE_PEER_TLS_SERVERHOSTOVERRIDE="a188020e3aba4ad39c4e266e498163f2-vp0.us.blockchain.ibm.com",CORE_PEER_PKI_TLS_ENABLED="true",CORE_PEER_PKI_TLS_ROOTCERT_FILE="/certs/peer/cert.pem",CORE_PEER_PKI_TLS_SERVERHOSTOVERRIDE="a188020e3aba4ad39c4e266e498163f2-vp0.us.blockchain.ibm.com",CORE_PEER_DISCOVERY_PERIOD="60s",CORE_PEER_DISCOVERY_TOUCHPERIOD="60s",CORE_CHAINCODE_DEPLOYTIMEOUT="180000",CORE_CHAINCODE_STARTUPTIMEOUT="30000",CORE_PEER_VALIDATOR_CONSENSUS_PLUGIN="pbft",CORE_PBFT_GENERAL_MODE="batch",CORE_PBFT_GENERAL_BATCHSIZE="1000",CORE_PBFT_GENERAL_TIMEOUT_BATCH="1s",CORE_PBFT_GENERAL_TIMEOUT_REQUEST="30s",CORE_PBFT_GENERAL_TIMEOUT_VIEWCHANGE="30s",CORE_PBFT_GENERAL_TIMEOUT_RESENDVIEWCHANGE="30s",CORE_PBFT_GENERAL_TIMEOUT_NULLREQUEST="0s",CORE_STATETRANSFER_TIMEOUT_SINGLEBLOCK="600s",CORE_STATETRANSFER_TIMEOUT_SINGLESTATEDELTA="600s",CORE_STATETRANSFER_TIMEOUT_FULLSTATE="600s",CORE_PEER_DISCOVERY_ROOTNODE="a188020e3aba4ad39c4e266e498163f2-vp1.us.blockchain.ibm.com:30002,a188020e3aba4ad39c4e266e498163f2-vp2.us.blockchain.ibm.com:30002,a188020e3aba4ad39c4e266e498163f2-vp3.us.blockchain.ibm.com:30002",CORE_SECURITY_ENABLED="true",CORE_SECURITY_ENROLLID="peer0",CORE_SECURITY_ENROLLSECRET="1e4e0f3366",CORE_PEER_PKI_ECA_PADDR="a188020e3aba4ad39c4e266e498163f2-ca.us.blockchain.ibm.com:30002",CORE_PEER_PKI_TCA_PADDR="a188020e3aba4ad39c4e266e498163f2-ca.us.blockchain.ibm.com:30002",CORE_PEER_PKI_TLSCA_PADDR="a188020e3aba4ad39c4e266e498163f2-ca.us.blockchain.ibm.com:30002"
OUT - 2016-11-24 01:06:57,903 CRIT Supervisor running as root (no user in config file)
OUT - 2016-11-24 01:06:57,904 INFO supervisord started with pid 14
OUT - 2016-11-24 01:06:58,907 INFO spawned: 'start_peer' with pid 17
OUT - 01:06:58.949 [nodeCmd] serve -> INFO 001[0m Security enabled status: true
OUT - 01:06:58.949 [nodeCmd] serve -> INFO 002[0m Privacy enabled status: false
OUT - 01:06:58.950 [eventhub_producer] start -> INFO 003[0m event processor started
OUT - 01:06:58.950 [db] open -> INFO 004[0m Setting rocksdb maxLogFileSize to 10485760
OUT - 01:06:58.950 [db] open -> INFO 005[0m Setting rocksdb keepLogFileNum to 10
OUT - 01:06:58.956 [crypto] RegisterValidator -> INFO 006[0m Registering validator [peer0] with name [peer0]...
OUT - 01:06:59.164 [crypto] RegisterValidator -> INFO 007[0m Registering validator [peer0] with name [peer0]...done!
OUT - 01:06:59.164 [crypto] InitValidator -> INFO 008[0m Initializing validator [peer0]...
OUT - 01:06:59.168 [crypto] InitValidator -> INFO 009[0m Initializing validator [peer0]...done!
OUT - 01:06:59.168 [chaincode] NewChaincodeSupport -> INFO 00a[0m Chaincode support using peerAddress: a188020e3aba4ad39c4e266e498163f2-vp0.us.blockchain.ibm.com:30002
OUT - [33m01:06:59.168 [sysccapi] RegisterSysCC -> WARN 00b[0m Currently system chaincode does support security(noop,github.com/hyperledger/fabric/bddtests/syschaincode/noop)
OUT - 01:06:59.168 [state] loadConfig -> INFO 00c[0m Loading configurations...
OUT - 01:06:59.168 [state] loadConfig -> INFO 00d[0m Configurations loaded. stateImplName=[buckettree], stateImplConfigs=map[numBuckets:%!s(int=1000003) maxGroupingAtEachLevel:%!s(int=5) bucketCacheSize:%!s(int=100)], deltaHistorySize=[500]
OUT - 01:06:59.168 [state] NewState -> INFO 00e[0m Initializing state implementation [buckettree]
OUT - 01:06:59.168 [buckettree] initConfig -> INFO 00f[0m configs passed during initialization = map[string]interface {}{"maxGroupingAtEachLevel":5, "bucketCacheSize":100, "numBuckets":1000003}
OUT - 01:06:59.168 [buckettree] initConfig -> INFO 010[0m Initializing bucket tree state implemetation with configurations &{maxGroupingAtEachLevel:5 lowestLevel:9 levelToNumBucketsMap:map[3:65 1:3 0:1 2:13 8:200001 7:40001 4:321 9:1000003 6:8001 5:1601] hashFunc:0xab4dc0}
OUT - 01:06:59.169 [buckettree] newBucketCache -> INFO 011[0m Constructing bucket-cache with max bucket cache size = [100] MBs
OUT - 01:06:59.169 [buckettree] loadAllBucketNodesFromDB -> INFO 012[0m Loaded buckets data in cache. Total buckets in DB = [0]. Total cache size:=0
OUT - 01:06:59.169 [genesis] func1 -> INFO 013[0m Creating genesis block.
OUT - 01:06:59.169 [consensus/controller] NewConsenter -> INFO 014[0m Creating consensus plugin pbft
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 015[0m PBFT type = *pbft.obcBatch
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 016[0m PBFT Max number of validating peers (N) = 4
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 017[0m PBFT Max number of failing peers (f) = 1
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 018[0m PBFT byzantine flag = false
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 019[0m PBFT request timeout = 30s
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01a[0m PBFT view change timeout = 30s
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01b[0m PBFT Checkpoint period (K) = 10
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01c[0m PBFT broadcast timeout = 1s
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01d[0m PBFT Log multiplier = 4
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01e[0m PBFT log size (L) = 40
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 01f[0m PBFT null requests disabled
OUT - 01:06:59.170 [consensus/pbft] newPbftCore -> INFO 020[0m PBFT automatic view change disabled
OUT - 01:06:59.170 [consensus/pbft] restoreLastSeqNo -> INFO 021[0m Replica 0 restored lastExec: 0
OUT - 01:06:59.170 [consensus/pbft] restoreState -> INFO 022[0m Replica 0 restored state: view: 0, seqNo: 0, pset: 0, qset: 0, reqBatches: 0, chkpts: 1 h: 0
OUT - 01:06:59.170 [consensus/pbft] newObcBatch -> INFO 023[0m PBFT Batch size = 1000
OUT - 01:06:59.170 [consensus/pbft] newObcBatch -> INFO 024[0m PBFT Batch timeout = 1s
OUT - 01:06:59.170 [nodeCmd] serve -> INFO 025[0m Starting peer with ID=name:"vp0" , network ID=a188020e3aba4ad39c4e266e498163f2, address=a188020e3aba4ad39c4e266e498163f2-vp0.us.blockchain.ibm.com:30002, rootnodes=a188020e3aba4ad39c4e266e498163f2-vp1.us.blockchain.ibm.com:30002,a188020e3aba4ad39c4e266e498163f2-vp2.us.blockchain.ibm.com:30002,a188020e3aba4ad39c4e266e498163f2-vp3.us.blockchain.ibm.com:30002, validator=true
OUT - 01:06:59.171 [consensus/statetransfer] blockThread -> INFO 026[0m Validated blockchain to the genesis block
OUT - 01:06:59.171 [consensus/statetransfer] SyncToTarget -> INFO 027[0m Syncing to target 46b9dd2b0ba88d13233b3feb743eeb243fcd52ea62b81b82b50c27646ed5762fd75dc4ddd8c0f200cb05019d67b592f6fc821c49479ab48640292eacb3b7c4be for block number 0 with peers []
OUT - 01:06:59.171 [consensus/statetransfer] blockThread -> INFO 028[0m Validated blockchain to the genesis block
OUT - 01:06:59.171 [consensus/pbft] ProcessEvent -> INFO 029[0m Replica 0 application caught up via state transfer, lastExec now 0
OUT - 01:06:59.177 [rest] StartOpenchainRESTServer -> INFO 02a[0m Initializing the REST service on 0.0.0.0:5002, TLS is enabled.
OUT - [31m01:06:59.456 [peer] handleChat -> ERRO 02b[0m Error handling message: Peer FSM failed while handling message (DISCHELLO): current state: created, error: transition canceled with error: Error registering Handler: Duplicate Handler error: {name:"vp2" a188020e3aba4ad39c4e266e498163f2-vp2.us.blockchain.ibm.com:30002 VALIDATOR �a�}�%��碱B���]y�l�r����6�}
OUT - 2016/11/24 01:07:00 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 172.16.10.116:30002: getsockopt: connection refused"; Reconnecting to {"a188020e3aba4ad39c4e266e498163f2-vp3.us.blockchain.ibm.com:30002"
Run Hyperledger fabric CA Server and peer as test network. Deploy cp-web. It gives following error:-
{ name: 'query() resp error', code: 400, details: { code: -32003, message: 'Query failure', data: 'Error when querying chaincode: Error:Failed to launch chaincode spec(Could not get deployment transaction for bc25e42864477feeeedbfb5fecb7fea0c5bba627f9af2acf9c19746f705e671019dd04c1f7f7282f62a7cbefba1780d78b27507e777b3620713d7df37131442f - LedgerError - ResourceNotFound: ledger: resource not found)' } }