Closed paymog closed 2 years ago
Not sure why Geth is not happy, everything flagged "logger":"reader.geth"
is coming from Geth
directly. Bad block indicates something really bad. The insufficient space might have cause this indeed.
Fix the space issue, rewind head earlier and try again. Not really a firehose-ethereum
issue directly.
weird, restarting firehose seems to have solved the issue, at least temporarily. Will keep an eye on this and see if it comes back.
I've tried geth attach
ing to the new instance, and it seems I'm now at block 6158574:
> root@firehose-mainnet-7457c6d7f7-t6m26:/# geth attach /data/firehose/reader/ipc
INFO [10-31|15:43:18.537] Initializing firehose
INFO [10-31|15:43:18.556] Firehose initialized enabled=false sync_instrumentation_enabled=true mining_enabled=false block_progress_enabled=false compaction_disabled=false archive_blocks_to_keep=0 genesis_provenance="Geth Default" firehose_version=2.0 geth_version=1.10.25-fh2 chain_variant=geth
Welcome to the Geth JavaScript console!
instance: Geth/v1.10.25-fh2-67d4fa90/linux-amd64/go1.18.5
at block: 6158571 (Thu Aug 16 2018 11:46:38 GMT-0400 (EDT))
datadir: /data/firehose/reader/data
modules: admin:1.0 debug:1.0 engine:1.0 eth:1.0 ethash:1.0 miner:1.0 net:1.0 personal:1.0 rpc:1.0 txpool:1.0 web3:1.0
To exit, press ctrl-d or type exit
> eth.syncing
{
currentBlock: 6158574,
healedBytecodeBytes: 0,
healedBytecodes: 0,
healedTrienodeBytes: 0,
healedTrienodes: 0,
healingBytecode: 0,
healingTrienodes: 0,
highestBlock: 15870156,
startingBlock: 6158488,
syncedAccountBytes: 0,
syncedAccounts: 0,
syncedBytecodeBytes: 0,
syncedBytecodes: 0,
syncedStorage: 0,
syncedStorageBytes: 0
}
yeah, looks like the disk space was an issue and the bad block was a symptom of that. I had causality reversed.
I've started running firehose and I just ran into the following log lines which seems to have broken geth - it's now reporting that a Disk Quota has been been exceeded:
Is this a known issue? Could it be that my geth instance isn't syncing properly? Might the bad block be a red herring for the disk quota error?