Hi, Just making a small update. I received another answer that suggested to do a peer node reset: Took a backup of peer docker container Took a backup of respective couchdb's data Stopped the chaincod

#fabric #database #consensus

Meant to say "Restart the two peers in org1"... Dave Enyeart "David Enyeart" ---11/06/2019 08:07:14 PM---Often times issues like this are related to gossip misconfiguration. Restart the two peers in o

#fabric #database #consensus

Often times issues like this are related to gossip misconfiguration. Restart the two peers in org2 and then look at the peer logs. You should see some messages like this if everything is working well:

#fabric #database #consensus

Hi to all, Currently, in my setup, I have 2 organizations with 2 peers each. Also have 2 Orderers, one per each organization, and a CA per Organization too. They have a Kafkas and Zookeepers consensus

#fabric #database #consensus

From the error, I assume you are trying to connect to MySQL over TLS. Looks like MySQL auto-generated a server certificate with a Common Name or SAN of "MySQL_Server_8.0.17_Auto_Generated_Server_Certi

#fabric-ca #ssl #database

Hey, I was trying to configure Fabric-CA with mysql and PostgreSQL for using LDAP. I'm not able to initialize the db due to some ssl certificate issue. And when I start my fabric-ca-server then these

#fabric-ca #ssl #database

Hi all, following the indications here: https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/users-guide.html#configuring-the-database I'm trying to understand how to correctly set Fabric-CA wi

#database #ssl #fabric-ca

The different revs does not indicate a data correctness problem. You may see this for example if one peer crashes while writing to state database. When the peer is restarted it will detect that it was

#fabric #database

Hi to all, currently using a network with Kafka ordering service, with 2 orderers and 4 peers. Checking data from the couchdb mychannel_mychannel database on all peers i can see some differences on th

#fabric #database

Hi, https://lists.hyperledger.org/g/fabric/topic/how_to_gethistoryforkey_on_a/32567164?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,32567164 Please refer to the above link. Regards, Soumya

#fabric #fabric-questions #database

just as the question in the title, I know we have getHistoryByKey, but it returns all results how do we get the status of the blockchain at a certain date time? or, maybe how to get the history for a

#fabric #fabric-questions #database

JH, I found the root cause, it is indeed a bug in history db reporting for blocks in multiples of 256. Fortunately the history db content is correct, the bug is on the query side. Opened bug https://j

#database

Dear Dave, I checked all the transactions in ledger and they are marked as valid, no invalidation message in peer logs. Then I stopped peers, delete the history database, and restart peers, after the

#database

Hi Ajaya - The state database represents the latest know value of any given key. It can always be rebuilt from the actual ledger itself. So if you delete the state database, it will be automatically r

#fabric #database

Hi everyone, I would like to know that if by any reason my statedb (couchDB) loses data or is changed using fauxton by any user. Then how can I make it to synchronize again with the blockchain's world

#fabric #database

Perhaps a couple of the transactions got invalidated? Is there any invalidation messages in peer logs? You can stop peer, delete the history database directory at /var/hyperledger/production/historyLe

#database

Hello, I was using fabric 1.4.1 with Kafka ordering service, CouchDB as stateDB, Java SDK and Java chaincode. The test is about get data histories for same key from fabric. I used the function GetHist

#database

Hi Jonathan Correct Oh yes, let me correct my statement: have as many peers *from the owning organisation* as possible listen for events and perform the upload/update. Cheers, Ale

#fabric #database

Hi Ale, Thanks a lot for taking the time to respond. With either option you will have to build some logic to ensure atomicity of updates. In option 1, if your application server crashes after a DB upd

#fabric #database

Jonathan I have no direct experience with this use case but I can offer you some generic advice. With either option you will have to build some logic to ensure atomicity of updates. In option 1, if yo

#fabric #database