nebula-graphd: Exited

dmesg看看吧,日志没啥东西

dmesg.txt (38.0 KB)

这个dmes里面没有任何nebula相关信息。你翻翻历史的graph 的 LOG看看?比如前面几个/

另外4GB内存够不够我还真不确定,这个应该低于最低使用要求了

我这边数据量不大,之前正常运行一个月了,直到修改数据库密码重启之后出的问题。这是之前的一些log

nebula-metad.VM-0-14-centos.root.log.INFO.20230519-102923.21645 (121.5 KB)
nebula-graphd.VM-0-14-centos.root.log.ERROR.20230518-165113.3353 (5.5 KB)
nebula-graphd.VM-0-14-centos.root.log.INFO.20230518-144342.5710 (939 字节)

修改密码?

是的,原来是使用任意密码,后来修改了–enable_authorize参数为true,重启之后就nebula-graphd一直是Exited状态

我还禁用了服务器的ipv6,现在所有的通信都是ipv4

nebula.service restart graphd

之后,看下 graphd 新出来的 log 呢?

E20230522 18:44:39.047868 17006 MetaClient.cpp:772] Send request to “127.0.0.1”:9559, exceed retry limit
E20230522 18:44:39.048094 17006 MetaClient.cpp:773] RpcResponse exception: apache::thrift::transport::TTransportException: Dropping unsent request. Connection closed after: apache::thrift::transport::TTransportException: AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connection refused): Connection refused
E20230522 18:44:39.048144 17111 MetaClient.cpp:192] Heartbeat failed, status:RPC failure in MetaClient: apache::thrift::transport::TTransportException: Dropping unsent request. Connection closed after: apache::thrift::transport::TTransportException: AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connect
E20230522 18:44:52.061794 17076 MetaClient.cpp:772] Send request to “127.0.0.1”:9559, exceed retry limit
E20230522 18:44:52.061837 17076 MetaClient.cpp:773] RpcResponse exception: apache::thrift::transport::TTransportException: Dropping unsent request. Connection closed after: apache::thrift::transport::TTransportException: AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connection refused): Connection refused
E20230522 18:44:52.061878 17111 MetaClient.cpp:192] Heartbeat failed, status:RPC failure in MetaClient: apache::thrift::transport::TTransportException: Dropping unsent request. Connection closed after: apache::thrift::transport::TTransportException: AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connect

报这个错误

经过验证这个占用9669的程序是tomcat,但是tomcat配置文件中并无涉及9669,kill之后restart graphd后依然是exited

这说明 graphd 里的 meta client 连不上 metad,metad 那头日志又怎么说呢?

要不还是检查下,各个端口都是谁在占用吧。是不是有其他人和你在一起使用这个环境。你杀掉的进程,如果有systemd的话,会被重新拉起来的,你得关服务。

此话题已在最后回复的 30 天后被自动关闭。不再允许新回复。