背书者

Question

背书者

7

164 2019-03-14

重复发生"未找到分类帐"错误

我正在尝试在笔记本电脑和Windows VMware Workstation上的Ubuntu 18.04.2 LTS上进行单独烘焙.

一切都是最新的-LedgerLive安装的Tezos节点,Ledger Nano S固件,Tezos Baking应用程序.

我在ubuntu＆amp;上都出现了tezos-endorser-003-PsddFKi3重复出现的"找不到分类帐"错误. 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) '###'

请问该如何解决?

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?

- 您是否在Ubuntu和Windows中都看到此错误?tezos客户端还能识别您的分类帐吗?
  
  are you seeing this error both in Ubuntu and in Windows ? also does the tezos-client recognize your ledger ?
  - 0
  - 2019-03-15
  - Ezy
- 是的,是的.(对不起,我没有及时回答.)
  
  yes and yes. ( I am sorry for not prompt answer. )
  - 0
  - 2019-03-16
  - tzUserABC
- 我们已经通过Tezos Baking v2.0.0检查了与Ubuntu 18.04的分类帐兼容性,并且看起来一切正常.确认只有背书人有问题,而不是面包师吗?与分类帐的其他通信也可以正常工作,例如"tezos-client list connected ledgers"?如果只有背书人有问题,您是否仔细检查过使用正确的别名?
  
  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
- 根据tzscan.io的说法-是的,只有背书人才有问题,面包师/烘烤师傅还可以."tezos-client list connected分类帐"识别我的分类帐.我使用的别名是正确的别名.发生错误时,其消息"未找到abc-def-ghi-jkl/ed25519的总帐"列出了别名" ledger"的总帐,并打印了成功认可的输出->> Mar ##-client.endorsement:已为区块'##'(等级3#,合同分类帐)'###'@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感谢您提供其他信息！如果我正确地阅读了您最近的评论,则您的认可人有时*并非全部*失败.是对的吗?分类帐一次只能签名一件事.当分类帐已经对其他内容(例如块)进行签名时,我会看到此错误.如果节点正在追赶并且分类账对一串排队的块签名,从而阻止背书人找到繁忙的分类账设备,这可能非常常见.
  
  @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感谢您的参与！是的,背书者_sometimes_并非总是失败.让我再次在Ubuntu笔记本上的Mainnet床上进行测量/测试.我会尽快向您报告.不,-节点似乎正在更新而没有赶上,但谁知道.TY.然而,根据tzscan.io,没有任何遗漏,只有认可.//保持联系
  
  @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
- 听起来不错@tzUserABC-我也建议您设置调试日志-https://github.com/obsidiansystems/ledger-app-tezos#display-debug-logs.这将打印在操作过程中发送到分类帐的字节,这在调试问题时非常有帮助
  
  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
- 你最后在这里有运气吗?
  
  Did you end up having any luck here?
  - 0
  - 2019-05-30
  - mikereinhart
- 如果您最终以一种或另一种方式解决了问题,请@tzUserABC张贴您问题的答案吗?谢谢！
  
  @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 个回答

投票数

Phlogi · Answer 1 · 2020-01-23

1

2020-01-23

在烘焙/背书时,是否还有其他命令轮询分类帐?例如,如果您运行

 tezos-client list connected ledgers

这将阻止通信,并可能导致烘焙/背书失败.

如果您想仔细检查tezos客户端和分类帐之间的通信而无需等待背书或烘烤,只需将水印(HWM)设置为当前块高度:

 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>