Erro recorrente "sem razão encontrado" por Endosser

Question

Erro recorrente "sem razão encontrado" por Endosser

7

164 2019-03-14

Euestoutentando assar sozinhono Ubuntu 18.04.2 ltstantononotebook quantono workstation do Windows VMware.

Tudoestá atualizado - Nó Tezos,Firmware do Ledger Nano,Tezos Baking Appinstaladopor LedgerLive.

Eutenhoesseerro "No Ledger" recorrentepor Tezos-Endosser-003-PSDDFKI3,tantono Ubuntu & Amp; 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) '###'

Comoposso consertarisso,porfavor?

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?

- Vocêestá vendoesseerrono Ubuntue no Windows?também o Tezos-Cliente reconhece seu livro?
  
  are you seeing this error both in Ubuntu and in Windows ? also does the tezos-client recognize your ledger ?
  - 0
  - 2019-03-15
  - Ezy
- sime sim.(Eu sintomuitopela respostaimediata.)
  
  yes and yes. ( I am sorry for not prompt answer. )
  - 0
  - 2019-03-16
  - tzUserABC
- Nósfizemos um chequepara compatibilidade com razão com o Ubuntu 18.04 com Tezos Baking v2.0.0e as coisasparecemestarfuncionandobem.Confirmando que é apenas oendossanteterproblemase não opadeiro?Outras comunicações com o ledgerfuncionambem,como `Lista de Tezos-Cliente Conectado Ledgers`Se apenas oendossanteestivertendoproblemas,você verificou o verificado que usou o alias certo?
  
  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?
  - 0
  - 2019-03-18
  - mikereinhart
- De acordo com Tzscan.io - sim,é apenasendossadorterproblemas,Baker/Baking ébom.`Lista de Tezos-Cliente Connected Ledgers` reconhecemeu livro.O alias que usei é o correto.Quando oerro ocorre a suamensagem "Nenhum razãoencontradopara ABC-Def-Ghi-JKL/ED25519" lista o razãopara o "razão" do alias com qual saídapara oendossobem-sucedido éimpressa - >> Mar ## - Client.endorsement:Endossoinjetadoparabloco '##' (nível 3 #,contador de contratos) '###' @mikereinhart
  
  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
  - 0
  - 2019-03-20
  - tzUserABC
- @tzuserabc Obrigadopelainformação adicional!Seeuestiver lendo seu comentário recente corretamente,seuendossador sóestáfalhando * às vezes *,nem otempotodo.Issoestá certo?O Ledger sópode assinar uma coisa de cada vez.Eu vejoesseerro quando o livrojáestá assinando outra coisa,como umbloco.Issopode sermuito comum se onóestá se recuperandoe o livro assina uma cadeia deblocosenfileirados,impedindo que o Endosserencontrasse o dispositivo de razão ocupado
  
  @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
  - 0
  - 2019-03-20
  - mikereinhart
- @mikereinhart Obrigadopor cavar!Simendossadorfalha _setimes_,nem otempotodo.Deixe-memedir/testar as coisasnovamentena cama Mainnetnonotebook do Ubuntu.Eu vou relatar a você omais cedopossível.Não,onópareceestar sendo atualizado sem alcançar,mas quem sabe.Ty.Noentanto,de acordo com Tzscan.Io semblocosperdidos,apenasendossos.//mantendo contato
  
  @mikereinhart thank you for digging in! Yes endorser fails _sometimes_ , not all the time. Let me measure / test things again in mainnet bed on Ubuntu notebook. I will report to you ASAP. No, - the node looks like is being updated without catching up, but who knows. TY. Yet according tzscan.io no blocks missed, only endorsements. // staying in touch
  - 0
  - 2019-03-20
  - tzUserABC
- Sounds Great @tzuserabc - Eutambém recomendo a criação de logs de depuração - https://github.com/obsidiansystems/ledger-app-dezos#display-debug-logs.Issoimprimirá osbytes sendoenviadosparae apartir do livro durante uma operação,e pode sermuito útil ao depurarproblemas
  
  Sounds great @tzUserABC - I also recommend setting up debug logs - https://github.com/obsidiansystems/ledger-app-tezos#display-debug-logs. This will print the bytes being sent to and from the ledger during an operation, and can be very helpful when debugging issues
  - 0
  - 2019-03-20
  - mikereinhart
- Você acaboutendo alguma sorte aqui?
  
  Did you end up having any luck here?
  - 0
  - 2019-05-30
  - mikereinhart
- @tzuserabc Vocêpoderia,porfavor,postar uma respostapara suapergunta se você acabou resolvendo de umaforma ou de outra?obrigado!
  
  @tzUserABC could you please post an answer to your question if you ended up solving it one way or another ? thanks!
  - 0
  - 2019-12-24
  - Ezy

1 responda

votos

Phlogi · Answer 1 · 2020-01-23

1

2020-01-23

Há outros comandospesquisando o livronomomento da assadeira/endosso?Porexemplo,se vocêexecutar

 tezos-client list connected ledgers

Issobloqueará a comunicaçãoe poderáfazer com que a assadeira/endossofalhe.

Se você quiser Double verifique a comunicação entre o clientee o razão de Tezos semesperarpor umendosso ou cozimento,basta definir amarca d'água (HWM)para a altura dobloco atual:

 tezos-client set ledger high watermark for "ledger://your-address" to <level>

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>

fonte
Phlogi