Not able to mine transactions

vasa-develop commented 5 years ago

System information

Geth version: geth version

WARN [09-13|22:33:19.148] Sanitizing cache to Go's GC limits provided=1024 updated=666 Geth Version: 1.8.18-stable Git Commit: 664c2ab20af384c5b350aabf5f6307327d8de09e Quorum Version: 2.2.5 Architecture: amd64 Protocol Versions: [63 62] Network Id: 1337 Go Version: go1.10.1 Operating System: linux GOPATH= GOROOT=/usr/local/go OS & Version: Windows/Linux/OSX

Branch, Commit Hash or Release: git status

commit 664c2ab20af384c5b350aabf5f6307327d8de09e Author: Nguyen Kien Trung trung.n.k@gmail.com Date: Tue Aug 27 15:17:59 2019 -0400

p2p/enode, p2p/discv5: fix URL parsing test for go 1.11.13 (#810)

Other Details

I have set up a custom network on 5 quorum nodes(constellation), on 5 different ubuntu 16.10, t2.medium machines on AWS, using the 7nodes example.
Consensus used: Istanbul PBFT

Expected behaviour

Should able to deploy the contracts (mining the transactions)

Actual behaviour

I can't share the contract here, but I will try to provide as much detail as I can.

There are 3 observations:

When I try to deploy the contract using truffle, with the following config, I get the following errors:

Config

module.exports = {
  // See <http://truffleframework.com/docs/advanced/configuration>
  // to customize your Truffle configuration!
  networks: {
    development: {
      host: "NODE_1_IP",
      port: 22000,
      network_id: "*", // Match any network id
      gasPrice: 0,
      gas: 4600000
    }
  }
}

Error Stack Trace

err2

2. When I try to deploy the contract on Remix, with gasLimit: 3000000, I don't get the out of gas error. But now somehow, the new block is not mined. Below is the stack trace pic.

err1

3. When I run the same contract on a 7 nodes example, hosted on a single ubuntu 16.10, t2.medium machine, it works.

Steps to reproduce the behavior

The code for the 5 quorum nodes is public:

Use these repos to set up a network of 5 nodes on different machines and then try to deploy a contract, using truffle.

What I have already tried to fix the issue

I have already tried the fixes mentioned in #700 , but still no luck.

@jpmsam @fixanoid Let me know if you need any other details.

fixanoid commented 4 years ago

@vasa-develop is the genesis you are using been generated using istanbul-tools or have you reused one from quorum-examples? Are blocks increasing in your setup?

vasa-develop commented 4 years ago

@fixanoid

is the genesis you are using been generated using istanbul-tools or have you reused one from quorum-examples?

I reused the genesis from the quorum-examples. Can you point where I can find the steps/instructions to generate genesis from the Istanbul-tools?

Are blocks increasing in your setup?

No. The blocks are not increasing. Here is a trace.

err-quorum

vasa-develop commented 4 years ago

This can be a possible issue: https://github.com/jpmorganchase/istanbul-tools/pull/8

I will try setting up the network using the Getting Started Docs and see if it works or not.

jbhurat commented 4 years ago

Hi @vasa-develop, are you able to deploy the contracts after starting the network using the Getting Started Docs?

vasa-develop commented 4 years ago

@jbhurat Yes, but right now I'm having issues in sending transactions. The transaction nonce doesn't seem to increase after I send the transaction, so it works for only nonce=0.

jbhurat commented 4 years ago

I see that you closed this issue. Does it mean its working for you now?

vasa-develop commented 4 years ago

@jbhurat Nope, I opened a new issue here: https://github.com/jpmorganchase/quorum/issues/822

Consensys / quorum