Node cannot be synchronized

Hi all.
I have installed the Aeternity node. Node is not synchronizing. When I examine the Console output, I see the message “Dropping gossiped light micro_block”.

This is console output:

16:00:07.525 [info] TX-pool synchronization (outgoing) started towards “pp_2LnQXCm…sCQK4fN”
16:00:07.916 [info] Application aehttp started on node [email protected]
16:00:07.928 [info] Application aemon started on node [email protected]
16:00:07.932 [info] Application aestratum_lib started on node [email protected]
16:00:07.937 [info] Application aestratum started on node [email protected]
Eshell V9.3.3.12 (abort with ^G)
([email protected])1> 16:00:08.427 [info] TX-pool sync requries getting 1 TXs
16:00:08.457 [info] TX-pool sync added 1 TXs
16:00:08.485 [info] TX-pool synchronization finished!
16:00:08.773 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.802 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.806 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.816 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.839 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.844 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.858 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.886 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}
16:00:08.953 [info] Dropping gossiped light micro_block (<<6,15,106,102,…,33,106,164,207>>): {error,prev_key_block_not_found}

This is node status output:

{ "difficulty": 17188712909039, "genesis_key_block_hash": "kh_pbtwgLrNu23k9PA6XCZnUbtsvEFeQGgavY4FS2do3QP8kcp2z", "listening": true, "network_id": "ae_mainnet", "node_revision": "02546a105843c8f9773a93666a819beee2c1de48", "node_version": "5.1.0", "peer_count": 330, "peer_pubkey": "pp_Q3Hi4h1NrGaM..............sQrS6Ys", "pending_transactions_count": 22, "protocols": [ { "effective_at_height": 161150, "version": 4 }, { "effective_at_height": 90800, "version": 3 }, { "effective_at_height": 47800, "version": 2 }, { "effective_at_height": 0, "version": 1 } ], "solutions": 0, "sync_progress": 100.0, "syncing": false, "top_block_height": 173574, "top_key_block_hash": "kh_28Qwbk24sx41ANPtVTqvMr3sbALLup9pdCNsWKNzU3tiDfQ9An" }

What brings you to think that your node is not in sync? The status says sync_progress is at 100% and the height looks close to where the top was at the time you posted the message? (syncing: false means that the node is currently not syncing)

The occasional info-log message Dropping gossiped light micro_block... is nothing to worry about it just means that you got a micro-block out of order (which can happen). If it happens often it might indicate that you are not well connected to the network…