为什么我的认可人不认可316956区块？

Question

为什么我的认可人不认可316956区块？

- 3
- 156 2019-02-17
我已经在一台服务器上使用dockerimage设置了节点,贝克和背书者,并在另一台服务器上设置了远程签名者.

现在,我错过了认可它的机会,并且在我的认可者日志中没有看到任何此类日志,除了我的身份验证密钥密码(如下所述)的错误与我的烘焙帐户无关用作授权密钥,只能与远程签名者连接.

[[36mendorser-003-PsddFKi3_1| [[0m当前头:BLb3yr9bGYu9 (时间戳:2019-02-17T07:59:10Z,验证:2019-02-17T07:59:59Z) [[36mendorser-003-PsddFKi3_1| [[0m自举. [[36mendorser-003-PsddFKi3_1| [[0m输入加密密钥的密码 " auth":致命错误:[[36mendorser-003-PsddFKi3_1| [[0m
Unix.Unix_error(Unix.ENOTTY,"tcgetattr","") [[36mendorser-003-PsddFKi3_1| [[0m等待节点与网络同步... [[36mendorser-003-PsddFKi3_1| [[0m 免责声明:[[36mendorser-003-PsddFKi3_1| [[0m Tezos网络是一种新的区块链技术. [[36mendorser-003-PsddFKi3_1| [[0m 用户对相关风险承担全部责任 [[36mendorser-003-PsddFKi3_1| [[0m,使用Tezos网络. 用户应该执行自己的[[36mendorser-003-PsddFKi3_1| [[0m自己研究以确定Tezos是否合适 [[36mendorser-003-PsddFKi3_1| [[0m平台满足他们的需求和应该做出判断,[[36mendorser-003-PsddFKi3_1| [[0m护理在他们的网络互动中. [[36mendorser-003-PsddFKi3_1| [[0m [[36mendorser-003-PsddFKi3_1| [[0m当前头:BLAJbqV8Bxn1 (时间戳:2019-02-17T08:00:10Z,验证:2019-02-17T08:01:02Z) [[36mendorser-003-PsddFKi3_1| [[0m自举. [[36mendorser-003-PsddFKi3_1| [[0m输入加密密钥的密码 " auth":致命错误:[[36mendorser-003-PsddFKi3_1| [[0m
Unix.Unix_error(Unix.ENOTTY,"tcgetattr","") [[36mendorser-003-PsddFKi3_1| [[0m等待节点与网络同步... [[36mendorser-003-PsddFKi3_1| [[0m 免责声明:[[36mendorser-003-PsddFKi3_1| [[0m Tezos网络是一种新的区块链技术. [[36mendorser-003-PsddFKi3_1| [[0m 用户对相关风险承担全部责任 [[36mendorser-003-PsddFKi3_1| [[0m,使用Tezos网络. 用户应该执行自己的[[36mendorser-003-PsddFKi3_1| [[0m自己研究以确定Tezos是否合适 [[36mendorser-003-PsddFKi3_1| [[0m平台满足他们的需求和应该做出判断,[[36mendorser-003-PsddFKi3_1| [[0m护理在他们的网络互动中. [[36mendorser-003-PsddFKi3_1| [[0m [[36mendorser-003-PsddFKi3_1| [[0m当前磁头:BLMtVK6RWXSk (时间戳:2019-02-17T08:01:10Z,验证:2019-02-17T08:02:04Z) [[36mendorser-003-PsddFKi3_1| [[0m自举. [[36mendorser-003-PsddFKi3_1| [[0m输入加密密钥的密码 " auth":致命错误:[[36mendorser-003-PsddFKi3_1| [[0m
Unix.Unix_error(Unix.ENOTTY,"tcgetattr","") [[36mendorser-003-PsddFKi3_1| [[0m等待节点与网络同步... [[36mendorser-003-PsddFKi3_1| [[0m 免责声明:[[36mendorser-003-PsddFKi3_1| [[0m Tezos网络是一种新的区块链技术. [[36mendorser-003-PsddFKi3_1| [[0m 用户对相关风险承担全部责任 [[36mendorser-003-PsddFKi3_1| [[0m,使用Tezos网络. 用户应该执行自己的[[36mendorser-003-PsddFKi3_1| [[0m自己研究以确定Tezos是否合适 [[36mendorser-003-PsddFKi3_1| [[0m平台满足他们的需求和应该做出判断,[[36mendorser-003-PsddFKi3_1| [[0m护理在他们的网络互动中.

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

可能出了什么问题,我可以在哪里检查?

注意:这里要注意的一件事是,由于服务器的某些问题,在获得认可权后,我更改了贝克运行的服务器.当我再次注册面包师时,它说不需要注册该面包师,因为它已经被注册.这是否与我支持更改节点标识有关?

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

- "它仅用作与远程签名者连接的授权密钥"-您是不是要使用此远程签名者(需要此身份验证)来签署认可,但要使用其他密钥/签名者?
  
  "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
- 是的,我从远程签名者导入了另一个密钥(用作baker)(baker密钥是在远程签名者上生成的)," auth"密钥是在节点上生成的,并已注册为远程签名者上的授权密钥.如此处所述https://tezos.gitlab.io/alphanet/introduction/various.html#secure-the-connection"请注意,此密钥仅用于对签名者进行身份验证,而不能用作签名者.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 个回答

投票数

- 0
- 2019-02-19
如@Tom所述,日志中的错误实际上是问题所在.Endorser也尝试认可" auth"密钥,因为它存在于public_keys和docker容器中,endorser和baker尝试默认情况下对所有密钥执行其操作.

由于我的" auth"密钥已加密,因此它要求输入密码,并且由于没有密码,它抛出了异常,并且一直保持这种状态,因此,我的背书者从未处于健康状态,无法执行实际的背书操作.

为避免此问题,请使用未加密的密钥进行身份验证.在此处检查以了解如何创建未加密的密钥./p>

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.
- 对面包师的操作使用未加密的私钥是非常危险的.最佳实践是使用分类帐来保护密钥.
  
  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

错误日志清楚地表明" auth"键的ENOTTY错误是您的问题.

您不能直接使用加密密钥向远程签名者验证docker守护进程,因为您无法输入密码.(如FLF OCP所述," ENOTTY错误是由于试图在服务器上询问密钥密码而引起的.终端,但没有这样的终端".

原文
Tom

也许您应该编辑您的答复以解释ENOTTY错误是由于试图在终端上询问密钥密码而引起的,但是没有这样的终端.为避免这种情况,密钥不得加密(空密码).

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
未加密的密钥可以工作,但是主网不允许您创建它们...我认为,加密密钥的空密码将不起作用.

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
如何生成未加密的密钥?

how to generate unencrypted key?
- 0
- 2019-02-19
- Sachin Tomar
检查此问题的解决方案.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