op-node get stuck after upgrading to the v1.13.0 version

[unclezoro]

The log:

Apr 26 01:04:50 ip-xx t=2025-04-26T01:04:50+0000 lvl=warn msg="Deriver system is resetting" err="reset: cannot continue derivation until Engine has been reset"
Apr 26 01:05:42 ip-xx: t=2025-04-26T01:05:42+0000 lvl=warn msg="failed to notify engine driver of new L2 payload" err="context deadline exceeded" id=0x433632bfd1487ed0e42a9fd76375e82d84ae76fd8d8ddcefa326ccfd80b5c980:29420082

Version:

# ./op-node --version
op-node version v1.13.0-5f003211-1743511639

The geth client did not receive notification from op-node so that it stop importing block as well, but if I attach to the flag to --synctarget=xxx to geth command, it can go on for a while, so I think the issue happens on op-node. I used the --synctarget=xxx flag to sync from 5 days ago, will this cause the problem? Here is the log from op-geth:

INFO [04-26|00:56:59.410] Loaded most recent local block           number=29,419,480 hash=7be2d7..f08dc2 age=11m52s
INFO [04-26|00:56:59.410] Loaded most recent local finalized block number=29,127,579 hash=34ca83..ca7eb2 age=6d18h21m
INFO [04-26|00:56:59.410] Loaded last snap-sync pivot marker       number=27,165,263
INFO [04-26|00:56:59.434] Initialized transaction indexer          range="last 2350000 blocks"
INFO [04-26|00:56:59.434] Initialising Ethereum protocol           network=8453         dbversion=9

The local finalized block number seems quite old

What can I do to resolve this?