Thomas Jay Rush

You must have a valid `rpcProvider` for the Ethereum mainnet chain for `chifra init` to work properly. The error message is admittedly poor. When you try to run `chifra status...

So, it looks like you're starting your node right, but it's not visible to `chifra`. To eliminate `chifra` from the equation, try querying the node direct from the same machine...

I get this: ``` { "jsonrpc": "2.0", "id": 1, "result": { "difficulty": "0x3ffffa000", "extraData": "0x476574682f76312e302e302f6c696e75782f676f312e342e32", "gasLimit": "0x1388", "gasUsed": "0x0", "hash": "0xc63f666315fa1eae17e354fab532aeeecf549be93e358737d0648f50d57083a0", "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "miner": "0x0193d941b50d91be6567c7ee1c0fe7af498b4137", "mixHash": "0xbe4ba21fe1ecb061e44f178428c772d2a0f59a7aafb5ed4e198eba4df3656e52", "nonce": "0x5f6a5cc5c36e6627", "number":...

But....and this is a BIG but.... I'm just now noticing that your node is only synced to block `16999999`. This is a problem because the unchained index is now being...

When I do: ``` curl http://localhost:23456 -X POST -H "Content-Type: application/json" --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' ``` I get: ``` { "jsonrpc":"2.0", "id":1, "result":"0x127b71c" } ``` which is block `19379996`. The `chifra status`...

> Okay, it seems after eth merge, i also need to run consensus layer client as well. I thought this might be the problem, but I wasn't sure if block...

Okay. So you're making progress syncing...I now see block 17,819,982. That's good. Now we've encountered a real bug in our code...the "publisher" of the index (which is what `chifra init`...

No. Try adding --sleep 0.5.

Are you out of disc space or something? What does `df -h` say?

> /opt$ df -h Filesystem Size Used Avail Use% Mounted on tmpfs 13G 5,9M 13G 1% /run /dev/nvme0n1p2 92G 20G 67G 23% / tmpfs 63G 159M 63G 1% /dev/shm tmpfs...