Bor Out of sync

WARN [09-01|14:26:17.804] Synchronisation failed, dropping peer peer=fed36c01dd11a70500c989961f569a5775002ffc6966550cc9ca8aef679d2efb err=“retrieved hash chain is invalid: invalid merkle root (remote: 2a2759da0bed957c844f9e26fafdd45458173712a465a8e4b65c30fdef2d584a local: 116e90e996db6fe39231a8a92b8d463197c98d4d5c9ce0c3c8e347bee67f245d)”

WARN [09-01|14:26:24.071] Synchronisation failed, dropping peer peer=fed36c01dd11a70500c989961f569a5775002ffc6966550cc9ca8aef679d2efb err=timeout
WARN [09-01|14:26:25.616] Synchronisation failed, dropping peer peer=fe67874e7c1bbb868a7ea8c0d5927a12285ea35ed968c372458511e0e663ae2c err=“action from bad peer ignored: returned headers 192 != requested 1”
WARN [09-01|14:26:25.616] Synchronisation failed, retrying err=“peer is unknown or unhealthy”
WARN [09-01|14:26:25.616] Synchronisation failed, retrying err=“peer is unknown or unhealthy”
ERROR[09-01|14:26:29.460] Snapshot extension registration failed peer=89027a8b err=“peer connected on snap without compatible eth support”
ERROR[09-01|14:26:36.263] Snapshot extension registration failed peer=78e19f52 err=“peer connected on snap without compatible eth support”
ERROR[09-01|14:26:42.818] Snapshot extension registration failed peer=04dfa983 err=“peer connected on snap without compatible eth support”

The current height is 18450492 and will not be updated.

eth.syncing
{
currentBlock: 18450492,
highestBlock: 18615139,
knownStates: 0,
pulledStates: 0,
startingBlock: 18479498
}

My startup script:
bor --datadir /root/matic/bordata --port 30303 --http --http.addr 0.0.0.0 --http.vhosts * --http.corsdomain * --http.port 18545 --ipcpath /root/matic/bordata/bor.ipc --http.api eth,net,web3,personal,txpool --networkid 137 --syncmode full --txpool.nolocals --txpool.accountslots 16 --txpool.globalslots 131072 --txpool.accountqueue 64 --txpool.globalqueue 131072 --txpool.lifetime 1h30m0s --cache 4096 --maxpeers 200 --bootnodes enode://0cb82b395094ee4a2915e9714894627de9ed8498fb881cec6db7c65e8b9a5bd7f2f25cc84e71e89d0947e51c76e85d0847de848c7782b13c0255247a6758178c@44.232.55.71:30303,enode://88116f4295f5a31538ae409e4d44ad40d22e44ee9342869e7d68bdec55b0f83c1530355ce8b41fbec0928a7d75a5745d528450d30aec92066ab6ba1ee351d710@159.203.9.164:30303

Who has encountered this problem and how to solve it。

Hello @mayong82
Thanks for reaching to polygon Forums. Customer service may take some time to respond due to a large number of requests. We believe your case will be resolved as soon as possible. Kindly visit the polygon support live chat website