WARN [ledger] validateSourceAdvanced failed on

[texmason]

Background. I tried for several days to get the Google Cloud Guardian server to synch with no avail. So I decided to run the CLI commands on a google cloud linux server. Finally I am synching with the blockchain, but I'm getting errors. I don't think my guardian node is operating properly.

$

{ "address": "0x1659AF342F21433CeE9ec0fa6E89bb8903182F07", "chain_id": "mainnet", "current_epoch": "9255226", "current_height": "9180890", "current_time": "1613079434", "latest_finalized_block_epoch": "9255224", "latest_finalized_block_hash": "0xb535c99f5c5d584ac2b637e3ced5976bfe1be64aed186f026dd1fd6ffee4b43e",
"latest_finalized_block_height": "9180890", "latest_finalized_block_time": "1613079422", "peer_id": "0x1659AF342F21433CeE9ec0fa6E89bb8903182F07", "syncing": false }

[2021-02-11 21:18:52] WARN [ledger] validateSourceAdvanced failed on 0x2586E72a4D8B80cCE76d7E4069312A78cCc06b9C: Result{code:100002, message:ValidateInputAdvanced: Got 267, expected 268. (acc.seq=267)}

[2021-02-11 21:18:52] WARN [ledger] validateSourceAdvanced failed on 0x372489f42C3f2c36a77E9f3128792D04b0E948CB: Result{code:100002, message:ValidateInputAdvanced: Got 1, expected 2. (acc.seq=1)}

[Hyferion]

I set up a guardian node on a ubuntu server on Azure following the guide here: https://docs.thetatoken.org/docs/running-a-guardian-node-through-command-line and I'm running into the same problem. I don't think the node is running correctly. Is there a solution for this?

[tomerqueves]

same i am reading doc try to solve. if i read here de solution or find one i will retun and gibe it. probable related miss config relative wallet configuration node but it is only and opinion and de solutión would be in other location and the problem were being generated another issue. i will try readin.

[rrln]

Same here, a lot of "WARN [ledger] validateSourceAdvanced failed ... Got X, expected X+1" as in the log above. It's a Warning so I guess it's not critical, but it certanly results in overhead. The difference is always 1 when it fails.
Win 10 and Guardian Node v 2.2.10.

[rrln]

Looked some more in the log to get the big picture. I have no knowledge at all about how the protocol works but I think the "WARN [ledger] validateSourceAdvanced failed" is perfectly fine. I do think this is by design before "consensus" is reached.

The sequence is always something like this: "WARN [ledger] validateSourceAdvanced failed" ... "WARN [ledger] validateSourceAdvanced failed" "INFO [mempool] Insert tx, tx.hash:" "INFO [consensus] Finalizing block block." "INFO [consensus] Notified finalized block"

I don't know for sure, It is only what I'm thinking.

[rrln]

GN v2.2.10.

[ugazdgaz]

these warnings are normal, I get thousands of them too