Errore ricorrente "Nessun libro mastro trovato" dall'endorser

Question

Errore ricorrente "Nessun libro mastro trovato" dall'endorser

7

164 2019-03-14

Stoprovando afare da solo su Ubuntu 18.04.2 LTS sia sunotebook che su Windows VMware Workstation.

Tutto è aggiornato:nodo Tezos,firmware Ledger Nano S,app Tezos Bakinginstallata da LedgerLive.

Ho questoerrore ricorrente "Nessun registrotrovato" ditezos-endorser-003-PsddFKi3entrambi su 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) '###'

Comeposso risolvere questoproblema,perfavore?

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?

- stai vedendo questoerrore siain Ubuntu chein Windows?ancheiltezos-client riconosceiltuo libromastro?
  
  are you seeing this error both in Ubuntu and in Windows ? also does the tezos-client recognize your ledger ?
  - 0
  - 2019-03-15
  - Ezy
- sie si.(Mi dispiaceper la rispostanontempestiva.)
  
  yes and yes. ( I am sorry for not prompt answer. )
  - 0
  - 2019-03-16
  - tzUserABC
- Abbiamo verificato la compatibilità del registro con Ubuntu 18.04 con Tezos Baking v2.0.0e le cose sembranofunzionarebene.Confermare che è solo l'endorser ad avereproblemie nonilfornaio?Altre comunicazioni conil libromastrofunzionanobene,come "libri contabili collegati alla lista clienttezos"?Se solo l'endorser haproblemi,hai ricontrollato di aver utilizzato l'alias corretto?
  
  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
- Secondotzscan.io,sì,sono sologliendorser che hannoproblemi,ilpanettiere/la cottura vabene.`tezos-client list connected ledgers` riconosceilmio libromastro.L'alias che ho usato è quello corretto.Quando si verifica l'errore,il suomessaggio "Nessun libromastrotrovatoper abc-def-ghi-jkl/ed25519"elencail libromastroper l'alias "libromastro" conil quale viene stampato l'outputper l'approvazione di successo - >> Mar ## - client.endorsement:Approvazioneiniettataperilblocco "##" (livello 3 #,registro dei contratti) "###" @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
- @tzUserABCgrazieper leinformazioni aggiuntive!Se sto leggendo correttamenteiltuo commento recente,iltuo sostenitorefallisce solo * a volte *,non sempre.Ègiusto?Il libromastropuòfirmare solo una cosa alla volta.Vedo questoerrore quandoil libromastro stagiàfirmando qualcos'altro,come unblocco.Questopuòesseremolto comune seilnodo sta recuperandoterrenoe il libromastrofirma una stringa diblocchiin coda,impedendo all'endorser ditrovareil dispositivo di libromastro occupato
  
  @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
- @mikereinhartgrazieper aver scavato!Sì,l'endorserfallisce _sometimes_,non sempre.Fammimisurare/testare dinuovo le cosenel lettomainnet sulnotebook Ubuntu.Ti riferirò alpiùpresto.No,ilnodo sembraessere aggiornato senza recuperareil ritardo,ma chi lo sa.TY.Eppure secondotzscan.ionessunbloccomancato,solo conferme.//Rimanerein contatto
  
  @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
- Sembrafantastico @tzUserABC - Consiglio anche diimpostarei log di debug - https://github.com/obsidiansystems/ledger-app-tezos#display-debug-logs.Questo stamperài byteinviati dae versoil libromastro durante un'operazionee puòesseremolto utile duranteil debug deiproblemi
  
  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
- Hai avutofortuna qui?
  
  Did you end up having any luck here?
  - 0
  - 2019-05-30
  - mikereinhart
- @tzUserABCpotrestiperfavorepubblicare una risposta allatua domanda sefinissiper risolverlain unmodo onell'altro?Grazie!
  
  @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 risposta

voti

Phlogi · Answer 1 · 2020-01-23

1

2020-01-23

Ci sono altri comandi cheeseguonoilpolling del libromastro almomento dellapreparazione/approvazione?Adesempio,seesegui

 tezos-client list connected ledgers

questobloccherà la comunicazionee potrebbe causareilfallimento della cottura/approvazione.

Se desideri ricontrollare la comunicazione trail clienttezose il libromastro senza aspettare un'approvazione o una cottura,imposta semplicemente lafiligrana (HWM) sull'altezza delblocco corrente:

 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