Closed DzBricks closed 8 months ago
@DzBricks Hi, your node is experiencing this situation because your op-node has not been able to join the p2p network, so it cannot receive the latest blocks from the p2p network in a timely manner. Now its blocks are all from the L1 network. It is recommended that you check the p2p-related configuration. You can also confirm the current p2p connection status of your op-node through the following interface:
curl -X POST -H "Content-Type: application/json" -d '{"id":3, "jsonrpc":"2.0", "method": "opp2p_peers","params":[true]}' http://127.0.0.1:8546
The result of this interface contains the peers that your op-node node is connected to. If it is empty, then there is a problem.
@DzBricks Hi, your node is experiencing this situation because your op-node has not been able to join the p2p network, so it cannot receive the latest blocks from the p2p network in a timely manner. Now its blocks are all from the L1 network. It is recommended that you check the p2p-related configuration. You can also confirm the current p2p connection status of your op-node through the following interface:
curl -X POST -H "Content-Type: application/json" -d '{"id":3, "jsonrpc":"2.0", "method": "opp2p_peers","params":[true]}' http://127.0.0.1:8546
The result of this interface contains the peers that your op-node node is connected to. If it is empty, then there is a problem.
I've found problem.
In https://raw.githubusercontent.com/bnb-chain/opbnb-node-docker/main/scripts/op-node-start.sh :
P2P_BOOTNODES="enr:-J24QGRN1ZLv--bzrqM-qRC-zUlCO4irVVg2bbWOvd3KEFjwLj8qCh54a1ziqic84uQz-2RLVSuNyNAbKEfrNr-STj-GAYoIQDCIgmlkgnY0gmlwhDaykUmHb3BzdGFja4PMAQCJc2VjcDI1NmsxoQJ-_5GZKjs7jaB4TILdgC8EwnwyL3Qip89wmjnyjvDDwoN0Y3CCIyuDdWRwgiMr"
p2p not working with this ENR.
And working with ENR from docs "running-a-local-node".
@DzBricks Hi, your node is experiencing this situation because your op-node has not been able to join the p2p network, so it cannot receive the latest blocks from the p2p network in a timely manner. Now its blocks are all from the L1 network. It is recommended that you check the p2p-related configuration. You can also confirm the current p2p connection status of your op-node through the following interface:
curl -X POST -H "Content-Type: application/json" -d '{"id":3, "jsonrpc":"2.0", "method": "opp2p_peers","params":[true]}' http://127.0.0.1:8546
The result of this interface contains the peers that your op-node node is connected to. If it is empty, then there is a problem.
I've found problem. In https://raw.githubusercontent.com/bnb-chain/opbnb-node-docker/main/scripts/op-node-start.sh :
P2P_BOOTNODES="enr:-J24QGRN1ZLv--bzrqM-qRC-zUlCO4irVVg2bbWOvd3KEFjwLj8qCh54a1ziqic84uQz-2RLVSuNyNAbKEfrNr-STj-GAYoIQDCIgmlkgnY0gmlwhDaykUmHb3BzdGFja4PMAQCJc2VjcDI1NmsxoQJ-_5GZKjs7jaB4TILdgC8EwnwyL3Qip89wmjnyjvDDwoN0Y3CCIyuDdWRwgiMr"
p2p not working with this ENR. And working with ENR from docs "running-a-local-node".
@DzBricks You are right, I am trying to fix the issue with the script, thank you very much for your feedback!
Close issue, given that this problem has been solved.
Hello! I've ran op-node and op-geth from repo opbnb-node-docker. However upon sync completion I'm seeing a very strange behaviour, where op-node regularly stalls for over a minute and then catches up. Op-node logs before start inserting:
How can I do my op-geth receive new block every 1 sec (generated time for new block in opBNB)?
Version: op-node: v0.2.4 and v0.2.5-alpha op-geth: v0.2.2 and v0.2.3-alpha
Params for op-node and op-geth from repo opbnb-node-docker
Hardware: Net: 1Gb/s CPU: AMD Ryzen 9 7950X3D 16-Core Processor Mem: 128GB Storage: SSD >10k IOPS
Please let me know if I can provide any more information, thanks.