Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction Stuck at Indexing #166

Closed
vickyvickydev opened this issue Oct 30, 2024 · 2 comments
Closed

Transaction Stuck at Indexing #166

vickyvickydev opened this issue Oct 30, 2024 · 2 comments

Comments

@vickyvickydev
Copy link

vickyvickydev commented Oct 30, 2024

I've successfully created a VIC transfer transaction: https://www.vicscan.xyz/tx/0x930a267f13221e571772e3b4ee944b526b88927f97c9993d0d0e8f0edd01c435

But in the transaction details on frontend, it's stuck in indexing.
CleanShot 2567-10-30 at 15 59 24@2x

I looked through the txs-worker-indexer container logs and found this error

txs-worker-indexer-1  | 2024-10-30 09:00:11,066 [ERROR] [06b82f49/index_safe_events_task] Block with hash=0x90c0932663355225be97542f9532018dfd8c47eb204621b8d82f2ed8bc85e08a does not exist on database
txs-worker-indexer-1  | 2024-10-30 09:00:11,083 [ERROR] [06b82f49/index_safe_events_task] Task safe_transaction_service.history.tasks.index_safe_events_task[06b82f49-f51a-4224-90b5-b3704544c179] raised unexpected: DoesNotExist('EthereumBlock matching query does not exist.')

CleanShot 2567-10-30 at 16 00 34@2x

But when I looked in /txs/admin django administration page, I found the block with the tx:
CleanShot 2567-10-30 at 15 58 41
CleanShot 2567-10-30 at 15 58 19

I'm not sure what I did wrong? By the way this is the version of txs-worker-indexer I'm using in the .env file

REVERSE_PROXY_PORT=80

CFG_VERSION=latest
CGW_VERSION=latest
TXS_VERSION=v5.11.0
UI_VERSION=latest
EVENTS_VERSION=latest

RPC_NODE_URL=https://rpc.viction.xyz
@vickyvickydev
Copy link
Author

Also, I'm not sure if it's related, but the API /cgw/v1/chains/88/safes/{safeAddress}/transactions/history returns 404.

@vickyvickydev
Copy link
Author

I've found that the issue came from RPC and not the safe 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant