mainnet sync err: miner id does not map to peer that sent message

[TonyS001]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

• lotus daemon - chain sync
• lotus fvm/fevm - Lotus FVM and FEVM interactions
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt/WinningPoSt)
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Lotus Version

1.23.2-dev+mainnet+git.517c0a53b
APIVersion:66816

Repro Steps

No response

Describe the Bug

I start a mainnet node but can't sync. The log shows miner id does not map to peer that sent message.
I attach the log file.
lotus.log

Logging Information

`miner id does not map to peer that sent message`

[arajasek]

@TonyS001 Can you please share the results of lotus sync status and lotus net peers here?

[arajasek]

Moving this issue to Lotus Discussions for help and troubleshooting.

Closing Lotus issue ticket.

[jerry900314]

We downloaded the light version and encountered an issue: "Miner ID does not map to the peer that sent the message and cannot authenticate the message." {"err": "Miner ID does not map to the peer that sent the message", "errVerbose": "Miner ID does not map to the peer that sent the message."} : This issue should be resolved after syncing is completed?? Or any comment?