I encountered the problem of `Ignoring already known beacon payload` and the node got stuck
bijianing97 opened this issue · 0 comments
bijianing97 commented
log is
WARN [06-24|01:23:53.539] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=37m46s
WARN [06-24|01:23:59.818] Served eth_sendRawTransaction conn=219.73.35.24:8153 reqid=2468 duration=262.753025ms err="nonce too low: next nonce 128, tx nonce 127"
WARN [06-24|01:24:08.666] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=38m1s
WARN [06-24|01:24:09.903] Served eth_sendRawTransaction conn=219.73.35.24:62784 reqid=2479 duration=290.021816ms err="nonce too low: next nonce 128, tx nonce 127"
WARN [06-24|01:24:23.852] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=38m16s
WARN [06-24|01:24:38.876] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=38m31s
WARN [06-24|01:24:54.066] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=38m47s
WARN [06-24|01:25:09.098] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=39m2s
WARN [06-24|01:25:24.168] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=39m17s
WARN [06-24|01:25:27.787] Served eth_sendRawTransaction conn=219.73.35.24:63648 reqid=13608 duration=266.186027ms err="nonce too low: next nonce 26, tx nonce 25"
WARN [06-24|01:25:38.513] Served eth_sendRawTransaction conn=219.73.35.24:8973 reqid=13621 duration=260.24499ms err="nonce too low: next nonce 26, tx nonce 25"
WARN [06-24|01:25:39.252] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=39m32s
WARN [06-24|01:25:48.806] Served eth_sendRawTransaction conn=219.73.35.24:63774 reqid=25197 duration=257.559647ms err="nonce too low: next nonce 36, tx nonce 35"
WARN [06-24|01:25:52.007] Served eth_sendRawTransaction conn=219.73.35.24:63796 reqid=25210 duration=264.485287ms err="nonce too low: next nonce 36, tx nonce 35"
WARN [06-24|01:25:54.330] Ignoring already known beacon payload number=5,190,076 hash=fdeecc..cfa0b8 age=39m47s
maybe is a op-node problem, I can't find any solution