Remove approve tx retry explaination in troubleshooting step

This commit is contained in:
IshaVenikar 2024-07-22 14:24:13 +05:30
parent 3456e8692c
commit c0391d19ea

View File

@ -1170,50 +1170,45 @@
## Troubleshooting
- If the ledger channel creation fails, check whether the status of `cerc/fixturenet-eth-geth` is `unhealthy`.
- If the ledger channel creation fails, follow these steps:
```bash
docker ps
```
- If the chain is not producing new blocks, restart the chain.
- Check whether the status of `cerc/fixturenet-eth-geth` is `unhealthy`.
```bash
laconic-so deployment --dir fixturenet-eth-deployment stop
laconic-so deployment --dir fixturenet-eth-deployment start
docker ps
```
- If chain is producing blocks, nodes will wait for certain number of blocks for `Approval` event, and if the node is unable to receive the `Approval` event after certain number of blocks, node will retry the transaction with higher gas (Node will calculate estimated gas limit for new transaction and multiply it with `1.5`)
- If the chain is not producing new blocks, restart the chain.
- Check logs of the node for which ledger channel creation failed
```bash
laconic-so deployment --dir fixturenet-eth-deployment stop
```bash
...
3:41PM ERR event Approval was not emitted approveTxHash=0x533c758b0c7d4b2f5bc40ee2c9c1bc9bc3586e499b1600d4f48e27dd7be18dab
3:41PM INF Resubmitted transaction with higher gas limit gasLimit=69511 approveTxHash=0x96e552de514873e9e87e55fca53f72c02b3f16bdff3eefcf5700338d45e68c52
...
```
laconic-so deployment --dir fixturenet-eth-deployment start
```
- Make curl request to the geth node to get transaction by hash
- Stop the nitro-rpc-client if it is stuck
```bash
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["<approve_tx_hash>"],"id":1}' http://localhost:8545
# Expected output
# For old transaction
# {"jsonrpc":"2.0","id":1,"result":null}
# Check if the new tranasction succeeds
# {"jsonrpc":"2.0","id":1,"result":{"blockHash":"0x34ce3048de5c24b9da9b5f1a19b1707b071d7f88570aa31954ef27b99a119f42","blockNumber":"0x1c4","from":"0xf1ac8dd1f6d6f5c0da99097c57ebf50cd99ce293","gas":"0x10f87","gasPrice":"0xf4247","maxFeePerGas":"0xf424e","maxPriorityFeePerGas":"0xf4240","hash":"0x96e552de514873e9e87e55fca53f72c02b3f16bdff3eefcf5700338d45e68c52","input":"0x095ea7b3000000000000000000000000b2592723b09f42937543f199a305ea6576dcb50600000000000000000000000000000000000000000000000000000000000f4240","nonce":"0x5f","to":"0x71d73e2f0908c003070b5d60f66be8bf4ff0a54e","transactionIndex":"0x0","value":"0x0","type":"0x2","accessList":[],"chainId":"0x4bc","v":"0x0","r":"0x3444047a23970f8f49f5039e3087a6e197a2d0637926b6541f600029040539b2","s":"0x6612446c98d4e0026d6eb63cc861484d6e430c47207730b0c3d6c1b36c294a05","yParity":"0x0"}}
```
- Restart the failed node (For ex. to restart Alice's node)
<!-- TODO: Update with nitro-stack steps -->
- Stop the nitro-rpc-client if it is stuck
- Stop the failed nitro node
- Stop the failed nitro node
```bash
laconic-so deployment --dir l1alice-nitro-deployment stop
```
- Remove that nitro node's durable store located at `~/go-nitro/data/Nitro-address-of-failed-node`
- Remove the node's durable store and create it again
- Restart the node and create ledger channel again
```bash
rm -rf l1alice-nitro-deployment/data/nitro_node_data
mkdir l1alice-nitro-deployment/data/nitro_node_data
```
- Restart the node and create ledger channel again
```bash
laconic-so deployment --dir l1alice-nitro-deployment start
```
## Future enhancements