We are using stable version of geth v1.3. The nodes are on docker containers. Have configured two nodes, signer and sealer accounts using clique POA and used puppet for creating genesis file. Have unlocked the account and started the miner process. Getting following in logs and blocks are not getting mined

When the miner is started getting following in the Logs WARN [01-22|19:07:12] Block sealing failed err="authentication needed: password or unlock"

  • Can you give a docker-compose configuration for this setup? – justin.m.chase Feb 5 '18 at 12:58

It looks like you've authorised the right accounts for your geth nodes (otherwise you'd be getting an error message about the account being unauthorised, rather than unlocked) - so that's a good start.

Do you have multiple accounts on your geth nodes? if so it may be the case that the authorised sealer accounts are still locked. Type the following into your geth console:


and if more than one address comes up then that may be the issue - simply unlock the correct account. Alternatively, it may be that your accounts were correctly unlocked but have re-locked over time - in order to keep them open use the following:

personal.unlockAccount(eth.accounts[0], "<password>", 0)

Assuming your first account listed under eth.accounts is your sealer account. The '0' in the phrase above refers to how long to keep the account unlocked for in seconds - a non-zero figure here can be used to keep it open for a set period instead.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.