Por que meu endossador não endossou o bloco 316956?

Question

Por que meu endossador não endossou o bloco 316956?

- 3
- 156 2019-02-17
Eu configureimeunó,Bakere Endosser usando aimagem do Dockerem um servidore configurar um signatário remotoem outro servidor.

Agora,quando setrata daminha chance deendossá-loperdidoe eunão vinenhum desses logsem meus logs de Endosser,excetoe erroparaminha senha de autenticação (mencionado abaixo),quenãotem nada a ver comminha conta de cozer comoera usado como chave autorizadapara se conectar apenas com o signatário remoto.

.
[[36mendorser-003-psddfki3_1| [[0m Cabeça atual:blb3yr9byu9 (Timestamp: 2019-02-1707: 59: 10z,validação: 2019-02-1707: 59: 59Z) [[36mendorser-003-psddfki3_1| [[0mbootstrapped. [[36mendorser-003-psddfki3_1| [0m Digite a senhapara a chave criptografada "Auth":errofatal: [[36mendorser-003-psddfki3_1| [[0m de
Unix.unix_error (Unix.enotty,"tcgetattr","") [[36mendorser-003-psddfki3_1| [0m àespera donópara sincronizar com a rede ... [[36mendorser-003-psddfki3_1| [[0m Isenção de responsabilidade: [[36mendorser-003-psddfki3_1| [0m a rede Tezos é umanovatecnologia deblockchain. [[36mendorser-003-psddfki3_1| [0m Os usuários são apenas responsáveis por quaisquer riscos associados [[36mendorser-003-psddfki3_1| [0m com uso da rede Tezos. Os usuários devemfazer o seu [[36mendorser-003-psddfki3_1| [[0mpróprio pesquisapara determinar se Tezos é o apropriado [[36mendorser-003-psddfki3_1| [[plataforma 0mpara suasnecessidadese deve aplicarjulgamentoe [[36mendorser-003-psddfki3_1| [[0m cuidado em suasinterações de rede. [[36mendorser-003-psddfki3_1| [0m [[36mendorser-003-psddfki3_1| [0m Cabeça atual: Blajbqv8bxn1 (Timestamp: 2019-02-1708: 00: 10z,validação: 2019-02-1708: 01: 02Z) [[36mendorser-003-psddfki3_1| [[0mbootstrapped. [[36mendorser-003-psddfki3_1| [0m Digite a senhapara a chave criptografada "Auth":errofatal: [[36mendorser-003-psddfki3_1| [[0m de
Unix.unix_error (Unix.enotty,"tcgetattr","") [[36mendorser-003-psddfki3_1| [0m àespera donópara sincronizar com a rede ... [[36mendorser-003-psddfki3_1| [[0m Isenção de responsabilidade: [[36mendorser-003-psddfki3_1| [0m a rede Tezos é umanovatecnologia deblockchain. [[36mendorser-003-psddfki3_1| [0m Os usuários são apenas responsáveis por quaisquer riscos associados [[36mendorser-003-psddfki3_1| [0m com uso da rede Tezos. Os usuários devemfazer o seu [[36mendorser-003-psddfki3_1| [[0mpróprio pesquisapara determinar se Tezos é o apropriado [[36mendorser-003-psddfki3_1| [[plataforma 0mpara suasnecessidadese deve aplicarjulgamentoe [[36mendorser-003-psddfki3_1| [[0m cuidado em suasinterações de rede. [[36mendorser-003-psddfki3_1| [0m [[36mendorser-003-psddfki3_1| [[0m Cabeça atual:blmtvk6rwxsk (Timestamp: 2019-02-1708: 01: 10z,validação: 2019-02-1708: 02: 04Z) [[36mendorser-003-psddfki3_1| [[0mbootstrapped. [[36mendorser-003-psddfki3_1| [0m Digite a senhapara a chave criptografada "Auth":errofatal: [[36mendorser-003-psddfki3_1| [[0m de
Unix.unix_error (Unix.enotty,"tcgetattr","") [[36mendorser-003-psddfki3_1| [0m àespera donópara sincronizar com a rede ... [[36mendorser-003-psddfki3_1| [[0m Isenção de responsabilidade: [[36mendorser-003-psddfki3_1| [0m a rede Tezos é umanovatecnologia deblockchain. [[36mendorser-003-psddfki3_1| [0m Os usuários são apenas responsáveis por quaisquer riscos associados [[36mendorser-003-psddfki3_1| [0m com uso da rede Tezos. Os usuários devemfazer o seu [[36mendorser-003-psddfki3_1| [[0mpróprio pesquisapara determinar se Tezos é o apropriado [[36mendorser-003-psddfki3_1| [[plataforma 0mpara suasnecessidadese deve aplicarjulgamentoe [[36mendorser-003-psddfki3_1| [[0m cuidado em suasinterações de rede.

Timestamp doblocofoi 2019-02-17T08: 00: 10z

O quepoderiateridoerradoe ondeeuposso verificarisso?

Nota: Uma coisa anotar aqui é queeumudei o servidorno qualmeupadeiroestava correndo depois que recebi os direitos deendossopor causa de algunsproblemas com o servidor. Quando registrei o Bakernovamente,não hánecessidade de registrar opadeiro comojáfoi registrado. Issotem algo a ver com omeuendossado queeumudeiminhaidentidade denó?

I have setup my node, baker and endorser using docker image on one server and setup a remote signer on another server.

Now when it comes to my chance of endorsing it missed and i did not see any such logs in my endorser logs except and error for my auth key password (mentioned below) which has nothing to do with my baking account as it was used as authorized key to connect with remote-signer only.

[[36mendorser-003-PsddFKi3_1 |[[0m Current head: BLb3yr9bGYu9 (timestamp: 2019-02-17T07:59:10Z, validation: 2019-02-17T07:59:59Z) [[36mendorser-003-PsddFKi3_1 |[[0m Bootstrapped. [[36mendorser-003-PsddFKi3_1 |[[0m Enter password for encrypted key "auth": Fatal error: [[36mendorser-003-PsddFKi3_1 |[[0m
Unix.Unix_error(Unix.ENOTTY, "tcgetattr", "") [[36mendorser-003-PsddFKi3_1 |[[0m Waiting for the node to synchronize with the network... [[36mendorser-003-PsddFKi3_1 |[[0m Disclaimer: [[36mendorser-003-PsddFKi3_1 |[[0m The Tezos network is a new blockchain technology. [[36mendorser-003-PsddFKi3_1 |[[0m Users are solely responsible for any risks associated [[36mendorser-003-PsddFKi3_1 |[[0m with usage of the Tezos network. Users should do their [[36mendorser-003-PsddFKi3_1 |[[0m own research to determine if Tezos is the appropriate [[36mendorser-003-PsddFKi3_1 |[[0m platform for their needs and should apply judgement and [[36mendorser-003-PsddFKi3_1 |[[0m care in their network interactions. [[36mendorser-003-PsddFKi3_1 |[[0m [[36mendorser-003-PsddFKi3_1 |[[0m Current head: BLAJbqV8Bxn1 (timestamp: 2019-02-17T08:00:10Z, validation: 2019-02-17T08:01:02Z) [[36mendorser-003-PsddFKi3_1 |[[0m Bootstrapped. [[36mendorser-003-PsddFKi3_1 |[[0m Enter password for encrypted key "auth": Fatal error: [[36mendorser-003-PsddFKi3_1 |[[0m
Unix.Unix_error(Unix.ENOTTY, "tcgetattr", "") [[36mendorser-003-PsddFKi3_1 |[[0m Waiting for the node to synchronize with the network... [[36mendorser-003-PsddFKi3_1 |[[0m Disclaimer: [[36mendorser-003-PsddFKi3_1 |[[0m The Tezos network is a new blockchain technology. [[36mendorser-003-PsddFKi3_1 |[[0m Users are solely responsible for any risks associated [[36mendorser-003-PsddFKi3_1 |[[0m with usage of the Tezos network. Users should do their [[36mendorser-003-PsddFKi3_1 |[[0m own research to determine if Tezos is the appropriate [[36mendorser-003-PsddFKi3_1 |[[0m platform for their needs and should apply judgement and [[36mendorser-003-PsddFKi3_1 |[[0m care in their network interactions. [[36mendorser-003-PsddFKi3_1 |[[0m [[36mendorser-003-PsddFKi3_1 |[[0m Current head: BLMtVK6RWXSk (timestamp: 2019-02-17T08:01:10Z, validation: 2019-02-17T08:02:04Z) [[36mendorser-003-PsddFKi3_1 |[[0m Bootstrapped. [[36mendorser-003-PsddFKi3_1 |[[0m Enter password for encrypted key "auth": Fatal error: [[36mendorser-003-PsddFKi3_1 |[[0m
Unix.Unix_error(Unix.ENOTTY, "tcgetattr", "") [[36mendorser-003-PsddFKi3_1 |[[0m Waiting for the node to synchronize with the network... [[36mendorser-003-PsddFKi3_1 |[[0m Disclaimer: [[36mendorser-003-PsddFKi3_1 |[[0m The Tezos network is a new blockchain technology. [[36mendorser-003-PsddFKi3_1 |[[0m Users are solely responsible for any risks associated [[36mendorser-003-PsddFKi3_1 |[[0m with usage of the Tezos network. Users should do their [[36mendorser-003-PsddFKi3_1 |[[0m own research to determine if Tezos is the appropriate [[36mendorser-003-PsddFKi3_1 |[[0m platform for their needs and should apply judgement and [[36mendorser-003-PsddFKi3_1 |[[0m care in their network interactions.

Block Timestamp was 2019-02-17T08:00:10Z

What could have gone wrong and where i can check it?

NOTE: One thing to notice here is i changed the server on which my baker was running after i got the endorsement rights because of some issues with server. When i registered the baker again it says no need to register the baker as it was already registered. Is this have something to do with my endorsing that i changed my node identity?

baker endorser remote-signer missed-endorsement

- "Foi usado como chave autorizadapara se conectar apenas com o signatário remoto" - você quer dizer que vocênãoestá usandoeste assinante remoto (queexigiuessa autenticação)para assinarendossos,mas alguma outra chave/signater?
  
  "it was used as authorized key to connect with remote-signer only" -- do you mean that you are not using this remote signer (which required this authentication) to sign endorsements, but some other key/signer?
  - 0
  - 2019-02-17
  - Tom
- Sim,importei a outra chave (usada como Baker) do Signer remoto (atecla Bakerfoigeradano dirigível remoto)e atecla "AUTH"foigeradanonóe registrada como chave autorizadano signatário remoto.Como émencionado aqui https://tezos.gitlab.io/alphanet/introduction/várious.html#secure-the-connection "Observe queesta chave é usada apenaspara autenticar o clientepara o signatárioe não é usado comoConta de Tezos ".
  
  Yes i imported the other key(used as baker) from remote-signer (baker key was generated on remote-signer) and "auth" key was generated on node and registered as authorized key on remote signer. As it is mentioned here https://tezos.gitlab.io/alphanet/introduction/various.html#secure-the-connection "Note that this key is only used to authenticate the client to the signer and it is not used as a Tezos account."
  - 0
  - 2019-02-17
  - Sachin Tomar

2 respostas

votos

- 0
- 2019-02-19
Comomencionadopor @tom,oerronos logs realmentefoi oproblema.Endosserestavatentandoendossarpara a chave "autenticação"também comoestavapresenteem Public_Keyse em contêineres de Docker,Endossere Bakertentamexecutar sua operaçãoparatodas as chavesporpadrão.

Ejá queminha chave "autenticação"foi criptografada,elaestavapedindo senhae devido à ausência de qualquer senha quejogouexceçãoe continuoufazendoisso,devido ao quemeuendossadornuncaesteveem estado saudávelpara realizar operações reais deendosso.

Paraevitaresseproblema,use chavesnão criptografadaspara autenticação. Verifique aqui para como criar chavesnão criptografadas.
.

As mentioned by @Tom, the error in the logs actually was the issue. Endorser was trying to endorse for "auth" key also as it was present in public_keys and in docker containers, endorser and baker try to perform their operation for all the keys by default.

And since my "auth" key was encrypted, it was asking for password and due to absence of any password it threw exception and it kept doing that, due to which my endorser was never in healthy state to perform actual endorsement operations.

To avoid this problem use unencrypted keys for authentication. Check here for how to create unencrypted keys.
- Émuitoperigoso usar chavesprivadasnão criptografadaspara as operações de umpadeiro.Amelhorprática é usar o Ledgerparaproteger as chaves.
  
  It is very dangerous to use unencrypted private keys for a baker’s operations. Best practice is to use ledger to protect keys.
  - 1
  - 2019-02-25
  - Ezy

Tom · Accepted Answer · 2019-02-18

2

2019-02-18

Os logs deerro sugerem claramente que oerroenottypara atecla "Auth" é o seuproblema.

Vocênãopode usar diretamente uma chave criptografadapara autenticar os daemons do Dockerpara um assinante remoto,porque vocênãopode digitar a senha. (comonotas OCP da FLF,"Oerroenottyestáproveniente de umatentativa de solicitar a senhaterminal,masnão hátalterminal ").

fonte
Tom

Talvez você deveeditar sua respostaparaexplicar que oerroenottyestáproveniente de umatentativa depedir a senha chaveem umterminal,masnão hátalterminal.Paraevitarisso,a chavenão deve ser criptografada (senha vazia).

Maybe you should edit your reply to explain that the ENOTTY error is coming from an attempt to ask the key password on a terminal, but there is no such terminal. To avoid that, the key must not be encrypted (empty password).
- 0
- 2019-02-18
- lefessan
Ateclanão criptografadapodefuncionar,mas a Mainnetnãopermite que você os crie ... senha vaziapara a chave criptografadanãofunciona,eu acho.

Unencrypted key could work, but mainnet doesn't let you create them... Empty password for encrypted key won't work, I think.
- 0
- 2019-02-18
- Tom
Comogerar chavenão criptografada?

how to generate unencrypted key?
- 0
- 2019-02-19
- Sachin Tomar
Verifiqueissopara soluçãoparaesteproblema.https://tezos.stackexchange.com/questions/451/Baking-with-remote-signer-compatible-with-require-authentication

Check this for solution to this problem. https://tezos.stackexchange.com/questions/451/baking-with-remote-signer-compatible-with-require-authentication
- 0
- 2019-02-25
- Sachin Tomar