创建对等节点时的Hyperledger Fabric错误

如何解决创建对等节点时的Hyperledger Fabric错误

我已经将core.yaml设置为与对等方在同一节点上使用CouchDB实例,我不是在使用docker,而是直接在节点上使用peer命令。

第一次运行对等节点时,出现以下错误:

[36m2020-09-03 17:35:35.619 UTC [kvledger] recoverUnderConstructionLedger -> DEBU 083[0m Recovering under construction ledger
[36m2020-09-03 17:35:35.619 UTC [kvledger] recoverUnderConstructionLedger -> DEBU 084[0m No under construction ledger found. Quitting recovery

panic: Error in instantiating ledger provider: sync /vagrant/runtime/peer0/ledger/ledgersData/snapshots: invalid argument
error while synching dir:/vagrant/runtime/peer0/ledger/ledgersData/snapshots

github.com/hyperledger/fabric/core/ledger/kvledger.syncDir
    /__w/1/go/src/github.com/hyperledger/fabric/core/ledger/kvledger/snapshot.go:186
github.com/hyperledger/fabric/core/ledger/kvledger.(*Provider).initSnapshotDir
    /__w/1/go/src/github.com/hyperledger/fabric/core/ledger/kvledger/kv_ledger_provider.go:266
github.com/hyperledger/fabric/core/ledger/kvledger.NewProvider
    /__w/1/go/src/github.com/hyperledger/fabric/core/ledger/kvledger/kv_ledger_provider.go:132
github.com/hyperledger/fabric/core/ledger/ledgermgmt.NewLedgerMgr
    /__w/1/go/src/github.com/hyperledger/fabric/core/ledger/ledgermgmt/ledger_mgmt.go:65
github.com/hyperledger/fabric/internal/peer/node.serve
    /__w/1/go/src/github.com/hyperledger/fabric/internal/peer/node/start.go:426
github.com/hyperledger/fabric/internal/peer/node.glob..func6
    /__w/1/go/src/github.com/hyperledger/fabric/internal/peer/node/start.go:127
github.com/spf13/cobra.(*Command).execute
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:762
github.com/spf13/cobra.(*Command).ExecuteC
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:852
github.com/spf13/cobra.(*Command).Execute
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:800
main.main
    /__w/1/go/src/github.com/hyperledger/fabric/cmd/peer/main.go:54
runtime.main
    /usr/local/go/src/runtime/proc.go:203
runtime.goexit
    /usr/local/go/src/runtime/asm_amd64.s:1373

goroutine 1 [running]:
github.com/hyperledger/fabric/core/ledger/ledgermgmt.NewLedgerMgr(0xc000367968,0x1b0d960)
    /__w/1/go/src/github.com/hyperledger/fabric/core/ledger/ledgermgmt/ledger_mgmt.go:79 +0x782
github.com/hyperledger/fabric/internal/peer/node.serve(0x24a9520,0x0,0x0)
    /__w/1/go/src/github.com/hyperledger/fabric/internal/peer/node/start.go:426 +0x1f62
github.com/hyperledger/fabric/internal/peer/node.glob..func6(0x2377120,0x24a9520,0x0)
    /__w/1/go/src/github.com/hyperledger/fabric/internal/peer/node/start.go:127 +0x9c
github.com/spf13/cobra.(*Command).execute(0x2377120,0x2377120,0x24a9520)
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:762 +0x453
github.com/spf13/cobra.(*Command).ExecuteC(0x2377840,0xc0005a5f50,0x1,0x1)
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:852 +0x2ea
github.com/spf13/cobra.(*Command).Execute(...)
    /__w/1/go/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:800
main.main()
    /__w/1/go/src/github.com/hyperledger/fabric/cmd/peer/main.go:54 +0x45b

我四处搜寻,但似乎并没有太多提及此特定错误。

我在做什么错了?

解决方法

找到了解决方案。

与主机中目录同步有关的常见游荡问题(例如 https://medium.com/@dtinth/isolating-node-modules-in-vagrant-9e646067b36

我只需要将/ vagrant / runtime绑定到$ HOME / runtime上,节点就可以正常启动了。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-