grgchain/baasmanager

基于K8S平台的区块链即服务BaaS（Blockchain as a Service），借鉴于hyperledger/cello，支持Hyperledger Fabric，但更加轻量级的架构实现

grgchain

运通链

baasmanager's Issues

构建区块链时出错，baas-fabricengine打印 Could not find profile: OrdererGenesis. 求助~~~

点击构建时，baas-fabricengine打印出错误

自己DEBUG了一会儿，发现c.profile, c.configPath都有值，configtx.yaml也正常生成，下面是configtx.yaml文件的一部分：
Profiles:
OrdererGenesis:
Policies:
Readers:
Type: ImplicitMeta
Rule: ANY Readers
Writers:
Type: ImplicitMeta
Rule: ANY Writers
Admins:
Type: ImplicitMeta
Rule: MAJORITY Admins
Capabilities:
V1_3: true
Orderer:
OrdererType: solo
Addresses:
- orderer0.adminblcokkcccchainorderer:7050
BatchTimeout: 2s

请问到底是哪里的错误，求助~~~~~~

start node error with minikube

env:

k8s : v1.14.1

shurenweideMacBook-Pro:dashboard shurenwei$ kubectl get pods --all-namespaces
NAMESPACE           NAME                                          READY   STATUS             RESTARTS   AGE
admintest3orderer   orderer0-admintest3orderer-6cfbf7b464-qqtgn   0/1     CrashLoopBackOff   5          8m56s
admintest3orderer   orderer1-admintest3orderer-5f9878dbb5-sv7vn   0/1     CrashLoopBackOff   5          8m56s
admintest3orderer   orderer2-admintest3orderer-78756755bb-7cpdt   0/1     Pending            0          8m56s
admintest3org1      ca-admintest3org1-858dfdc6b-d7dxg             0/1     CrashLoopBackOff   6          8m56s
admintest3org1      peer0-admintest3org1-599c987fbc-2pxwj         1/2     Error              5          8m56s
kube-system         coredns-d5947d4b-l2cc7                        1/1     Running            1          20m
kube-system         etcd-minikube                                 1/1     Running            2          20m
kube-system         kube-apiserver-minikube                       1/1     Running            1          20m
kube-system         kube-controller-manager-minikube              1/1     Running            1          20m
kube-system         kube-flannel-ds-amd64-lw8tk                   1/1     Running            0          15m
kube-system         kube-proxy-pvttx                              1/1     Running            2          20m
kube-system         kube-scheduler-minikube                       1/1     Running            2          20m
kube-system         kubernetes-dashboard-5f57845f9d-9vrqr         1/1     Running            0          14m
kube-system         storage-provisioner                           1/1     Running            2          21m

looking into orderer0-admintest3orderer-6cfbf7b464-qqtgn

==> storage-provisioner [78ed0583a4e0] <==
F0803 09:21:57.392043       1 main.go:37] Error getting server version: Get https://10.96.0.1:443/version: dial tcp 10.96.0.1:443: getsockopt: connection refused

==> storage-provisioner [bc7ee4fceaf5] <==
E0803 09:31:02.977450       1 controller.go:682] Error watching for provisioning success, can't provision for claim "admintest3orderer/admintest3orderer-pv": events is forbidden: User "system:serviceaccount:kube-system:storage-provisioner" cannot list resource "events" in API group "" in the namespace "admintest3orderer"
E0803 09:31:03.003174       1 controller.go:682] Error watching for provisioning success, can't provision for claim "admintest3orderer/admintest3orderer-pvdata": events is forbidden: User "system:serviceaccount:kube-system:storage-provisioner" cannot list resource "events" in API group "" in the namespace "admintest3orderer"
E0803 09:31:03.016025       1 leaderelection.go:273] Failed to update lock: Operation cannot be fulfilled on persistentvolumeclaims "admintest3orderer-pv": the object has been modified; please apply your changes to the latest version and try again
E0803 09:31:03.048753       1 leaderelection.go:273] Failed to update lock: Operation cannot be fulfilled on persistentvolumeclaims "admintest3orderer-pvdata": the object has been modified; please apply your changes to the latest version and try again
E0803 09:31:03.052603       1 controller.go:682] Error watching for provisioning success, can't provision for claim "admintest3org1/admintest3org1-pv": events is forbidden: User "system:serviceaccount:kube-system:storage-provisioner" cannot list resource "events" in API group "" in the namespace "admintest3org1"
E0803 09:31:03.245313       1 controller.go:682] Error watching for provisioning success, can't provision for claim "admintest3org1/admintest3org1-pvdata": events is forbidden: User "system:serviceaccount:kube-system:storage-provisioner" cannot list resource "events" in API group "" in the namespace "admintest3org1"

I really don't know how to fix above error.

创建channel失败

报错信息:
2020/01/14 10:16:02 [Recovery] 2020/01/14 - 10:16:02 panic recovered:
POST /defChannelAndBuild HTTP/1.1
Host: localhost:4991
Accept-Encoding: gzip
Content-Length: 146
Content-Type: application/json;charset=utf-8
User-Agent: Go-http-client/1.1

runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:82 (0xc34a30)
panicmem: panic(memoryError)
/usr/local/go/src/runtime/signal_unix.go:390 (0xc3485f)
sigpanic: panicmem()
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/hyperledger/fabric-sdk-go/pkg/fabsdk/context.go:53 (0x16b25d5)
(*FabricSDK).newIdentity: orgName: sdk.provider.IdentityConfig().Client().Organization,
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/hyperledger/fabric-sdk-go/pkg/fabsdk/fabsdk.go:368 (0x16b637d)
(*FabricSDK).Context.func1: identity, err := sdk.newIdentity(options...)
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/hyperledger/fabric-sdk-go/pkg/client/msp/client.go:67 (0x16b7dab)
New: ctx, err := clientProvider()
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/jonluo94/baasmanager/baas-core/core/fasdk/fasdk.go:76 (0x1727a7c)
(*FabricClient).CreateChannel: mspClient, err := mspclient.New(f.sdk.Context(), mspclient.WithOrg(f.Orgs[0]))
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/service/fabric_service.go:94 (0x174226f)
FabricService.defChannelAndBuild: fsdk.CreateChannel(fautil.GetChannelTx(chain, paths.ArtifactPath))
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/context.go:124 (0x119d589)
(*Context).Next: c.handlersc.index
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/recovery.go:83 (0x11af269)
RecoveryWithWriter.func1: c.Next()
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/context.go:124 (0x119d589)
(*Context).Next: c.handlersc.index
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/jonluo94/baasmanager/baas-core/common/gintool/ginlog.go:16 (0x11be7f0) Logger.func1: c.Next()
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/context.go:124 (0x119d589)
(*Context).Next: c.handlersc.index
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/gin.go:389 (0x11a6a71)
(*Engine).handleHTTPRequest: c.Next()
/opt/gopath/src/github.com/jonluo94/baasmanager/baas-fabricengine/vendor/github.com/gin-gonic/gin/gin.go:351 (0x11a62a3)
(*Engine).ServeHTTP: engine.handleHTTPRequest(c)
/usr/local/go/src/net/http/server.go:2774 (0xed1157)
serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/usr/local/go/src/net/http/server.go:1878 (0xeccd40)
(*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/usr/local/go/src/runtime/asm_amd64.s:1337 (0xc4c3c0)
goexit: BYTE $0x90 // NOP

fabric引擎log报通道创建失败，重新刷新前端，通道却显示成功了

为什么不用go-micro呢

搭建了作者的服务，发现调用过程比较慢，作者用的是gin框架的http调用，既然搞成这样的微服务为什么没有用go-micro等这样的微服务框架呢？是出于什么考虑吗？

有大神遇到过fasdk could not get chConfig cache reference的问题吗

在前台创建通道之后，看后台的baas-fabricengine一直再报这个错误，有人遇到过吗

[ERRO] fasdk 2024-02-27 18:27:00 [(*FabricClient).QueryLedger] : could not get chConfig cache reference: QueryBlockConfig failed: queryChaincode failed: Transaction processing for endorser [192.168.101.52:30899]: Endorser Client Status Code: (2) CONNECTION_FAILED. Description: dialing connection timed out [192.168.101.52:30899]

链码安装调用问题

链码实例化启动失败，无法编译启动链码容器

没有找到配置文件feconfig.yaml文件

您好，这个yaml文件是生成的？还是这个项目里本来就有的？我没有找到这个文件。
这个项目在Ubuntu里可以进行部署吗？

这里还有人讨论这个框架的吗？

用的这个脚手架，遇到些问题、弄了几天内都没解决！网上都是单一的、试过了没用！想来这问下、可是都没什么人活跃！

有用这个搭建且成功运行的人吗

admin登陆后，退出重新用普通用户登陆，有可能会跳转到用户管理界面，提示找不到该页面，建议更改为直接跳转到首页

rt
ps：系统做的很赞，但是存在一些bug，希望尽快更新哟

创建channel失败，失败原因：[ERRO] password 2019-07-29 16:54:23 [(*FabricClient).CreateChannel] : create channel failed: SendEnvelope failed: calling orderer '10.16.32.11:31938' failed: Orderer Client Status Code: (2) CONNECTION_FAILED. Description: dialing connection timed out [10.16.32.11:31938]

前提：centos7 防火墙已关闭，seLinux设为0

点击添加之后，fabric-engine服务打印出如下错误：

查看k8s-dashboard里容器组错误如下：

上面说的连接端口号为31938的超时，发现31938是proxy在监听

telnet试了一下，连接不通

不知道是什么原因，大神帮忙看一下

创建通道失败，求解答

[(*FabricClient).JoinChannel] : Org peers failed to JoinChannel: genesis block retrieval failed: Orderer Server Status Code: (400) BAD_REQUEST. Description: error status from ordering service

调用链码失败问题

ERRO 5adb�[0m [btc][92a7a473]
failed to invoke chaincode name:"lscc" , error: container exited with 0
github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1
/opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/runtime_launcher.go:63
runtime.goexit
/opt/go/src/runtime/asm_amd64.s:1333
chaincode registration failed

添加部署链码之后，调用链码失败，看了内部日志，报这个错误，请教一下，这是系统问题还是我环境的问题，其他人有遇到过吗？

Missing package file jonluo94/fabric-goclient

"github.com/jonluo94/fabric-goclient"

kafka yaml error

https://github.com/jonluo94/baasmanager/blob/cf06ac5109143da5eec00d6fb412d103cf402f30/baas-template/kafka.yaml#L75