I have a multi-node private chain and recently had to switch the networkId and the ChainID in the Genesis block to match in order to obey Metamask's requirements.
Now that I have made those changes and redeployed, it worked fine for me locally, but my Dockerized Geth nodes are not able to "Successfully sealed a new block" but is able to "Commit new mining work". Below is the following Dockerfile:
FROM ethereum/client-go:v1.7.2
RUN mkdir -p /root/myChain/
WORKDIR /root/myChain
COPY Genesis.json /root/myChain/
RUN geth \
--identity "myChainNode" \
init \
--datadir "/root/.ethereum/myChain/" \
"/root/myChain/Genesis.json" \
--ipcdisable \
--mine --autodag --networkid 777 --nat "any" --gasprice "3000000"
EXPOSE 30303
EXPOSE 8545
ENTRYPOINT geth \
--identity "myChainNode" \
--datadir "/root/.ethereum/myChain/" \
--ipcdisable \
--networkid 777 \
--rpcapi eth,web3,net,personal \
--rpc --rpcaddr "0.0.0.0" --rpcport "8545" \
--rpccorsdomain "*" \
--nat "any" \
--port "30303" \
--etherbase "<myPublicAddress>" \
--ws --wsport "8546" --wsaddr="0.0.0.0" --wsorigins "*" \
--mine \
console
When I miner.start()
or miner.start(8)
the response is null
I am connected to peers in my private chain and my hashrate is still 0.
AWS has the appropriate 30303 and 8545 ports open for my EC2 running it.
My local node is mining beautifully and it's run script looks like the following:
sudo geth \
--identity "myChainNode" \
--datadir "~/Library/Ethereum/myChain" \
--ipcdisable \
--etherbase "<myPublicAddress>" \
--networkid 777 \
--rpcapi eth,web3,net,personal \
--rpc --rpccorsdomain "*" \
-rpcport "8545" \
--verbosity 3 \
--ws --wsport "8547" --wsorigins "*" \
--mine \
console
Any thoughts?