Date   

Re: Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc

Brett T Logan <brett.t.logan@...>
 

 
You'll need to upgrade to the absolute latest npm package, though I'm not sure if its been released yet, so you may need to use one of the snapshot packages: https://www.npmjs.com/package/fabric-network?activeTab=versions
 
Brett Logan
Software Engineer, IBM Blockchain
Phone: 1-984-242-6890
 
 
 

----- Original message -----
From: tingli_huoh@...
Sent by: fabric@...
To: fabric@...
Cc:
Subject: [EXTERNAL] Re: [Hyperledger Fabric] Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc
Date: Wed, Dec 2, 2020 10:11 PM
 
Hi Nicholas,

Yes. Just checked through <peer version> command and it is running on 2.x
 


Re: Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc

Nicholas Leonardi
 

Check in your package.json if you're using     "fabric-network": "^2.2.0". If you're using 1.4 then it won't work. Also, from 1.4 to 2.2, there is no more fabric-client node package. You can check the documentation here Hyperledger Fabric SDK for Node.js Index




Em quinta-feira, 3 de dezembro de 2020 00:11:07 BRT, tingli_huoh@... <tingli_huoh@...> escreveu:


Hi Nicholas,

Yes. Just checked through <peer version> command and it is running on 2.x


Re: Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc

tingli_huoh@...
 

Hi Nicholas,

Yes. Just checked through <peer version> command and it is running on 2.x


Re: Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc

Nicholas Leonardi
 

Hey Tingli,
Are you running fabric 2.x? 
Those functions won't work on 1.4 

Em quarta-feira, 2 de dezembro de 2020 23:49:58 BRT, tingli_huoh@... <tingli_huoh@...> escreveu:


I think system chaincodes can be invoked from either client SDK or peer CLI.
Under the same fabric environment, I am able to invoke qscc from CLI but having an error when invoking from client SDK.
I was using the same method as invoking user chaincode.
The error reports "peer is not running chaincode qscc" at the code line of network.getContract('qscc')

So, I am wondering how can I invoke qscc from client SDK? Thank you!! 


Invoking qscc from client SDK (V2.0) #fabric-sdk-node #qscc

tingli_huoh@...
 

I think system chaincodes can be invoked from either client SDK or peer CLI.
Under the same fabric environment, I am able to invoke qscc from CLI but having an error when invoking from client SDK.
I was using the same method as invoking user chaincode.
The error reports "peer is not running chaincode qscc" at the code line of network.getContract('qscc')

So, I am wondering how can I invoke qscc from client SDK? Thank you!! 


Updated Event: Hyperledger Fabric Documentation Workgroup call - Western hemisphere #cal-invite

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Fabric Documentation Workgroup call - Western hemisphere

When:
Friday, 4 December 2020
11:00am to 12:00pm
(UTC-05:00) America/New York
Repeats: Weekly on Friday

Where:
https://zoom.us/my/hyperledger.community.backup?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09

Organizer: Pam Andrejko pama@...

Description:
Documentation workgroup call.
Agenda, minutes and recordings :https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group

Join Zoom Meeting
https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
 
Meeting ID: 622 333 6701
Passcode: 475869


Re: Fabric Orderer Doesn't Recognize Org Admin Signature

Bryan Matsuo
 

After more investigation and local experimentation the problem seems to stem from the network not having the v1_4_3 channel capabilities enabled (only v1_4_2), despite the crypto-config for the added org having NodeOUs enabled. It seems this has led to the network not recognizing the org2 certificate with the admin OU as support for Node OUs is part of the v1_4_3 capability set.

Is there a way to fix this given that the network only has two orgs? It seems that updating the capabilities for the channel or manipulating the network MSP structure is not possible because it would require a majority where the second org's signature will not be recognized.

On the other hand is there a way to recreate the network without the capability mismatch while retaining the application data from the existing channel?

Thanks.


Using Fabric Java SDK with v2.3.0 breaks code

vijayrv@...
 

Hi All,
Does the fabric java sdk break with 2.3.0? Here's what I observed. When you try  HFClient.newChannel()
Method used : public Channel newChannel(String name, Orderer orderer, ChannelConfiguration channelConfiguration byte[]... channelConfigurationSignatures
 you get an error : "channel001 expected config block type CONFIG_UPDATE, but got: MESSAGE". 
The same code executes normally when there was a system channel and a channel configtx was created using -outputCreateChannelTx.
Any thoughts?
Regards
Vijay


Private Chaincode Lab - Tue, 12/01/2020 #cal-notice

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Private Chaincode Lab

When:
Tuesday, 1 December 2020
8:00am to 9:00am
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Organizer:
bur@...

Description:
Two of the Hyperleger Labs projects (private data objects and private chain code) are collaborating to develop a "private smart contracts" capability.

Join Zoom Meeting https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Meeting ID: 518 494 7650 Passcode: 475869


Re: HLF Explorer fails to connect to the peer #fabric-questions #blockchain-explorer #fabric-kubernetes

nekia <atsushin@...>
 

Hi,

Thank you for reporting your issue. Hyperledger Explorer Group is right place where sharing this issue.

This 'connection failure' issue has been reported in hyperledger explorer channel. I'm not sure this issue also has same root cause, but it's worthwhile to try the following step to update Explorer image on your local.

There were the following concurrent tx issue (FABN-1646) on fabric-sdk-node v2.2.2 which Explorer is using. It's been resolved in the latest package v2.2.3 but this revision has introduced another issue (FABN-1663) which is critical for Explorer. The fix for this issue has not been released yet, but you can still use the latest snapshot package (2.2.4-snapshot.7).
 
https://jira.hyperledger.org/browse/FABN-1646
https://jira.hyperledger.org/browse/FABN-1663

cd /some/where/blockchain-explorer
# update rev of fabric-network package
npm install fabric-network@2.2.4-snapshot.7
# rebuild Explorer container image
./build_docker_image.sh -e
# apply this image into your runtime

Thanks,
Atsushi


Re: Hyperledger Fabric Operator

Ross Tang <tangross@...>
 

Thank you very much, for your brilliant works.

On Mon, Nov 30, 2020 at 7:08 AM DAVID VIEJO POMATA
<dviejo@...> wrote:

Hi,

We just released the first version of a project to deploy Hyperledger Fabric on Kubernetes using Operators.

It supports:
- Create certificates authorities (CA)
- Create peers
- Create ordering services
- Create resources without manual provisioning of cryptographic material
- Domain routing with SNI using Istio
- Run chaincode as external chaincode in Kubernetes
- Support Hyperledger Fabric 2.2 and 2.3
- Managed genesis for Ordering services
- E2E testing including the execution of chaincodes in KIND

You can find the instructions on GitHub:
https://github.com/kfsoftware/hlf-operator

There's also an external builder operator available at GitHub, which is also used by the operator:
https://github.com/kfsoftware/externalbuilder

Thanks for your attention and feel free to contribute or contact me for any issues :)

Regards.



--
Ross Tang
+852-91937419


Hyperledger Fabric Operator

DAVID VIEJO POMATA
 

Hi,

We just released the first version of a project to deploy Hyperledger Fabric on Kubernetes using Operators.

It supports:
- Create certificates authorities (CA)
- Create peers
- Create ordering services
- Create resources without manual provisioning of cryptographic material
- Domain routing with SNI using Istio
- Run chaincode as external chaincode in Kubernetes
- Support Hyperledger Fabric 2.2 and 2.3
- Managed genesis for Ordering services
- E2E testing including the execution of chaincodes in KIND

You can find the instructions on GitHub:

There's also an external builder operator available at GitHub, which is also used by the operator:

Thanks for your attention and feel free to contribute or contact me for any issues :)

Regards.


Hyperledger Fabric Documentation Workgroup call - Western hemisphere - Fri, 11/27/2020 #cal-notice

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Fabric Documentation Workgroup call - Western hemisphere

When:
Friday, 27 November 2020
4:00pm to 5:00pm
(GMT+00:00) Europe/London

Where:
https://zoom.us/my/hyperledger.community.backup?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09

Organizer:
pama@...

Description:
Documentation workgroup call.
Agenda, minutes and recordings :https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group

Join Zoom Meeting
https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
 
Meeting ID: 622 333 6701
Passcode: 475869


chaincode commit #fabric-chaincode

kokolaki@...
 

Hello,
when chaincode is committed in version 2.x, it is installed with the block that is created on blockchain? and with the code inside that block we interact when we invoke transactions? or just we interact with code that is packaged in the peer container inside path /var/hyperledger/production/lifecycle/chaincodes?
Tnank you.


Node.js SDK: difference between Network.addBlockListener vs EventService.registerBlockEvent #fabric-sdk-node

@secure12
 

What is the difference between the two? When to use which?


Re: Passing an array as argument to chaincode via Node.js SDK #fabric-questions #fabric-chaincode

@secure12
 

I finally succeed to call the function by passing the first parameter with it JSON.strinify-ed, then laster unmarshal it in the chaincode. But I believe there are better ways.


Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere - Fri, 11/27/2020 #cal-notice

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere

When:
Friday, 27 November 2020
6:00am to 7:00am
(GMT+00:00) Europe/London

Where:
https://zoom.us/my/hyperledger.community.backup?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09

Organizer:
pama@...

Description:
Documentation workgroup call.
Agenda, minutes and recordings: https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group


Join Zoom Meeting
https://zoom.us/j/6223336701?pwd=dkJKdHRlc3dNZEdKR1JYdW40R2pDUT09
 
Meeting ID: 622 333 6701
Passcode: 475869


HLF Explorer fails to connect to the peer #fabric-questions #blockchain-explorer #fabric-kubernetes

anton.zaslavskiy@...
 

Hi Community,
 
We're trying to run hlf explorer instance in k8s. Explorer looses a connection to a peer sometimes and outputs an error.
[2020-11-26T12:55:34.394] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at process._tickCallback (internal/process/next_tick.js:63:19) connectFailed: true }
[2020-11-26T12:55:34.397] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.397] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
 

After that it usually stops syncing new blocks and transactions. In order to overcome this we restart hlf explorer whenever there is a "Failed to connect before the deadline" string in the logs, as we couldn't find any other way to check the syncing process.
 
The problem is that when there are several organization added to a channel and thus there are a few blocks (more than 10-20) hlf explorer tries to perform discovery for every synced block and outputs a lot of connection errors during start up. Consequently, our healthcheck gives false negative result.
 
Tried on 1.1.2 and 1.1.3.

Maybe anyone can help with the following questions:
1. Does anybody know the correct way of checking the liveness of the syncing process?
2. What can we do with these "Failed to connect" errors? We tried to increase timeouts with "grpc-wait-for-ready-timeout" and "request-timeout" options, after that we got a different error: "Failed to get discovery result from channel defaultchannel :  { Error: 14 UNAVAILABLE: Connection dropped" because TLS handshake timeout exceeded on peer's side.
 
Info about configuration of the explorer:
  • DISCOVERY_AS_LOCALHOST env is set to false
  • Connection-profile is as follows
    {
    "name": "nw-767-370-1",
    "version": "1.0.0",
    "client": {
    "tlsEnable": false,
    "adminCredential": {
    "id": "***",
    "password": "***"
    },
    "enableAuthentication": false,
    "organization": "RG-488-419-MSP",
    "connection": {
    "timeout": {
    "peer": {
    "endorser": "300"
    },
    "orderer": "300"
    }
    }
    },
    "channels": {
    "defaultchannel": {
    "peers": {
    "nd-980-845-068.***.com": {}
    },
    "connection": {
    "timeout": {
    "peer": {
    "endorser": "6000",
    "eventHub": "6000",
    "eventReg": "6000"
    }
    }
    }
    }
    },
    "organizations": {
    "RG-488-419-MSP": {
    "mspid": "RG-488-419-MSP",
    "fullpath": true,
    "adminPrivateKey": {
    "path": "/var/explorer/msp/adminkey/key.pem"
    },
    "peers": ["nd-980-845-068.***.com"],
    "signedCert": {
    "path": "/var/explorer/msp/admincert/cert.pem"
    }
    }
    },
    "peers": {
    "nd-980-845-068.***.com": {
    "tlsCACerts": {
    "path": "/var/explorer/peer/tls/ca.crt"
    },
    "url": "grpcs://nd-980-845-068.***.com:7051",
    "eventUrl": "grpcs://nd-980-845-068.***.com:7053"
    }
    }
    }
     
 
 
Start up logs of the explorer:


> hyperledger-explorer@1.1.3 app-start /opt/explorer
> ./start.sh

************************************************************************************
**************************** Hyperledger Explorer **********************************
************************************************************************************
[2020-11-26T12:54:41.301] [INFO] Synchronizer - initialize : 60
[2020-11-26T12:54:41.301] [INFO] SyncPlatform - Sync process is started for the network = [network] and client = [nw-155-715-7]
[2020-11-26T12:54:41.302] [INFO] FabricConfig - config.client.tlsEnable false
[2020-11-26T12:54:41.303] [INFO] FabricConfig - FabricConfig, this.config.channels defaultchannel
[2020-11-26T12:54:46.712] [INFO] FabricUtils - generateBlockHash 0
[2020-11-26T12:54:46.721] [INFO] SyncServices - SyncServices.synchNetworkConfigToDB client network channel_name defaultchannel
[2020-11-26T12:54:46.812] [INFO] FabricUtils - generateBlockHash 0
[2020-11-26T12:54:47.640] [INFO] FabricClient - Discovered RG-958-375-MSP [ { mspid: 'RG-958-375-MSP',
endpoint: 'nd-113-392-727.****.com:7051',
name: 'nd-113-392-727.****.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:54:47.641] [INFO] FabricClient - Discovered RG-785-558-MSP [ { mspid: 'RG-785-558-MSP',
endpoint: 'nd-679-110-235.****.com:7051',
name: 'nd-679-110-235.****.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:54:47.642] [INFO] FabricClient - Discovered RG-907-954-MSP [ { mspid: 'RG-907-954-MSP',
endpoint: 'nd-603-674-180.****.com:7051',
name: 'nd-603-674-180.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:54:47.642] [INFO] FabricClient - Discovered RG-837-380-MSP [ { mspid: 'RG-837-380-MSP',
endpoint: 'nd-739-228-632.***.com:7051',
name: 'nd-739-228-632.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:54:47.654] [INFO] FabricClient - Discovered RG-239-893-MSP [ { mspid: 'RG-239-893-MSP',
endpoint: 'nd-423-261-488.***.com:7051',
name: 'nd-423-261-488.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:54:47.654] [INFO] FabricClient - Discovered RG-922-625-MSP [ { mspid: 'RG-922-625-MSP',
endpoint: 'nd-186-074-086.***.com:7051',
name: 'nd-186-074-086.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:54:47.654] [INFO] FabricClient - Discovered RG-954-235-MSP [ { mspid: 'RG-954-235-MSP',
endpoint: 'nd-226-796-011.***.com:7051',
name: 'nd-226-796-011.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:54:47.697] [INFO] FabricGateway - queryInstantiatedChaincodes defaultchannel
[2020-11-26T12:54:47.751] [INFO] FabricGateway - 1: InstalledChaincode {
references: { defaultchannel: References { chaincodes: [Array] } },
package_id:
'freedomDividendContract1:7f3f8622516757155cb0bfd22913c670664812d3b0528d3725684001d174c9d4',
label: 'freedomDividendContract1' }
[2020-11-26T12:54:47.751] [INFO] FabricGateway - 2: References {
chaincodes:
[ Chaincode { name: 'freedomDividendContract', version: '1' } ] }
[2020-11-26T12:54:47.820] [INFO] Sync - Synchronizer pid is 32
[2020-11-26T12:54:47.947] [INFO] FabricEvent - Successfully created channel event hub for [defaultchannel]
[2020-11-26T12:54:47.951] [INFO] FabricUtils - generateBlockHash 1
[2020-11-26T12:54:47.960] [INFO] SyncServices - block_row.blocknum 1
[2020-11-26T12:54:48.003] [INFO] FabricUtils - generateBlockHash 2
[2020-11-26T12:54:48.014] [INFO] SyncServices - block_row.blocknum 2
[2020-11-26T12:54:48.096] [INFO] FabricUtils - generateBlockHash 3
[2020-11-26T12:54:48.110] [INFO] SyncServices - block_row.blocknum 3
[2020-11-26T12:54:48.199] [INFO] FabricUtils - generateBlockHash 4
[2020-11-26T12:54:48.211] [INFO] SyncServices - block_row.blocknum 4
[2020-11-26T12:54:48.215] [INFO] FabricUtils - generateBlockHash 5
[2020-11-26T12:54:48.219] [INFO] SyncServices - block_row.blocknum 5
[2020-11-26T12:54:48.300] [INFO] FabricUtils - generateBlockHash 6
[2020-11-26T12:54:48.399] [INFO] SyncServices - block_row.blocknum 6
[2020-11-26T12:54:48.403] [INFO] FabricUtils - generateBlockHash 7
[2020-11-26T12:54:48.421] [INFO] SyncServices - block_row.blocknum 7
[2020-11-26T12:54:48.424] [INFO] FabricUtils - generateBlockHash 8
[2020-11-26T12:54:48.428] [INFO] SyncServices - block_row.blocknum 8
[2020-11-26T12:54:48.515] [INFO] FabricUtils - generateBlockHash 9
[2020-11-26T12:54:48.628] [INFO] SyncServices - block_row.blocknum 9
[2020-11-26T12:54:48.657] [INFO] FabricUtils - generateBlockHash 10

... up to 125 block

[2020-11-26T12:54:51.195] [INFO] FabricUtils - generateBlockHash 125
[2020-11-26T12:54:51.198] [INFO] SyncServices - block_row.blocknum 125
[2020-11-26T12:55:34.201] [INFO] SyncPlatform - Updating the client network and other details to DB
2020-11-26T12:55:34.208Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.209Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.210Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
2020-11-26T12:55:34.211Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true

... a lot of duplications of the same line

[2020-11-26T12:55:34.296] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at process._tickCallback (internal/process/next_tick.js:63:19) connectFailed: true }
[2020-11-26T12:55:34.296] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at process._tickCallback (internal/process/next_tick.js:63:19) connectFailed: true }
[2020-11-26T12:55:34.296] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at process._tickCallback (internal/process/next_tick.js:63:19) connectFailed: true }
[2020-11-26T12:55:34.297] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at process._tickCallback (internal/process/next_tick.js:63:19) connectFailed: true }

... a lot of duplications of the same line


[2020-11-26T12:55:34.397] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.397] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
[2020-11-26T12:55:34.398] [INFO] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Closing client processor >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.398] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.398] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
[2020-11-26T12:55:34.399] [INFO] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Closing client processor >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.399] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.399] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
[2020-11-26T12:55:34.399] [INFO] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Closing client processor >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.399] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.399] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)


... a lot of duplications of the same line


[2020-11-26T12:55:34.698] [INFO] SyncServices - SyncServices.synchNetworkConfigToDB client network channel_name defaultchannel
[2020-11-26T12:55:34.796] [INFO] FabricUtils - generateBlockHash 0
[2020-11-26T12:55:34.797] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.797] [ERROR] Sync - Error: Client was closed and is not queryable
at process.nextTick (/opt/explorer/node_modules/pg/lib/client.js:535:25)
at process._tickCallback (internal/process/next_tick.js:61:11)
[2020-11-26T12:55:34.797] [INFO] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Closing client processor >>>>>>>>>>>>>>>>>>>>>
2020-11-26T12:55:34.807Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
2020-11-26T12:55:34.807Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server be discoverer nd-113-392-727.***.com url:grpcs://nd-113-392-727.***.com:7051 timeout:3000
[2020-11-26T12:55:34.807] [ERROR] FabricGateway - Failed to get discovery result from channel defaultchannel : { Error: Failed to connect before the deadline on Discoverer- name: be discoverer nd-113-392-727.***.com, url:grpcs://nd-113-392-727.***.com:7051, connected:false, connectAttempted:true
at checkState (/opt/explorer/node_modules/@grpc/grpc-js/build/src/client.js:69:26)
at Timeout.watcherObject.timer.setTimeout [as _onTimeout] (/opt/explorer/node_modules/@grpc/grpc-js/build/src/channel.js:292:17)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10) connectFailed: true }
[2020-11-26T12:55:34.807] [ERROR] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Synchronizer Error >>>>>>>>>>>>>>>>>>>>>
[2020-11-26T12:55:34.808] [ERROR] Sync - TypeError: Cannot use 'in' operator to search for 'peers_by_org' in null
at FabricClient.<anonymous> (/opt/explorer/app/platform/fabric/FabricClient.js:175:32)
at Generator.next (<anonymous>)
at fulfilled (/opt/explorer/app/platform/fabric/FabricClient.js:8:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
[2020-11-26T12:55:34.808] [INFO] Sync - <<<<<<<<<<<<<<<<<<<<<<<<<< Closing client processor >>>>>>>>>>>>>>>>>>>>>

... a lot of duplications of the same line

[2020-11-26T12:55:36.102] [INFO] FabricClient - Discovered RG-837-380-MSP [ { mspid: 'RG-837-380-MSP',
endpoint: 'nd-739-228-632.***.com:7051',
name: 'nd-739-228-632.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.103] [INFO] FabricClient - Discovered RG-239-893-MSP [ { mspid: 'RG-239-893-MSP',
endpoint: 'nd-423-261-488.***.com:7051',
name: 'nd-423-261-488.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.103] [INFO] FabricClient - Discovered RG-922-625-MSP [ { mspid: 'RG-922-625-MSP',
endpoint: 'nd-186-074-086.***.com:7051',
name: 'nd-186-074-086.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.103] [INFO] FabricClient - Discovered RG-954-235-MSP [ { mspid: 'RG-954-235-MSP',
endpoint: 'nd-226-796-011.***.com:7051',
name: 'nd-226-796-011.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.103] [INFO] FabricClient - Discovered RG-958-375-MSP [ { mspid: 'RG-958-375-MSP',
endpoint: 'nd-113-392-727.***.com:7051',
name: 'nd-113-392-727.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.103] [INFO] FabricClient - Discovered RG-785-558-MSP [ { mspid: 'RG-785-558-MSP',
endpoint: 'nd-679-110-235.***.com:7051',
name: 'nd-679-110-235.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.104] [INFO] FabricClient - Discovered RG-907-954-MSP [ { mspid: 'RG-907-954-MSP',
endpoint: 'nd-603-674-180.***.com:7051',
name: 'nd-603-674-180.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.514] [INFO] FabricClient - Discovered RG-954-235-MSP [ { mspid: 'RG-954-235-MSP',
endpoint: 'nd-226-796-011.***.com:7051',
name: 'nd-226-796-011.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.514] [INFO] FabricClient - Discovered RG-958-375-MSP [ { mspid: 'RG-958-375-MSP',
endpoint: 'nd-113-392-727.***.com:7051',
name: 'nd-113-392-727.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.514] [INFO] FabricClient - Discovered RG-785-558-MSP [ { mspid: 'RG-785-558-MSP',
endpoint: 'nd-679-110-235.***.com:7051',
name: 'nd-679-110-235.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.514] [INFO] FabricClient - Discovered RG-907-954-MSP [ { mspid: 'RG-907-954-MSP',
endpoint: 'nd-603-674-180.***.com:7051',
name: 'nd-603-674-180.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.514] [INFO] FabricClient - Discovered RG-837-380-MSP [ { mspid: 'RG-837-380-MSP',
endpoint: 'nd-739-228-632.***.com:7051',
name: 'nd-739-228-632.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.515] [INFO] FabricClient - Discovered RG-239-893-MSP [ { mspid: 'RG-239-893-MSP',
endpoint: 'nd-423-261-488.***.com:7051',
name: 'nd-423-261-488.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.515] [INFO] FabricClient - Discovered RG-922-625-MSP [ { mspid: 'RG-922-625-MSP',
endpoint: 'nd-186-074-086.***.com:7051',
name: 'nd-186-074-086.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-954-235-MSP [ { mspid: 'RG-954-235-MSP',
endpoint: 'nd-226-796-011.***.com:7051',
name: 'nd-226-796-011.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-958-375-MSP [ { mspid: 'RG-958-375-MSP',
endpoint: 'nd-113-392-727.***.com:7051',
name: 'nd-113-392-727.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-785-558-MSP [ { mspid: 'RG-785-558-MSP',
endpoint: 'nd-679-110-235.***.com:7051',
name: 'nd-679-110-235.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-907-954-MSP [ { mspid: 'RG-907-954-MSP',
endpoint: 'nd-603-674-180.***.com:7051',
name: 'nd-603-674-180.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-837-380-MSP [ { mspid: 'RG-837-380-MSP',
endpoint: 'nd-739-228-632.***.com:7051',
name: 'nd-739-228-632.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]
[2020-11-26T12:55:36.901] [INFO] FabricClient - Discovered RG-239-893-MSP [ { mspid: 'RG-239-893-MSP',
endpoint: 'nd-423-261-488.***.com:7051',
name: 'nd-423-261-488.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object] ] } ]
[2020-11-26T12:55:36.902] [INFO] FabricClient - Discovered RG-922-625-MSP [ { mspid: 'RG-922-625-MSP',
endpoint: 'nd-186-074-086.***.com:7051',
name: 'nd-186-074-086.***.com:7051',
ledgerHeight: Long { low: 126, high: 0, unsigned: true },
chaincodes: [ [Object], [Object] ] } ]


 


Context deadline exceeded error #fabric-kubernetes #fabric-questions

anton.zaslavskiy@...
 

Hi Community,
 
Whenever we deploy hlf peers in k8s, especially if there are more than 2-3 of them, the "context deadline exceeded" error happens from time to time while calling peer cli commands (like `peer channel join`). Sometimes it works well, so the problem looks flaky.
 
Impact:
  •  To overcome it we have to retry multiple times while joining the channel.
 
  • I suspect that peers constantly go online and offline due to the same reason.
020-11-19 08:14:13.128 UTC [gossip.channel] reportMembershipChanges -> INFO 10406 [[defaultchannel] Membership view has changed. peers went offline:  [[nd-423-261-488.***.com:7051 ]] , current view:  [[nd-113-392-727.***.com:7051 ] [nd-652-480-342.***.com:7051 ] [nd-679-110-235.***.com:7051 ] [nd-603-674-180.***.com:7051 ] [nd-186-074-086.***.com:7051 ] [nd-766-765-673.***.com:7051 ] [nd-589-874-673.***.com:7051 ] [nd-097-937-249.***.com:7051 ] [nd-226-796-011.***.com:7051 ] [nd-840-816-472.***.com:7051 ] [nd-183-749-184.***.com:7051 ]]]
2020-11-19 08:14:21.324 UTC [comm.grpc.server] 1 -> INFO 10407 unary call completed grpc.service=discovery.Discovery grpc.method=Discover grpc.request_deadline=2020-11-19T08:14:31.293Z grpc.peer_address=172.31.45.237:41366 grpc.code=OK grpc.call_duration=2.347721ms
2020-11-19 08:14:21.332 UTC [comm.grpc.server] 1 -> INFO 10408 unary call completed grpc.service=discovery.Discovery grpc.method=Discover grpc.request_deadline=2020-11-19T08:14:31.303Z grpc.peer_address=172.31.45.237:41368 grpc.code=OK grpc.call_duration=2.33063ms
2020-11-19 08:14:21.419 UTC [endorser] callChaincode -> INFO 10409 finished chaincode: _lifecycle duration: 0ms channel= txID=dc42f3ed
2020-11-19 08:14:21.419 UTC [comm.grpc.server] 1 -> INFO 1040a unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:41370 grpc.code=OK grpc.call_duration=1.836976ms
2020-11-19 08:14:21.426 UTC [endorser] callChaincode -> INFO 1040b finished chaincode: _lifecycle duration: 2ms channel=defaultchannel txID=8458ebdf
2020-11-19 08:14:21.426 UTC [comm.grpc.server] 1 -> INFO 1040c unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:41372 grpc.code=OK grpc.call_duration=2.859235ms
2020-11-19 08:14:21.571 UTC [comm.grpc.server] 1 -> INFO 1040d unary call completed grpc.service=gossip.Gossip grpc.method=Ping grpc.request_deadline=2020-11-19T08:14:23.571Z grpc.peer_address=172.31.45.237:41382 grpc.peer_subject="CN=nd-423-261-488.***.com,L=Singapore,ST=Singapore,C=SG" grpc.code=OK grpc.call_duration=111.041µs
2020-11-19 08:14:21.572 UTC [lifecycle] CheckCommitReadiness -> INFO 1040e Successfully checked commit readiness of chaincode name 'freedomDividendContract' on channel 'defaultchannel' with definition {sequence: 1, endorsement info: (version: '1', plugin: 'escc', init required: false), validation info: (plugin: 'vscc', policy: '12202f4368616e6e656c2f4170706c69636174696f6e2f456e646f7273656d656e74'), collections: (<nil>)}
2020-11-19 08:14:21.572 UTC [endorser] callChaincode -> INFO 1040f finished chaincode: _lifecycle duration: 6ms channel=defaultchannel txID=c045923e
2020-11-19 08:14:21.573 UTC [comm.grpc.server] 1 -> INFO 10410 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:41378 grpc.code=OK grpc.call_duration=7.370915ms
2020-11-19 08:14:21.592 UTC [comm.grpc.server] 1 -> INFO 10411 unary call completed grpc.service=gossip.Gossip grpc.method=Ping grpc.request_deadline=2020-11-19T08:14:23.592Z grpc.peer_address=172.31.45.237:41384 grpc.peer_subject="CN=nd-423-261-488.***.com,L=Singapore,ST=Singapore,C=SG" grpc.code=OK grpc.call_duration=99.86µs
2020-11-19 08:14:23.128 UTC [gossip.channel] reportMembershipChanges -> INFO 10412 [[defaultchannel] Membership view has changed. peers went online: [[nd-423-261-488.***.com:7051 ]] , current view: [[nd-113-392-727.***.com:7051 ] [nd-652-480-342.***.com:7051 ] [nd-679-110-235.***.com:7051 ] [nd-603-674-180.***.com:7051 ] [nd-186-074-086.***.com:7051 ] [nd-766-765-673.***.com:7051 ] [nd-589-874-673.***.com:7051 ] [nd-423-261-488.***.com:7051 ] [nd-226-796-011.***.com:7051 ] [nd-840-816-472.***.com:7051 ] [nd-183-749-184.***.com:7051 ] [nd-097-937-249.***.com:7051 ]]]
2020-11-19 08:14:24.423 UTC [endorser] callChaincode -> INFO 10413 finished chaincode: qscc duration: 1ms channel=defaultchannel txID=75e53418
2020-11-19 08:14:24.423 UTC [comm.grpc.server] 1 -> INFO 10414 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:32906 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=2.863925ms
2020-11-19 08:14:24.990 UTC [endorser] callChaincode -> INFO 10415 finished chaincode: cscc duration: 0ms channel=defaultchannel txID=937e54a4
2020-11-19 08:14:24.990 UTC [comm.grpc.server] 1 -> INFO 10416 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:32906 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=1.011878ms
2020-11-19 08:14:24.997 UTC [endorser] callChaincode -> INFO 10417 finished chaincode: qscc duration: 1ms channel=defaultchannel txID=324f411c
2020-11-19 08:14:24.997 UTC [comm.grpc.server] 1 -> INFO 10418 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:32906 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=2.499983ms
2020-11-19 08:14:25.524 UTC [comm.grpc.server] 1 -> INFO 10419 unary call completed grpc.service=discovery.Discovery grpc.method=Discover grpc.peer_address=172.31.45.237:41388 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=965.549µs
2020-11-19 08:14:25.617 UTC [endorser] callChaincode -> INFO 1041a finished chaincode: lscc duration: 2ms channel=defaultchannel txID=061c3bb8
2020-11-19 08:14:25.617 UTC [comm.grpc.server] 1 -> INFO 1041b unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:32906 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=3.285879ms
2020-11-19 08:14:25.623 UTC [endorser] callChaincode -> INFO 1041c finished chaincode: _lifecycle duration: 0ms channel=defaultchannel txID=c11b3d5b
2020-11-19 08:14:25.624 UTC [comm.grpc.server] 1 -> INFO 1041d unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.31.45.237:32906 grpc.peer_subject="CN=fabric-common" grpc.code=OK grpc.call_duration=2.003268ms
2020-11-19 08:14:26.338 UTC [comm.grpc.server] 1 -> INFO 1041e unary call completed grpc.service=gossip.Gossip grpc.method=Ping grpc.request_deadline=2020-11-19T08:14:28.338Z grpc.peer_address=172.31.45.237:41390 grpc.peer_subject="CN=nd-097-465-953.***.com,L=Portland,ST=Oregon,C=US" grpc.code=OK grpc.call_duration=129.671µs
2020-11-19 08:14:27.067 UTC [comm.grpc.server] 1 -> INFO 1041f unary call completed grpc.service=gossip.Gossip grpc.method=Ping grpc.request_deadline=2020-11-19T08:14:29.067Z grpc.peer_address=172.31.45.237:41392 grpc.peer_subject="CN=nd-097-465-953.***.com,L=Portland,ST=Oregon,C=US" grpc.code=OK grpc.call_duration=127.27µs
2020-11-19 08:14:28.128 UTC [gossip.channel] reportMembershipChanges -> INFO 10420 [[defaultchannel] Membership view has changed. peers went online: [[nd-097-465-953.***.com:7051 ]] , current view: [[nd-186-074-086.***.com:7051 ] [nd-766-765-673.***.com:7051 ] [nd-589-874-673.***.com:7051 ] [nd-097-465-953.***.com:7051 ] [nd-113-392-727.***.com:7051 ] [nd-652-480-342.***.com:7051 ] [nd-679-110-235.***.com:7051 ] [nd-603-674-180.***.com:7051 ] [nd-183-749-184.***.com:7051 ] [nd-097-937-249.***.com:7051 ] [nd-423-261-488.***.com:7051 ] [nd-226-796-011.***.com:7051 ] [nd-840-816-472.***.com:7051 ]]]
2020-11-19 08:14:31.325 UTC [comm.grpc.server] 1 -> INFO 10421 unary call completed grpc.service=discovery.Discovery grpc.method=Discover grpc.request_deadline=2020-11-19T08:14:41.289Z grpc.peer_address=172.31.45.237:41394 grpc.code=OK grpc.call_duration=1.644114ms
  •  Additionally, sometimes peers just stuck and go offline, but their /healthz endpoint works and responds with 200. Restart of the peer helps though.
2020-11-26 04:40:42.992 UTC [comm.grpc.server] 1 -> INFO 1f04 streaming call completed grpc.service=protos.Deliver grpc.method=DeliverFiltered grpc.peer_address=172.31.37.66:62660 grpc.peer_subject="CN=fabric-common" error="context finished before block retrieved: context canceled" grpc.code=Unknown grpc.call_duration=14h50m10.591964512s
2020-11-26 04:40:46.771 UTC [gossip.comm] sendToEndpoint -> WARN 1f05 Failed obtaining connection for 172.31.36.151:7051, PKIid:4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf reason: context deadline exceeded
2020-11-26 04:40:46.772 UTC [gossip.discovery] expireDeadMembers -> WARN 1f06 Entering [4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf]
2020-11-26 04:40:46.772 UTC [gossip.discovery] expireDeadMembers -> WARN 1f07 Closing connection to Endpoint: nd-136-026-294.***.com:7051, InternalEndpoint: 172.31.36.151:7051, PKI-ID: 4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf, Metadata:
2020-11-26 04:40:46.772 UTC [gossip.discovery] expireDeadMembers -> WARN 1f08 Exiting
2020-11-26 04:40:49.775 UTC [gossip.comm] sendToEndpoint -> WARN 1f09 Failed obtaining connection for 172.31.36.151:7051, PKIid:4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf reason: context deadline exceeded
2020-11-26 04:40:51.299 UTC [gossip.channel] reportMembershipChanges -> INFO 1f0a [[defaultchannel] Membership view has changed. peers went offline: [[nd-136-026-294.***.com:7051 172.31.36.151:7051]] , current view: []]
2020-11-26 04:40:52.777 UTC [gossip.comm] sendToEndpoint -> WARN 1f0b Failed obtaining connection for 172.31.36.151:7051, PKIid:4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf reason: context deadline exceeded
2020-11-26 04:40:55.779 UTC [gossip.comm] sendToEndpoint -> WARN 1f0c Failed obtaining connection for 172.31.36.151:7051, PKIid:4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf reason: context deadline exceeded
2020-11-26 04:40:56.073 UTC [gossip.election] beLeader -> INFO 1f0d f6b42b2b2aca8b81935e5bb3e1e8ffcec568bcb64f3b522737cb3bfd8342c846 : Becoming a leader
2020-11-26 04:40:56.074 UTC [gossip.service] func1 -> INFO 1f0e Elected as a leader, starting delivery service for channel defaultchannel
2020-11-26 04:40:56.074 UTC [deliveryClient] StartDeliverForChannel -> INFO 1f0f This peer will retrieve blocks from ordering service and disseminate to other peers in the organization for channel defaultchannel
2020-11-26 04:40:58.781 UTC [gossip.comm] sendToEndpoint -> WARN 1f10 Failed obtaining connection for 172.31.36.151:7051, PKIid:4c59fb2758a919f5857acb1607d557d110d3c2f9a995500a649d75e75307bdcf reason: context deadline exceeded
2020-11-26 04:41:05.424 UTC [core.comm] ServerHandshake -> ERRO 1f11 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33424
2020-11-26 04:41:06.426 UTC [core.comm] ServerHandshake -> ERRO 1f12 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33426
2020-11-26 04:41:08.233 UTC [core.comm] ServerHandshake -> ERRO 1f13 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33456
2020-11-26 04:41:33.427 UTC [core.comm] ServerHandshake -> ERRO 1f14 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33564
2020-11-26 04:41:34.430 UTC [core.comm] ServerHandshake -> ERRO 1f15 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33570
2020-11-26 04:41:36.121 UTC [core.comm] ServerHandshake -> ERRO 1f16 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33574
2020-11-26 04:42:01.430 UTC [core.comm] ServerHandshake -> ERRO 1f17 TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:33688
...
...
2020-11-26 08:51:15.311 UTC [core.comm] ServerHandshake -> ERRO 255b TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:39532
2020-11-26 08:51:16.841 UTC [core.comm] ServerHandshake -> ERRO 255c TLS handshake failed with error remote error: tls: bad certificate server=PeerServer remoteaddress=172.31.36.151:39538
Some details about the network:
  • network has 1 application channel
  • multiple organizations are added to this channel dynamically
  • each organization has it's own anchor peer + each organization may have several "secondary" peers
  • there is only 1 orderer in the network
  • examples of the configurations can't be found below
Orderer:
ADMIN_MSP_PATH: /var/hyperledger/admin_msp
FABRIC_CA_CLIENT_HOME: /var/hyperledger/fabric-ca-client
FABRIC_LOGGING_SPEC: warning
GODEBUG: netdns=go
ORDERER_CFG_PATH: /var/hyperledger/config
ORDERER_FILELEDGER_LOCATION: /var/hyperledger/ledger
ORDERER_GENERAL_BATCHSIZE_MAXMESSAGECOUNT: "10"
ORDERER_GENERAL_BATCHTIMEOUT: 1s
ORDERER_GENERAL_GENESISFILE: /hl_config/genesis/genesis.block
ORDERER_GENERAL_GENESISMETHOD: file
ORDERER_GENERAL_GENESISPROFILE: initial
ORDERER_GENERAL_LEDGERTYPE: file
ORDERER_GENERAL_LISTENADDRESS: 0.0.0.0
ORDERER_GENERAL_LISTENPORT: "7050"
ORDERER_GENERAL_LOCALMSPDIR: /var/hyperledger/msp
ORDERER_GENERAL_LOCALMSPID: RG-488-419-ORD-MSP
ORDERER_GENERAL_LOGLEVEL: debug
ORDERER_GENERAL_MAXWINDOWSIZE: "1000"
ORDERER_GENERAL_ORDERERTYPE: solo
ORDERER_GENERAL_TLS_CERTIFICATE: /var/hyperledger/tls/server/pair/tls.crt
ORDERER_GENERAL_TLS_CLIENTAUTHREQUIRED: "false"
ORDERER_GENERAL_TLS_CLIENTROOTCAS: "/var/hyperledger/tls/client/cert/*"
ORDERER_GENERAL_TLS_ENABLED: "true"
ORDERER_GENERAL_TLS_PRIVATEKEY: /var/hyperledger/tls/server/pair/tls.key
ORDERER_GENERAL_TLS_ROOTCAS: /var/hyperledger/tls/server/cert/cacert.pem
ORDERER_METRICS_PROVIDER: prometheus
ORDERER_OPERATIONS_LISTENADDRESS: 0.0.0.0:8443
Anchor peer of each org
ADMIN_MSP_PATH: /var/hyperledger/admin_msp
CORE_LEDGER_STATE_STATEDATABASE: goleveldb
CORE_LOGGING_CAUTHDSL: warning
CORE_LOGGING_GOSSIP: info
CORE_LOGGING_GRPC: error
CORE_LOGGING_LEDGER: info
CORE_LOGGING_LEVEL: info
CORE_LOGGING_MSP: warning
CORE_LOGGING_PEER: info
CORE_LOGGING_POLICIES: warning
CORE_METRICS_PROVIDER: prometheus
CORE_OPERATIONS_LISTENADDRESS: 0.0.0.0:9443
CORE_PEER_ADDRESS: nd-980-845-068.***.com:7051
CORE_PEER_ADDRESSAUTODETECT: "true"
CORE_PEER_COMMITTER_ENABLED: "true"
CORE_PEER_DISCOVERY_PERIOD: 60s
CORE_PEER_DISCOVERY_TOUCHPERIOD: 60s
CORE_PEER_GOSSIP_BOOTSTRAP: ""
CORE_PEER_GOSSIP_ENDPOINT: ""
CORE_PEER_GOSSIP_EXTERNALENDPOINT: nd-980-845-068.***.com:7051
CORE_PEER_GOSSIP_ORGLEADER: "false"
CORE_PEER_GOSSIP_USELEADERELECTION: "true"
CORE_PEER_ID: nw-767-370-1-nd-980-845-068
CORE_PEER_LISTENADDRESS: 0.0.0.0:7051
CORE_PEER_LOCALMSPID: RG-488-419-MSP
CORE_PEER_MSPCONFIGPATH: /var/hyperledger/msp
CORE_PEER_NETWORKID: nid1
CORE_PEER_PROFILE_ENABLED: "true"
CORE_PEER_TLS_CERT_FILE: /var/hyperledger/tls/server/pair/tls.crt
CORE_PEER_TLS_CLIENTAUTHREQUIRED: "false"
CORE_PEER_TLS_ENABLED: "true"
CORE_PEER_TLS_KEY_FILE: /var/hyperledger/tls/server/pair/tls.key
CORE_PEER_TLS_ROOTCERT_FILE: /var/hyperledger/tls/server/cert/cacert.pem
CORE_VM_ENDPOINT: tcp://localhost:2375
FABRIC_CFG_PATH: /var/hyperledger/fabric_cfg
GODEBUG: netdns=go
ORD_TLS_PATH: /var/hyperledger/tls/ord/cert
PEER_CFG_PATH: /var/hyperledger/config
Secondary peer:
ADMIN_MSP_PATH: /var/hyperledger/admin_msp
CORE_LEDGER_STATE_STATEDATABASE: goleveldb
CORE_LOGGING_CAUTHDSL: warning
CORE_LOGGING_GOSSIP: info
CORE_LOGGING_GRPC: error
CORE_LOGGING_LEDGER: info
CORE_LOGGING_LEVEL: info
CORE_LOGGING_MSP: warning
CORE_LOGGING_PEER: info
CORE_LOGGING_POLICIES: warning
CORE_METRICS_PROVIDER: prometheus
CORE_OPERATIONS_LISTENADDRESS: 0.0.0.0:9443
CORE_PEER_ADDRESS: nd-136-026-294.***.com:7051
CORE_PEER_ADDRESSAUTODETECT: "true"
CORE_PEER_COMMITTER_ENABLED: "true"
CORE_PEER_DISCOVERY_PERIOD: 60s
CORE_PEER_DISCOVERY_TOUCHPERIOD: 60s
CORE_PEER_GOSSIP_BOOTSTRAP: nd-980-845-068.***.com:7051
CORE_PEER_GOSSIP_ENDPOINT: ""
CORE_PEER_GOSSIP_EXTERNALENDPOINT: nd-136-026-294.***.com:7051
CORE_PEER_GOSSIP_ORGLEADER: "false"
CORE_PEER_GOSSIP_USELEADERELECTION: "true"
CORE_PEER_ID: nw-767-370-1-nd-136-026-294
CORE_PEER_LISTENADDRESS: 0.0.0.0:7051
CORE_PEER_LOCALMSPID: RG-488-419-MSP
CORE_PEER_MSPCONFIGPATH: /var/hyperledger/msp
CORE_PEER_NETWORKID: nid1
CORE_PEER_PROFILE_ENABLED: "true"
CORE_PEER_TLS_CERT_FILE: /var/hyperledger/tls/server/pair/tls.crt
CORE_PEER_TLS_CLIENTAUTHREQUIRED: "false"
CORE_PEER_TLS_ENABLED: "true"
CORE_PEER_TLS_KEY_FILE: /var/hyperledger/tls/server/pair/tls.key
CORE_PEER_TLS_ROOTCERT_FILE: /var/hyperledger/tls/server/cert/cacert.pem
CORE_VM_ENDPOINT: tcp://localhost:2375
FABRIC_CFG_PATH: /var/hyperledger/fabric_cfg
GODEBUG: netdns=go
ORD_TLS_PATH: /var/hyperledger/tls/ord/cert
PEER_CFG_PATH: /var/hyperledger/config
 
P.S.
 
I believe these unanswered topics both relate to the same issue:
 
https://lists.hyperledger.org/g/fabric/message/6343
https://lists.hyperledger.org/g/fabric/message/5726?p=,,,20,0,0,0::relevance,,posterid%3A1369019,20,2,0,30700654
 
 


Re: Passing an array as argument to chaincode via Node.js SDK #fabric-questions #fabric-chaincode

@secure12
 

Sorry, I don't quite understand. my_array is a single array here, no?

2221 - 2240 of 11518