How to solve "No blocks processed" problem?

[ashuralyk]

0|eos-inde | 2020-06-23T18:39:46: [00_master] No blocks processed! Indexer will stop in 35 seconds!
0|eos-inde | 2020-06-23T18:39:51: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:39:51: [00_master] No blocks processed! Indexer will stop in 30 seconds!
0|eos-inde | 2020-06-23T18:39:56: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:39:56: [00_master] No blocks processed! Indexer will stop in 25 seconds!
0|eos-inde | 2020-06-23T18:40:01: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:40:01: [00_master] No blocks processed! Indexer will stop in 20 seconds!
0|eos-inde | 2020-06-23T18:40:06: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:40:06: [00_master] No blocks processed! Indexer will stop in 15 seconds!
0|eos-inde | 2020-06-23T18:40:11: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:40:11: [00_master] No blocks processed! Indexer will stop in 10 seconds!
0|eos-inde | 2020-06-23T18:40:16: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:40:16: [00_master] No blocks processed! Indexer will stop in 5 seconds!
0|eos-inde | 2020-06-23T18:40:21: [00_master] W:11 | R:0 | C:0 | A:0 | D:0 | I:0 | 0/0/127640799 | syncs a few seconds ago (0.0% 0.0%)
0|eos-inde | 2020-06-23T18:40:21: [00_master] Reached limit for no blocks processed, stopping now...

It's werid, my main-net nodeos' plugin state_history_plugin is on, and it seems everything is fine with other dependencies.

[adu-web3]

I have met with the same problem

[JoYeonJeong]

Did you solve it?

[adu-web3]

no

[poudelanuj]

I am also facing the same problem. while running ./run.sh eos-indexer this command, the log is same as above mentioned

[mikevmk]

I'm stuck with this issue too (with EOS Jungle Testnet chain). Any suggestions?

2022-01-11T09:17:16: [03_deserializer] deserializeNative >> signed_block >> Invalid argument
2022-01-11T09:17:16: {
2022-01-11T09:17:16: head: {
2022-01-11T09:17:16: block_num: 119327771,
2022-01-11T09:17:16: block_id: '071CCC1B954DF8EEECE204150045CE97F9D9171B83855BB004D27E708165829B'
2022-01-11T09:17:16: },
2022-01-11T09:17:16: last_irreversible: {
2022-01-11T09:17:16: block_num: 119327445,
2022-01-11T09:17:16: block_id: '071CCAD5D18744666A0025F3979382551D1CAF38CA024D25C796AF0F02E91400'
2022-01-11T09:17:16: },
2022-01-11T09:17:16: this_block: {
2022-01-11T09:17:16: block_num: 119327170,
2022-01-11T09:17:16: block_id: '071CC9C2F9E16381547FEF93D3B8747222F93B705FE32AA54EC516D6EB67B9D7'
2022-01-11T09:17:16: },
2022-01-11T09:17:16: prev_block: {
2022-01-11T09:17:16: block_num: 119327169,
2022-01-11T09:17:16: block_id: '071CC9C16591244ABD9F9B0276CF41653635AC37D9434C864FF8FB762292FBD1'
2022-01-11T09:17:16: },
2022-01-11T09:17:16: block: [
2022-01-11T09:17:16: 'signed_block_v1',
2022-01-11T09:17:16: {
2022-01-11T09:17:16: timestamp: '2022-01-11T06:08:24.000',
2022-01-11T09:17:16: producer: 'hippopotamus',
2022-01-11T09:17:16: confirmed: 228,
2022-01-11T09:17:16: previous: '071CC9C16591244ABD9F9B0276CF41653635AC37D9434C864FF8FB762292FBD1',
2022-01-11T09:17:16: transaction_mroot: '0000000000000000000000000000000000000000000000000000000000000000',
2022-01-11T09:17:16: action_mroot: '0000000000000000000000000000000000000000000000000000000000000000',
2022-01-11T09:17:16: schedule_version: 108,
2022-01-11T09:17:16: new_producers: null,
2022-01-11T09:17:16: header_extensions: [],
2022-01-11T09:17:16: producer_signature: 'SIG_K1_KW4LGQALqB2yfnL6CgwVg98ewf4JwodUJSHNDHi8XzfYcb8bkGm7ZwjuMRK2cHiKVhiZedgxbTGGup8nVXD2VFCDTFeDrB',
2022-01-11T09:17:16: prune_state: 2,
2022-01-11T09:17:16: transactions: [],
2022-01-11T09:17:16: block_extensions: []
2022-01-11T09:17:16: }
2022-01-11T09:17:16: ],
2022-01-11T09:17:16: traces: '00',
2022-01-11T09:17:16: deltas: '0101157265736F757263655F6C696D6974735F73746174650101530000C2C91C07A257B301000000001D0000000000000000C2C91C0708E4C900000000000E000000000000005E4ABF5BE5590300080E736958280D000A6A516F030000000000803E0000000000C2EB0B00000000'
2022-01-11T09:17:16: }
2022-01-11T09:17:16: [00_master] The worker #3 has disconnected
2022-01-11T09:17:19: [00_master] W:13 | R:39.2 | C:0 | A:0 | D:0 | I:0 | 0/0/119327169 | syncs a few seconds ago (0.0% 0.0%)
2022-01-11T09:17:19: [00_master] No blocks processed! Indexer will stop in 290 seconds!

[Lizard-King101]

bump?

[iliyahristov]

After some play around I fixed that error ...
You need to set the correct IP address and port in connections.json under your connection name :

...
  "chains": {
    "private": {
      "name": "Private",
      "ship": "ws://127.0.0.1:8088",     <-------- THIS IS THE NEEDED PARAMETER
      "http": "http://127.0.0.1:8888",
      "chain_id": "*************************************************************",
      "WS_ROUTER_HOST": "127.0.0.1",
      "WS_ROUTER_PORT": 7001,
      "control_port": 7002
   },
... 

The address must be as your node address and the port must be like the port setted in nodeos config.ini with parameter
state-history-endpoint = 0.0.0.0:8088

I that example the nodeos and the hyperion are on same machine

Hope that helps someone .

Regards,
I