使用helm部署nebulagraph失败

问答 问题
22

你好
问题1，可以进入容器，cd 到 /usr/local/nebula/logs 目录，看下nebula-graphd.ERROR、nebula-storaged.ERROR 的日志，进一步排查问题
问题2，应该是文档没有更新，operator最新的版本，svc默认用的是NodePort nebula-operator/values.yaml at master · vesoft-inc/nebula-operator · GitHub, 可以参考这个文档如何进行连接 连接 NebulaGraph - NebulaGraph Database 手册

23

使用官网文档最新的创建集群命令
helm install “${NEBULA_CLUSTER_NAME}” nebula-operator/nebula-cluster
–namespace=“${NEBULA_CLUSTER_NAMESPACE}”
–set nameOverride=${NEBULA_CLUSTER_NAME}
–set nebula.storageClassName=“${STORAGE_CLASS_NAME}”
–set nebula.version=3.4.1
–version=1.4.2
副本数改为1，无法拉取镜像
Warning Failed 78s (x4 over 3m35s) kubelet Failed to pull image “vesoft/nebula-metad:3.4.1”: rpc error: code = Unknown desc = Error response from daemon: manifest for vesoft/nebula-metad:3.4.1 not found: manifest unknown: manifest unknown
Warning Failed 78s (x4 over 3m35s) kubelet Error: ErrImagePull
Warning Failed 66s (x6 over 3m34s) kubelet Error: ImagePullBackOff
Normal BackOff 53s (x7 over 3m34s) kubelet Back-off pulling image “vesoft/nebula-metad:3.4.1”

24

感谢反馈，这里版本应该用 v3.4.1

25

那我等你们后台修改以后在部署

26

Error: failed to download “nebula-operator/nebula-cluster” at version “1.4.2” (hint: running helm repo update may help)

27

helm install nebula nebula-operator/nebula-cluster --set nebula.storageClassName=local --set nebula.version=v3.4.1 --set nebula.graphd.replicas=1 --set nebula.metad.replicas=1 --set nebula.storaged.replicas=1 --version=1.4.2 你可以用这个命令部署，我本地验证是可以的

28

您好如果是生产环境部署是不是不适合使用helm部署，因为要做一些用户名密码的认证。

29

适合的，Helm 只是一个 Kubernetes 包管理工具，它可以帮助您简化在 Kubernetes 上部署、升级和管理应用程序的过程

30

您好，再次感谢回复，部署好以后，发现9669 19669端口正常，但是19670端口连接被拒绝，请问这个端口是哪个服务监听，要如何排查呢？能否提供一个思路？

31

这是error日志

E20230413 06:04:30.873139    37 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:04:30.901764    37 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:04:30.901772    37 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230413 06:05:35.815047    36 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:05:35.818186    36 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:05:35.818193    36 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230413 06:06:22.670097    35 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:06:22.670173    35 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:06:22.670177    35 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230413 06:10:48.821354    34 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:10:48.821427    34 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 06:10:48.821431    34 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230413 18:12:32.811507    37 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 18:12:32.811554    37 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230413 18:12:32.811579    37 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230414 00:17:34.853178    36 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230414 00:17:34.857717    36 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230414 00:17:34.857722    36 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230414 01:50:04.261195    35 GeneratedCodeHelper.cpp:201] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230414 01:50:04.261227    35 GeneratedCodeHelper.cpp:134] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E20230414 01:50:04.261230    35 GeneratedCodeHelper.cpp:93] invalid message from client in function process
E20230417 05:36:02.832226    35 HeaderServerChannel.cpp:100] Received invalid request from client: apache::thrift::transport::TTransportException: Header transport frame is too large: 4294246397 (hex 0xfff4fffd) (transport apache::thrift::PreReceivedDataAsyncTransportWrapper, address 172.16.48.55, port 43366)
E20230417 05:36:02.840224    35 PeekingManager.h:262] peekSuccess failed, dropping connection: apache::thrift::transport::TTransportException: Channel is !good()
[root@nebula-cluster-graphd-0 logs]#
32

你好，19670是原来http2的端口，在nebula 3.x里被去掉了，目前没地方用到，可以不用管，我们在operator后续版本里也会把它去掉

33

再次请教，部署的时候要如何指定用户名密码。默认部署不用使用身份验证这样上生产不安全

34

你好，这应该不属于helm部署失败的问题了，可以开个新帖哈

1 个赞
35

修改密码的话需要开启身份验证，参考：身份验证 - NebulaGraph Database 手册

相关权限操作参考：用户管理 - NebulaGraph Database 手册

有其他问题的话，正如 kqzh 所说的，你可以开个新帖哈

36

好的。非常感觉回复，我会开新帖咨询