Error recurrente "No se encontró el libro mayor" por parte del endosante

Question

Error recurrente "No se encontró el libro mayor" por parte del endosante

7

164 2019-03-14

Estoyintentando hornear soloen Ubuntu 18.04.2 LTStantoen una computadoraportátil comoen Windows VMware Workstation.

Todoestá actualizado:nodo Tezos,firmware Ledger Nano S,aplicación Tezos Bakinginstaladapor LedgerLive.

Tengoesteerror recurrente "No seencontróel libromayor" detezos-endorser-003-PsddFKi3tantoen Ubuntu comoen 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) '###'

¿Cómopuedo solucionaresto,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?

- ¿Vesesteerrortantoen Ubuntu comoen Windows?¿El cliente detezostambién reconoce su libromayor?
  
  are you seeing this error both in Ubuntu and in Windows ? also does the tezos-client recognize your ledger ?
  - 0
  - 2019-03-15
  - Ezy
- si y si.(Lamentono haber respondido rápidamente).
  
  yes and yes. ( I am sorry for not prompt answer. )
  - 0
  - 2019-03-16
  - tzUserABC
- Hemos comprobado la compatibilidad del libromayor con Ubuntu 18.04 con Tezos Baking v2.0.0 ytodopareceestarfuncionandobien.¿Confirma que soloelendosantetiene problemas ynoelpanadero?Otras comunicaciones conel libromayorfuncionanbien,como los "libros contables conectados de la lista de clientes detezos".Si soloelendosantetiene problemas,¿ha verificado dos veces que utilizóel alias correcto?
  
  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
- Segúntzscan.io,sí,soloelendosantetiene problemas,elpanadero/horneadoestábien.`tezos-client list connected ledgers` reconocemi libromayor.El alias que utilicéesel correcto.Cuando seproduceelerror,elmensaje "No seencontróel libromayorpara abc-def-ghi-jkl/ed25519"enumerael libromayorparael alias "libromayor" conel que seimprime la salidaparaelendosoexitoso - >> Mar ## -endoso del cliente:Aprobacióninyectadaparaelbloque '##' (nivel 3 #,libromayor 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 ¡graciaspor lainformación adicional!Si leo correctamente su comentario reciente,supatrocinador solofalla * a veces *,notodoeltiempo.¿Estábien?El libromayor solopuedefirmar una cosa a la vez.Veoesteerror cuandoel libromayor yaestáfirmando algomás,como unbloque.Estopuede sermuy común sielnodo seestáponiendo al día yel libromayorfirma una serie debloquesen cola,evitando queelendosanteencuentreel dispositivo del libromayor 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 ¡graciasporindagar!Sí,elendosantefalla _a veces_,notodoeltiempo.Déjamemedir/probar cosas denuevoen la cama de la redprincipalen unportátil Ubuntu.Teinformaré lo antesposible.No,parece queelnodo seestá actualizando sinponerse al día,pero quién sabe.TY.Sinembargo,segúntzscan.io,no seperdieronbloques,solo respaldos.//mantenerseen contacto
  
  @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
- Suenagenial @tzUserABC - También recomiendo configurar registros de depuración - https://github.com/obsidiansystems/ledger-app-tezos#display-debug-logs.Estoimprimirá losbytes que seenvían hacia y desdeel libromayor durante una operación,ypuede sermuy útil al 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
- ¿Terminasteteniendo suerte aquí?
  
  Did you end up having any luck here?
  - 0
  - 2019-05-30
  - mikereinhart
- @tzUserABC,¿podríaspublicar una respuesta atupregunta siterminaste resolviéndola de unaforma u otra?¡Gracias!
  
  @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 respuesta

votos

Phlogi · Answer 1 · 2020-01-23

1

2020-01-23

¿Hay otros comandos que sondeanel libromayoren elmomento de hornear/aprobar?Porejemplo,siejecuta

 tezos-client list connected ledgers

Estobloqueará la comunicación ypodría hacer quefalleel horneado/respaldo.

Si desea verificar dos veces la comunicación entreel cliente detezos yel libromayor sinesperar un respaldo u horneado,simplemente configure lamarca de agua (HWM) a la altura delbloque actual:

 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>