'method handler crashed' in deploy.py

[nk307]

Hello there,
When I tried running ./run.sh for my vagrant based quorum setup, I see the error as follows:
contract_CompileDeploySave(contract_source_file=FILE_CONTRACT_SOURCE) File "./deploy.py", line 120, in contract_CompileDeploySave contractAddress = deployContract(contract_interface) File "./deploy.py", line 70, in deployContract tx_hash = w3.toHex( myContract.constructor().transact() ) File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/utils/decorators.py", line 14, in _wrapper return self.method(obj, *args, **kwargs) File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/contract.py", line 842, in transact return self.web3.eth.sendTransaction(transact_transaction) File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/eth.py", line 262, in sendTransaction get_buffered_gas_estimate(self.web3, transaction), File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/utils/transactions.py", line 84, in get_buffered_gas_estimate gas_estimate = web3.eth.estimateGas(gas_estimate_transaction) File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/eth.py", line 303, in estimateGas [transaction], File "/home/kor11137702/testbed/chainhammer/chainhammer/env/lib/python3.6/site-packages/web3/manager.py", line 110, in request_blocking raise ValueError(response["error"]) ValueError: {'code': -32000, 'message': 'method handler crashed'}

The log file using tail -f logs/deploy.py.log:

tail: logs/deploy.py.log: file truncated versions: web3 4.3.0, py-solc: 2.1.0, solc 0.4.25+commit.59dbf8f1.Linux.gpp, testrpc 1.3.4, python 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] web3 connection established, blockNumber = 556, node version string = Geth/v1.9.7-stable-9339be03(quorum-v2.6.0)/linux-amd64/go1.13.10 first account of node is 0xed9d02e382b34818e88B88a309c7fe71E65f419d, balance is 1000000000 Ether WARN: raft consensus did report timestamps in nanoseconds. Is that still the case? nodeName: Quorum, nodeType: Geth, nodeVersion: v1.9.7-stable-9339be03(quorum-v2.6.0), consensus: raft, network: 10, chainName: ???, chainId: -1 unlocked: True unlock: True
Is there something I am missing?
I have modified the RPC address as discussed in the previous #23.

[drandreaskrueger]

well done with the log files.

my code is quite talkative, and gives a lot of output.

helps .

---

if you see such (any) problems, do not use run.sh right away, because it is harder to debug.
run.sh is a complex script which relies on all other called elements to run in perfection.

Instead you go step by step as described here https://github.com/drandreaskrueger/chainhammer/blob/master/docs/azure.md#cloud-connection-attempt as I told you before.

---

'method handler crashed'

I have never before seen the above error, so I might not even be able to help you with this without trying myself.

But I do not have the time right now, to try it myself.

And I do not intend to benchmark it again myself anytime soon, because I have already benchmarked quorum, see e.g. here: https://github.com/drandreaskrueger/chainhammer#results-summary --> "quorum crux IBFT"

---

Go ahead and try to reproduce that now, is probably difficult - unless you go back to the exact old versions that I had been using back then. That might help.

Sorry that I just do not have the time to do your work. You want to benchmark it again, then ... get it working yourself.

I would appreciate if you reported back what you find out.

---

What I can help you now is to explain that error message to you:

tx_hash = w3.toHex( myContract.constructor().transact() )

causes an error. in "./deploy.py"

contractAddress = deployContract(contract_interface)

so the whole contract deployment fails.

Must be some web3 error. Perhaps quorum has changed the RPC protocol for that call, in the meantime? I really don't know.

it fails specifically in this section:

web3.eth.estimateGas(gas_estimate_transaction)

but that is already in the inner workings of the web3 library. I suppose you are using the web3 library version that is specified in the requirements.txt ? Of course, in this fast moving field, that might be long outdated. My measurements were in 2017 if I remember correctly. Or 2018?

---

Good news: All this now explains why in your previous issue you could not see tps.py and send.py interacting, because not even the contract got deployed in the first place.

That is what deploy.py is doing (or in your case, trying to do, but then fails). Until you get that working, do not move forward.

---

If you want to try, go step by step, see e.g. here:
https://github.com/drandreaskrueger/chainhammer/blob/master/docs/azure.md#cloud-connection-attempt

and solve one problem after the other.

look into the Python code where it throws an error, and fix that code.

---

You might need to learn more about quorum. Perhaps they changed the protocol of that

self.web3.eth.sendTransaction(transact_transaction) 

or more specifically this call

web3.eth.estimateGas(...)

but I cannot be sure.

---

No time right now.

Might look at it again in a few months though. If that then still helps you, we can keep this issue open.

---

Good luck. Please keep me posted. Thanks.

[drandreaskrueger]

P.S.:

https://github.com/drandreaskrueger/chainhammer/blob/master/hammer/deploy.py

is not overly complicated code. And it's mostly standalone, it just imports web3connection, unlockAccount from clienttools.

You'll manage. I am sure.

Good luck.