7

I am trying to bake solo on Ubuntu 18.04.2 LTS both on notebook and in Windows VMware Workstation.

Everything is up to date - Tezos node, Ledger Nano S firmware, Tezos Baking app installed by LedgerLive.

I have this recurring "No Ledger found" error by tezos-endorser-003-PsddFKi3 both on Ubuntu & VMWare Ubuntu :

Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###'

Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###'

Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###'



Mar ## - client.scheduling: Error while baking:

Mar ## - client.scheduling: Error:

Mar ## - client.scheduling:   No Ledger found for abc-def-ghi-jkl/ed25519

Mar ## - client.scheduling:


Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###'

Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###'

How can I fix this, please?

Improve this question
9
  • are you seeing this error both in Ubuntu and in Windows ? also does the tezos-client recognize your ledger ? – Ezy♦ Mar 15 '19 at 12:42
  • yes and yes. ( I am sorry for not prompt answer. ) – tzUserABC Mar 16 '19 at 6:16
  • We've done a check for ledger compatibility with Ubuntu 18.04 with Tezos Baking v2.0.0 and things seem to be working fine. Confirming it is only the endorser having issues and not the baker? Other communications with the ledger work fine, like tezos-client list connected ledgers? If only the endorser is having issues, have you double checked you used the right alias? – mikereinhart Mar 18 '19 at 17:27
  • According to tzscan.io - yes it is only endorser having issues, baker/baking is fine. tezos-client list connected ledgers recognizes my ledger. Alias I used is the correct one. When the error occurs its message " No Ledger found for abc-def-ghi-jkl/ed25519" lists the ledger for the alias "ledger" with which output for successful endorsement is printed -->> Mar ## - client.endorsement: Injected endorsement for block '##' (level 3#, contract ledger) '###' @mikereinhart – tzUserABC Mar 20 '19 at 14:24
  • @tzUserABC thanks for the additional information! If I'm reading your recent comment correctly, your endorser is only failing sometimes, not all the time. Is that right? The ledger can only sign one thing at a time. I see this error when the ledger is already signing something else, like a block. This can be very common if the node is catching up and the ledger signs a string of queued blocks, preventing the endorser from finding the busy ledger device – mikereinhart Mar 20 '19 at 16:12
1

Are there any other commands polling the ledger at the time of baking/endorsement? For example if you run 

tezos-client list connected ledgers

this will block the communication and could cause the baking/endorsement to fail.

If you want to double check the communication between tezos client and ledger without waiting for an endorsement or baking, just set the watermark (HWM) to the current block height: 

tezos-client set ledger high watermark for "ledger://your-address" to <level>
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.