Testnet node crashes with chain ID mismatch error when attempting to sync from genesis

[shpookas]

Hi abstract team,
We are trying to setup a abstract-testnet node from genesis, however we are dealing with this issue. The node crashes with chain ID mismatch error when attempting to sync from genesis:

 ERROR NamedFuture{name="transaction_finality_updater"}: zksync_node_sync::transaction_finality_updater: Fatal error occurred while updating transactions: internal error: No batch
  transactions to process for chain id 32657 while there are some for None chain_id.Error is thrown so node can restart and reload SL data. If node doesn't make any progress after 
  restart, then it's bug, please contact developers.

Configuration

• Image: matterlabs/external-node:v29.1.2
• Network: Abstract Testnet
• L2 Chain ID: 11124
• L1 Chain ID: 11155111 (Sepolia)
• Main Node URL: https://api.testnet.abs.xyz
• L1 RPC: https://sepolia.drpc.org
• Snapshots: EN_SNAPSHOTS_RECOVERY_ENABLED: "false"

Steps to Reproduce

1. Configure node with genesis sync
2. Clear all PostgreSQL data and persistent volumes
3. Start node from clean state
4. Node crashes with chain ID 32657 error

Environment

• Deployment: Kubernetes
• Storage: Persistent volumes (completely cleared)
• Database: PostgreSQL (fresh instance)

[cytadela8]

@shpookas Hi, just to clarify. Does the node keep crashing immidietly with this error if you restart it without clearing the volumes?