For finding the peer files, I find it easier to change the peer's volume in docker-compose-test-net.yaml (if using test network) to a local directory like this (last entry): volumes: -

Every transaction has to be submitted from a client application, it could be a different client application though. Calling it a '2nd transaction' was misleading on my part though... the '1st' one

Hello, A peer out of a network of 3 is having problems validating the messages from the gossip protocol: Failed validating identity message: Peer Identity { "CN": "XXXXXXXXXXXXXXXXXXXXXX",

Hello; Each chaincode language uses a 'natural-to-the-language' logging library, eg java.util.Logging or winston. The user's implementation likewise can hook into these libraries. For a typical

Hi Dave,Follow up question to the approach you suggested - does the 2nd transaction then have to be initiated from the client application? Thanks,Samyak Jain

Dear Community, We are designing an application with a chaincode that holds asset information including product quantity. One of the functions the chaincode needs to support is aggregating multiple

Hi Team, I have a kubernetes setup of HLF2.2 with Golang Chaincode and Nodejs SDK. I am performing load test on the network, when i try with 250 Concurrent thread, it shows unexpectedly chaincode

Thank you for your help. I was in wrong place. Yes, you are right. The container just started once we invoke. Thanks again, Jay.

I can't seem to find that file. I can't check from inside the peer, because the peer exited. If I try to run "docker-compose run" with the peer id, it says "service not found", which seems expected,

Hi Tomás, I had seen something similar in a test flake in the past and the issue was a race condition between the closing of the levelDB and acquiring an iterator. I am not sure if that's app;icable

Hi Fabric experts, I am attempting to develop a methodology to retrieve logs from the chaincode, in order to visualize in Kibana through ELK infrastructure. At the moment, I am retrieving chaincode

I was reading about similar issues in fabric version 1.4.2 (the images I'm using on my containers are 1.4.1, so I'm not sure if it is related at all or not), and how it was related to a certain

When you submit a transaction to ordering, it is not guaranteed to get ordered into a block. If an orderer encounters an issue (as it looks like yours has due to stress), the transaction may not get

You would need to provide the full stack trace from the panic message in order to troubleshoot. Dave Enyeart "Tomás Peixinho" ---02/10/2021 01:34:13 PM---Good afternoon fellow colleagues, I'm

Good afternoon fellow colleagues, I'm developing an application using Hyperledger Fabric and I've found a weird error that I'm not sure how to fix. I'm running everything on just one machine, with two

You should not upgrade a 2nd or 3rd time. Again - 'Upgrade' is a transaction on the channel, therefore you only need to do it once for the whole channel, not per peer or per organization. The

Hi David, Thank you for your response. If you see below log, I first install on 4 peers. And then upgrade two peers with success. And third one is failed. Actually, my problem is I have only two

Actually, taking a quick look at the ECDSA CryptoSuite implementation in the Node SDK, it seems to allow 384 to be specified as a key size (which maps to the P-384 curve). So rather than implementing

Hi Alejo, I am really glad that you pinned down the problem. I think the reason is that the CLI (written on Go) is using the Go crypto support which allows it to generate a signature from a hash

Hi. My team is running a couple of stress tests over HLF 2.3.0 in a network with 3 orderers and 2 peers (each peer is of different org), sending an array of JSON data through an API developed with