Stéphane Duchesneau
Stéphane Duchesneau
It also fails with the data from cleos PR ref: https://github.com/EOSIO/eos/pull/5225 on two aspects: 1) refuses the "SignedTransaction.packed_context_free_data " if it is an empty string instead of empty array 2)...
The problem is actually that the search router cannot access blockmeta... we need the log in search router saying "connecting to blockmeta to get irrBlk" it has the error...
the cursor has a "block ID" in it, so the search router needs to know if it is from a block that was forked out or not, so it can...
How do you know if the relayer is up to date ? 1) run this on it: `curl localhost:9102 |grep 'relayer'` 9for drift in seconds...) 2) run this on it:...
Ok, this means that the blockmeta are NOT stuck at this blockheight, they are OK. Maybe the abicodec has a cursor that points to a block that was forked out...
It also explains that log line on blockmeta, which was mistaken for an indication of the blockmeta itself lagging: ```Aug 20 10:08:16 jungle-bm11 dfuseeos[68839]: 2020-08-20T10:08:16.162Z (blockmeta) behind lib (blockmeta/server.go:319){"block_num": 30352948}...
Could you check with dfuseeos tools in your trxdb to see if you are missing irreversibility data for that block height ? ``` dfuseeos tools db blk 30352948 --dsn whatever://your-dsn-is/for/trxdb...
I can't reproduce by simply closing the endpoints: local setup: * minio(1) listening on 127.0.1.1 * minio(2) listening on 127.0.2.2 dns `ceph.stepd` A record pointing to both .1.1 and .2.2...
so locally, when I set common blocks folder like this: `s3://ceph.stepd:9000/oneblocks?region=none&insecure=true&access_key_id=minio&secret_access_key=miniostorage` tokenmeta will successfully switch to a new endpoint (added in DNS) in case of failure... I see the same...
This issue has been linked to a bug that caused missing status or missing receipts in blockss. https://github.com/streamingfast/firehose-ethereum/issues/84 https://github.com/streamingfast/firehose-ethereum/issues/85 Fixes are in firehose release v2.3.1, will require reprocessing the firehose...