Testnet Explorer Sync

Monitors the testnet block explorer's indexer sync status by comparing its latest indexed block height against the Ormos testnet chain head. Same check logic as mainnet — detects stuck sync jobs and worker failures. Critical for the dev team to notice when testnet explorer data goes stale during active development and QA testing. The most common cause of a DOWN result is the explorer auto-disabling itself (shouldSync=false) after 10+ consecutive RPC failures — the sync-status API returns an empty explorers array in this state. Recovery: UPDATE explorers SET "shouldSync"=true, "syncFailedAttempts"=0, "syncDisabledAt"=NULL WHERE id=1.

Operational

Environment

dev

Response Time

Average

555ms

Min

45ms

Max

2169ms

p99

1972ms

Uptime History

120 checks agoNow

Direct Links

Troubleshooting

Possible causes:

Explorer auto-disabled after 10+ consecutive RPC failures (shouldSync=false) — sync-status API returns empty explorers array— Fix: Re-enable in DB: UPDATE explorers SET "shouldSync"=true, "syncFailedAttempts"=0, "syncDisabledAt"=NULL WHERE id=1; then check worker logs for 'auto-disabled due to RPC failures' to confirm root cause
BullMQ blockSync job stuck in active state— Fix: SSH to server, clear queue: docker exec <backend> node -e "...Queue('blockSync')...obliterate()..."; restart workers
PM2 sync process crashed— Fix: Check PM2 logs: docker exec <pm2> pm2 logs --lines 50; restart: docker compose restart pm2
EVM indexer disabled on chain node— Fix: Set enable-indexer = true in app.toml, restart node, run: intgd index-eth-tx backward && intgd index-eth-tx forward
Workers disconnected from Redis/RPC— Fix: docker compose restart high_priority_worker medium_priority_worker low_priority_worker
Missing DB columns causing silent INSERT failures— Fix: Run migration: docker exec <backend> npx sequelize-cli db:migrate

Dependencies

Depends on Required by