0x5377ac0356223536f5e60646e3fa4350e98186fcb7a1a6144efe9e2562f221b6
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 24 hours and 0 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
Hi, we have seen that some blocks are missing in the blocks table. Is there any way to force blockscout to refetch these missing blocks? I tried adding rows in the pending_block_operations table but I'm getting a foreign key constraint violation:
ERROR: insert or update on table "pending_block_operations" violates foreign key constraint "pending_block_operations_block_hash_fkey"
DETAIL: Key (block_hash)=(\x52580fd530b5197f32f840a996c6d5f681a017d41ebcb238779a150c5af2c9ab) is not present in table "blocks".
How to find the API for token? https://blockscout.com/poa/xdai/tokens/0x7B6F95D7575Ad408f264520447b8c39e11620f23/
Hi. I received some EIDI on the IDChain network in my Metamask. However, I can not see any transactions on the https://explorer.idchain.one/address/.../explorer for that address? Why is this please?
hi.. i did not receive my transaction to eth network... https://blockscout.com/poa/xdai/tx/0xf995df3bc8cb027b15e6420231f15cbbf794b4b288d3a7d72c9fbfcf8db37d80/internal-transactions
Can someone help me?
[Victor Baranov, POA Network] @ssandeep Blockscout provides catchup fetcher which periodically checks missing blocks in the chain and fetches them eventually. You don’t need to undertake extra steps.
@dannygkass all available API endpoints are listed at /api-docs page. ?module=token especially for token. Also, there are some token related endpoints in ?module=*account* section. If you feel lack of some endpoints, please, create a feature request in the Github repository.
[Victor Baranov, POA Network] Logs are similar to those in the issue poanetwork/blockscout#3345. Please subscribe to it
1 reply
yes, I can see the logs where it is reattempting to get these blocks but it keeps failing. Here are the logs:
```[340]: Retrying.
[340]: 2020-10-14T07:10:49.805 application=indexer fetcher=block_catchup first_block_number=4750082 last_block_number=4750073 [error] ** (MatchError) no match of right hand side value: {:error, {:more, {:hparse
r, :response, 4096, 10, 0, :on_trailers, "", {1, 1}, "", [], :undefined, "chunked", "", "application/json", "", :done}}}
[340]: (indexer 0.1.0) lib/indexer/transform/address_coin_balances_daily.ex:67: anonymous fn/3 in Indexer.Transform.AddressCoinBalancesDaily.reducer/2
[340]: (elixir 1.10.3) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
[340]: (indexer 0.1.0) lib/indexer/transform/address_coin_balances_daily.ex:66: Indexer.Transform.AddressCoinBalancesDaily.reducer/2
[340]: (stdlib 3.12.1) maps.erl:232: :maps.fold_1/3
[340]: (indexer 0.1.0) lib/indexer/block/fetcher.ex:165: Indexer.Block.Fetcher.fetch_and_import_range/2
[340]: (indexer 0.1.0) lib/indexer/block/catchup/fetcher.ex:194: Indexer.Block.Catchup.Fetcher.fetch_and_import_range_from_sequence/3
[340]: (elixir 1.10.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
[340]: (elixir 1.10.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
[340]: Retrying.
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 24 hours and 0 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
the blockchain I am running creates blocks much faster than what is showing up in Average block time in blockscout
i also see that it is in sync and the latest blocks are available almost instantaneously
[Victor Baranov, POA Network] Average block time is an average block timestamp diff from last 100 blocks with 100 blocks offset from the head of the chain https://github.com/poanetwork/blockscout/blob/master/apps/explorer/lib/explorer/counters/average_block_time.ex#L75-L76
3 replies
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 24 hours and 0 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 22 hours and 27 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 10 hours and 46 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
I am able to access these blocks through curl but seeing this in the blockscout logs for the same block numbers:
2020-10-21T08:48:36.309 application=indexer fetcher=block_catchup first_block_number=5429631 last_block_number=5429631 step=blocks [error] failed to fetch: {:more, {:hparser, :response, 4096, 10, 0, :on_trailers, "", {1, 1}, "", [], :undefined, "chunked", "", "application/json", "", :done}}. Retrying.
Good afternoon I'm not sure if you can help in this situation but it seems as if somehow when sending 2 ETC to another individual's wallet the transaction made a copy and sent 2 separate transactions under the same block number. Totaling 4 ETC sent and received p2p but only showing 2 ETC on the network.
And what is the impact of running 2 fetcher processes (as part of the core setup) on 2 separate machines behind a common load balancer ?
[Victor Baranov, POA Network] Hi, it is possible to run indexer separately from the web application. However, there is no benefit to run multiple instances of indexers because they will don’t know each other and will process the same data intersecting. Luckily, every fetcher in the indexer has its own batch size and concurrency. So, you can manage parallelism of each fetcher inside a single indexer instance.
Hi! When transactions are relayed through QuikNode endpoints and they have a gasPrice of 1, they are not being picked up by blockscout's xDAI explorer despite existing on the QuikNode servers, for example, this transaction was appearing on our network (https://etherflow.quiknode.io/aHR0cHM6Ly9jb2xkLXNpbGVudC1yYWluLnhkYWkucXVpa25vZGUucHJvLzNjYWVlMjU5Y2NhN2VkNTViNDJlYTkzYjI4OTM5ZGUyOTFlOGUzZWQv/ethers/eth_getTransactionByHash/0xb472963e438430286bb092fc2389c9847542a1f6119e5bc6288e32d19f5819a6), but was not relayed and now appears to have been dropped.
i got this error when try to run blockscout version 3.3.3, can someone help me fix this? :(
[Victor Baranov, POA Network] Catchup fetcher will retry to fetch this range of blocks later until it will be fetched. If for some reason, blocks range fetching failed for a long time, check the state of archive node server. Probably, there are not enough resources for processing all JSON RPC requests.
--nodekey=boot.key --syncmode "full" --gcmode "archive" --rpc --rpcapi "db,personal,admin,debug,eth,net,web3,txpool" --allow-insecure-unlock --rpccorsdomain '' --rpcaddr 0.0.0.0 --rpcport 8545 --rpcvhosts= --ws --wsaddr "0.0.0.0" --wsport 8546 --wsapi "db,personal,admin,debug,eth,net,web3,txpool" --wsorigins=* --port 30303
this is my node's setup. do i miss something?
I think you are referring to the same error as mentioned in poanetwork/blockscout#3345
This has been fixed in v3.3.3
This has been fixed in v3.3.3
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 24 hours and 0 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.
[Victor Baranov, POA Network] > i see the log, first_block= 11262155 , last_block= 11262146, so the range is only 9 blocks.
Yes, the default batch size for catchup fetcher is 10 blocks. If more blocks are absent then it will be processed in different batches.
and i don’t know why first_block > last_block. is it normal?
that is fine. Blocks will be processed in this range.
Are these params for Geth? Looks good to me. You can check yourself too https://docs.blockscout.com/for-developers/information-and-settings/client-settings-parity-geth-ganache