Open StefanoVerrilli opened 1 year ago
I am getting this error when running test The method eth_sendTransaction is not supported. Use eth_sendRawTransaction to send a signed transaction to Besu
@adityajoshi12 eth_sendRawTransaction needs a signer to sign the transaction. setting the private key to the network config may help. good luck
{
"caliper": {
"blockchain": "ethereum",
"command": {}
},
"ethereum": {
"url": "ws://127.0.0.1:8542",
"fromAddressSeed": "0x3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580",
"gasPrice": 0,
"chainId": 1337,
@StefanoVerrilli Hi~ I have the same issue as you, How is it going? The failed transaction made a nonce gap in the txpool due to some of my transactions being stuck in there... seeking a solution but have no idea...
@adityajoshi12
you can add the fromAddressSeed to resolve you problem.
"fromAddressSeed":"0x8b12a749f7606741db03a4b5c912e846f346101fce9d7a632431b0bae3fc9060",
@StefanoVerrilli Hi~ I found the old version of besu doesn't have this issue, I tried besu-21.10.6, there is no "invalid params" error anymore. Seems it is a bug of besu project...
Hi @shubham-edx @cai-dclab
I am getting this error with besu network
2023.04.22-12:16:10.292 error [caliper] [ethereum-connector] Failed tx on simple calling method open nonce 0x1f7
2023.04.22-12:16:10.292 error [caliper] [ethereum-connector] Error: Returned error: Transaction nonce is too distant from current sender nonce
@adityajoshi12 hi ~
I think you are using besu version higher than 21.x, they added a flag tx-pool-limit-by-account-percentage
to limit the sender's transaction. set it to 1 to release the limitation maybe will solve this problem.
run the node with flag --tx-pool-limit-by-account-percentage=1 or add tx-pool-limit-by-account-percentage="1" to your config.toml file if you are using config file.
@adityajoshi12 hi ~ I think you are using besu version higher than 21.x, they added a flag
tx-pool-limit-by-account-percentage
to limit the sender's transaction. set it to 1 to release the limitation maybe will solve this problem.run the node with flag --tx-pool-limit-by-account-percentage=1 or add tx-pool-limit-by-account-percentage="1" to your config.toml file if you are using config file.
I ran into the "Invalid Params" problem even I set the flag, how did you solve this?
@chenqping Yeah, I am also facing this problem. Set a lower txNumber and temporarily solve this problem. But not all the time. I don't know what limitation is it. Maybe is the pending transaction percentage as the number is floating. Seems you are also struggling with Caliper and Besu. 有兴趣微信交流吗?
@chenqping Yeah, I am also facing this problem. Set a lower txNumber and temporarily solve this problem. But not all the time. I don't know what limitation is it. Maybe is the pending transaction percentage as the number is floating. Seems you are also struggling with Caliper and Besu. 有兴趣微信交流吗? yeah, can ping me by chanqping
Which Caliper version are you using?
0.5.0
Which Node.JS version are you using?
v16.18.0
Which operating system are you using?
MacOS Ventura
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I'm trying to submit a round of transaction to my private besu network with 3 node, sometimes when i start the round i get the error
invalid params
as error. When i enabled the logging in besu i see the message: Ex. Invalid transaction: transaction nonce 613 does not match sender account nonce 562.What was the observed incorrect behavior?
Caliper stacks and the other transactions are marked as unfinished
![Screenshot 2022-12-26 at 11 28 04](https://user-images.githubusercontent.com/74413257/209538406-ae1abfb6-dd49-44f7-be1a-e873337c06e0.png)
Please provide the error logs and their surroundings.
Please provide your benchmark configuration file content, if possible.
Please provide your network configuration file content, if possible.
Please provide your workload module content, if possible.
Please provide any additional information you deem relevant to the error.
No response