Hey all, I'm seeing a load of WARN when running geth -rinkeby -rpc -rpcapi eth,net,web3 --syncmode "light" on 1.9.13-stable
WARN [04-22|12:07:01.574] Served eth_getBlockByNumber conn=127.0.0.1:55380 reqid=19 t=224.274µs err="no trusted canonical hash trie"
WARN [04-22|12:07:05.776] Served eth_getBlockByNumber conn=127.0.0.1:55222 reqid=23 t=178.691µs err="no trusted canonical hash trie"
WARN [04-22|12:07:06.574] Served eth_getBlockByNumber conn=127.0.0.1:55380 reqid=20 t=103.525µs err="no trusted canonical hash trie"
WARN [04-22|12:07:10.776] Served eth_getBlockByNumber conn=127.0.0.1:55222 reqid=24 t=181.235µs err="no trusted canonical hash trie"
WARN [04-22|12:07:11.575] Served eth_getBlockByNumber conn=127.0.0.1:55380 reqid=21 t=233.229µs err="no trusted canonical hash trie"Transactions are still being published successfully, but can someone help me understand what this WARN means, and how I eliminate it?
But when i tried to check the status of it i am getting '0x0' as response.
from logs i can see node is synching and has active peers
curl -X POST -H 'content-type:application/json' --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}' http://localhost:9545
please help me hear
Hello. I'm trying to sync my new ETC node to the chain.
I'm using the version etclabscore/core-geth:version-1.11.15 with the following parameters:
geth --maxpeers 100 --http --http.addr 0.0.0.0 --http.port 8345 --http.corsdomain * --http.vhosts * --http.api debug,web3,eth,txpool,personal,net --syncmode full --datadir /data --cache 4096 --classicIn the beginning the sync was really fast and we closed 4 years of the network with less then 24h.
But now it takes a ~12h to complete the sync of 2m.
Right now I'm on block number 8886899 with age of 1y2w2d.
What can I do to improve the sync? I tried to increase the cache (from 2K to 4K) and It seems like it didn't help much, and it doesn't sounds me right to wait two weeks to let the node to finish the sync.
Hello
I'm looking for run a local node and get pending transactions
Since 1 day runing, no pending transactions appear
> txpool.status
{
pending: 0,
queued: 0
}And I use this command line (last version of geth)
geth --datadir=~/dev/chain --syncmode fast --cache 6144 --rpc --rpcaddr '0.0.0.0' --rpcapi=eth,net,rpc,web3,txpool,personal,debug --txpool.globalslots=250000 --txpool.globalqueue=500000 console
Is the command line wrong ? Or need more time to synchronize blockchain ?
{"jsonrpc":"2.0","method":"eth_submitWork","params":["0xf03655db16c8ea1b","0xde2425167ae9baa2f49dc60347c48f3b6a230c392b17cdc5ca12d4f45451488f","0xe518bea8cdc1733487e9c647d5e79c239f59385af033e1cc2c0add556571c23e"],"id":"1605541498"}
Hello,
I'm getting the Error: Contract not deployed after cloning private geth network from one server to another.
Steps to reproduce:
Private geth network is running on server1.
Deploy contract using truffle and make a few transactions.
Stop geth n/w of server1 and copy its entire directory (accounts.txt, boot.key, genesis.json, node's password.txt along with its directories keystore and geth) and paste to server2
Change in the geth configuration --rpcaddr 'xx.xx.xx.xx' with private IP of the server2.
Bring up this geth network clone of server1 on server2 (it is able to successfully seal new block, mine potential block, and commit new mining work)
Interact with contract on server2.
Error: contract not deployed
Restart the stopped geth n/w server1 (it is able to successfully seal new block, mine potential block, and commit new mining work)
Interact with contract on server1.
Error: contract not deployed
Expectation:
Restarting the geth n/w on server1 should not cause any data loss.
Should be able to interact (get the transactions performed on server1 as the data should be present in chaindata) with the contract on server2.
Note: I was able to migrate a test geth n/w successfully for a n/w running from past 2 days. After this successful operation, I was migrating this geth n/w which was running from past 7 months which is failing now with error contract not deployed. Will it sync/heal itself if its up for a long time? What are the correct ways to restart and migrate the n/w with huge chaindata. Any documentation would be much appreciated.
Thanks
{
currentBlock: 11347639,
highestBlock: 11347714,
knownStates: 491673340,
pulledStates: 491609932,
startingBlock: 11343389
}
0x5e9189a13ea487ee782de2004b20ef7c94771d338efe0c174fef4ac93770a9c4
I just set up an eth node on my new rpi4
and im running bitvise on my HP for ssh
So everything was up and running last night, but after i booted my personal pc this morning im having a hard time getting back into the terminal and checking the status of the mine, does anyone have any tips on checking progress in a new terminal?
i can’t even use the jobs command to make sure the node is running (but i know its running bc htop)
