Archive node sync fails with "Received invalid event id"

I’m trying to sync an archive node (first Mumbai, then mainnet) using the snapshots at https://snapshots.matic.today/

Got heimdall synced, but now I get this for bor:

Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.661] Fetching state sync events               queryParams="from-id=906232&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.683] Fetching state sync events               queryParams="from-id=906282&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.704] Fetching state sync events               queryParams="from-id=906332&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: WARN [10-07|15:19:29.742] Served miner_setEtherbase                conn=195.123.222.16:60284 reqid=1 t="18.495µs" err="the method miner_setEtherbase does not exist/is not available"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.749] Fetching state sync events               queryParams="from-id=906382&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.772] Fetching state sync events               queryParams="from-id=906432&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.794] Fetching state sync events               queryParams="from-id=906482&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.816] Fetching state sync events               queryParams="from-id=906532&to-time=1633429052&limit=50"
Oct 07 15:19:29 beefy bash[80677]: ERROR[10-07|15:19:29.849] Received invalid event id 21482, contract 0xA6FA4fB5f76172d178d61B04b0ecd319C5d1C0aa, data: 0x87a7811f4bfedea3d341ad165680ae306b01aaeacc205d227629cf157dd9f821000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a000000000000000000000000093beca36d5bcdc7be0f9ca38b1b5f5f5292aa859000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb480000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000f5e0b598, txHash: 0x99b7d8d23e06990529a0bfaf0ec7f22976f3709a8248acd223424e9a5ad1d568, logIndex: 95, chainId: 137, time 2021-01-16T08:03:28Z at block 19791040. Requested events until 2021-10-05T12:17:32+02:00. Last state id was 21481
Oct 07 15:19:29 beefy bash[80677]: INFO [10-07|15:19:29.854] Imported new chain segment               blocks=64 txs=173 mgas=99.860 elapsed=6m54.773s mgasps=0.241  number=19,791,040 hash=9dfc00..a603a4 age=2d2h59m dirty=0.00B
Oct 07 15:19:30 beefy bash[80677]: WARN [10-07|15:19:30.387] Caller gas above allowance, capping      requested=9,223,372,036,854,775,807 cap=50,000,000
Oct 07 15:19:30 beefy bash[80677]: WARN [10-07|15:19:30.387] Caller gas above allowance, capping      requested=9,223,372,036,854,775,807 cap=50,000,000
Oct 07 15:19:30 beefy bash[80677]: INFO [10-07|15:19:30.387] Fetching state updates from Heimdall     fromID=21482 to=2021-10-05T12:19:44+02:00
Oct 07 15:19:30 beefy bash[80677]: INFO [10-07|15:19:30.387] Fetching state sync events               queryParams="from-id=21482&to-time=1633429184&limit=50"
Oct 07 15:19:30 beefy bash[80677]: INFO [10-07|15:19:30.419] Fetching state sync events               queryParams="from-id=21532&to-time=1633429184&limit=50"

Seems to repeat like this in end endless loop.

heimdall version: 0.2.2
bor version: 1.10.9-unstable (git branch v0.2.8)

Bor was started like this:

bor --datadir /home/mumbai/.bor/data --port 40303 --http --http.addr 0.0.0.0 --http.vhosts * --http.corsdomain * --http.port 18545 --ipcpath /home/mumbai/.bor/data/bor.ipc --http.api eth,net,web3,txpool,bor --syncmode full --networkid 80001 --miner.gaslimit 20000000 --miner.gastarget 20000000 --txpool.nolocals --txpool.accountslots 16 --txpool.globalslots 131072 --txpool.accountqueue 64 --txpool.globalqueue 131072 --txpool.lifetime 1h30m0s --maxpeers 200 --metrics --pprof --pprof.port 17071 --pprof.addr 0.0.0.0 --bootnodes enode://320553cda00dfc003f499a3ce9598029f364fbb3ed1222fdc20a94d97dcc4d8ba0cd0bfa996579dcc6d17a534741fb0a5da303a90579431259150de66b597251@54.147.31.250:30303 --gcmode archive --bor.heimdall http://localhost:11317

I have heimdalld start and heimdalld rest-server running (using non-standard ports because I want to use the standard ports for mainnet.

I have not started the bridge tough because I think it’s not needed for a non-validator. Not 100% sure though.

Any ideas?

y, sure.
Is there only scammers in this forum?

This issue can occur when the gas allowance given is more than limit or if there is any problem with RPC call