成功解决 执行config_solo文件夹中./generate.sh脚本报错./bin/cryptogen ./bin/configtxgen: 没有那个文件或目录
报错信息如下:
[yujialing@localhost config_solo]$ ./generate.sh
curl: (56) Recv failure: Connection reset by peer
./generate.sh:行16: ./bin/cryptogen: 没有那个文件或目录
./generate.sh:行17: ./bin/configtxgen: 没有那个文件或目录
./generate.sh:行18: ./bin/configtxgen: 没有那个文件或目录
find: ‘crypto-config’: 没有那个文件或目录
原因是缺少Fabric的二进制脚本文件
可以到此处0积分下载Fabric1.4.1的脚本文件、 Fabric2.0.0的脚本文件,其他版本请自行下载
将二进制脚本文件复制到当前目录下(config_solo
)
重新执行生成指令
./generate.sh
解决了以上问题,但日志报警告提示需要在configtx.yaml
中增加共识策略,不用管,不影响运用Caliper对Fabric进行性能测试
但是你非要纠结怎么加共识,以下可有解决方案,但增加共识会导致Fabric性能测试报错,所以不用往configtx.yaml
中增加共识策略
经过多轮调试,目前已添加上共识策略,如图所示
小伙伴只需复制以下代码覆盖原有的configtx.yaml
文件即可
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
---
################################################################################
#
# Section: Organizations
#
# - This section defines the different organizational identities which will
# be referenced later in the configuration.
#
################################################################################
Organizations:
# SampleOrg defines an MSP using the sampleconfig. It should never be used
# in production but may be used as a template for other definitions
- &OrdererOrg
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: OrdererMSP
# ID to load the MSP definition as
ID: OrdererMSP
# MSPDir is th
2401_82778383: ok ,感谢!
生椰拿铁651: 无法建立ssl链接咋办啊
须弥互联网首席指挥官: 我的建议是卸了重装,别忘了sc delete mysql或者sc delete mysql80就行
孤独的求知者: 真实有效,点赞
m0_59197920: 怎么样解决了吗