无法启动集群,有人遇到过吗?
发布于 3 个月前 作者 goodwater 420 次浏览 来自 问答

2018-08-01 06:09:56.372+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component ‘org.neo4j.server.database.LifecycleManagingDatabase@3e48d38’ was successfully initialized, but failed to start. Please see the attached cause exception “Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}”. Starting Neo4j failed: Component ‘org.neo4j.server.database.LifecycleManagingDatabase@3e48d38’ was successfully initialized, but failed to start. Please see the attached cause exception “Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}”. org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component ‘org.neo4j.server.database.LifecycleManagingDatabase@3e48d38’ was successfully initialized, but failed to start. Please see the attached cause exception “Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}”. at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:68) at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:220) at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:111) at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:79) at com.neo4j.server.enterprise.CommercialEntryPoint.main(CommercialEntryPoint.java:22) Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component ‘org.neo4j.server.database.LifecycleManagingDatabase@3e48d38’ was successfully initialized, but failed to start. Please see the attached cause exception “Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}”. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:466) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:212) … 3 more Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, /opt/neo4j/data/databases/graph.db at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:212) at org.neo4j.kernel.ha.HighlyAvailableGraphDatabase.<init>(HighlyAvailableGraphDatabase.java:53) at org.neo4j.server.enterprise.OpenEnterpriseNeoServer.lambda$static$0(OpenEnterpriseNeoServer.java:72) at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:88) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:445) … 5 more Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component ‘org.neo4j.cluster.client.ClusterJoin@2f651f93’ was successfully initialized, but failed to start. Please see the attached cause exception “Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}”. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:466) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:445) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:208) … 9 more Caused by: java.util.concurrent.TimeoutException: Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}} at org.neo4j.cluster.statemachine.StateMachineProxyFactory$ResponseFuture.get(StateMachineProxyFactory.java:316) at org.neo4j.cluster.client.ClusterJoin.joinByConfig(ClusterJoin.java:146) at org.neo4j.cluster.client.ClusterJoin.start(ClusterJoin.java:85) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:445) … 13 more 2018-08-01 06:09:56.373+0000 INFO Neo4j Server shutdown initiated by request nohup: 忽略输入 2018-08-01 06:27:25.673+0000 INFO ======== Neo4j 3.4.0 ======== 2018-08-01 06:27:25.697+0000 INFO Starting… 2018-08-01 06:27:26.749+0000 INFO Write transactions to database disabled 2018-08-01 06:27:27.230+0000 INFO Initiating metrics… 2018-08-01 06:27:28.097+0000 INFO Attempting to join cluster of [172.16.247.135:5001, 172.16.247.132:5001, 172.16.247.136:5001]

10 回复

几台节点的集群?把每个节点上的neo4j.conf贴上来。

一共三个节点 master节点: [hadoop@master conf]$ cat neo4j.conf

dbms.directories.import=import dbms.backup.enabled=true dbms.backup.address=0.0.0.0:6362 dbms.connectors.default_listen_address=0.0.0.0 dbms.connector.bolt.enabled=true dbms.connector.bolt.listen_address=:7687 dbms.connector.http.enabled=true dbms.connector.http.listen_address=:7474 dbms.connector.https.enabled=true dbms.connector.https.listen_address=:7473

#*****************************************************************

HA configuration

#***************************************************************** dbms.mode=HA ha.server_id=1 ha.initial_hosts=172.16.247.135:5001,172.16.247.132:5001,172.16.247.136:5001 ha.pull_interval=30 dbms.shell.enabled=true dbms.shell.host=0.0.0.0 dbms.shell.port=1337 dbms.jvm.additional=-XX:+UseG1GC dbms.jvm.additional=-XX:-OmitStackTraceInFastThrow dbms.jvm.additional=-XX:+AlwaysPreTouch dbms.jvm.additional=-XX:+UnlockExperimentalVMOptions dbms.jvm.additional=-XX:+TrustFinalNonStaticFields dbms.jvm.additional=-XX:+DisableExplicitGC dbms.jvm.additional=-Djdk.tls.ephemeralDHKeySize=2048 dbms.jvm.additional=-Djdk.tls.rejectClientInitiatedRenegotiation=true dbms.windows_service_name=neo4j dbms.jvm.additional=-Dunsupported.dbms.udc.source=tarball

slave1节点: dbms.mode=HA ha.server_id=2 ha.initial_hosts=172.16.247.135:5001,172.16.247.132:5001,172.16.247.136:5001 ha.pull_interval=30

slave2节点: dbms.mode=HA ha.server_id=3 ha.initial_hosts=172.16.247.135:5001,172.16.247.132:5001,172.16.247.136:5001 ha.pull_interval=30 我参考的是这篇文章:https://blog.csdn.net/onlyoncelove/article/details/80427282

检查一下网络,看这几台能ping通吗

TimeoutException: Conversation-response mapping: {1/13#=ResponseFuture{conversationId=‘1/13#’, initiatedByMessageType=join, response=null}}

网络没问题,可以ping通 [root@master hadoop]# ping slave1 PING slave1 (172.16.247.132) 56(84) bytes of data. 64 bytes from slave1 (172.16.247.132): icmp_seq=1 ttl=64 time=0.343 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=2 ttl=64 time=0.784 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=3 ttl=64 time=0.239 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=4 ttl=64 time=0.898 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=5 ttl=64 time=1.15 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=6 ttl=64 time=0.773 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=7 ttl=64 time=0.586 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=8 ttl=64 time=0.764 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=9 ttl=64 time=0.691 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=10 ttl=64 time=0.626 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=11 ttl=64 time=1.00 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=12 ttl=64 time=0.728 ms 64 bytes from slave1 (172.16.247.132): icmp_seq=13 ttl=64 time=0.908 ms ^C — slave1 ping statistics — 13 packets transmitted, 13 received, 0% packet loss, time 12007ms rtt min/avg/max/mdev = 0.239/0.730/1.153/0.241 ms [root@master hadoop]# ping slave2 PING slave2 (172.16.247.136) 56(84) bytes of data. 64 bytes from slave2 (172.16.247.136): icmp_seq=1 ttl=64 time=0.695 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=2 ttl=64 time=0.690 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=3 ttl=64 time=0.719 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=4 ttl=64 time=0.755 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=5 ttl=64 time=0.749 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=6 ttl=64 time=0.981 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=7 ttl=64 time=0.786 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=8 ttl=64 time=0.867 ms 64 bytes from slave2 (172.16.247.136): icmp_seq=9 ttl=64 time=0.550 ms ^C — slave2 ping statistics — 9 packets transmitted, 9 received, 0% packet loss, time 8006ms rtt min/avg/max/mdev = 0.550/0.754/0.981/0.117 ms

@graphway 大佬这个配置文件有什么问题吗?

三台机器都配置就可以了 dbms.connectors.default_listen_address=0.0.0.0

为什么不配置因果集群?HA集群很快要不支持了。

@graphway HA集群快不支持了,我之前也不清楚。我也就是为了学习学习,之后再配置因果集群,多谢了。

@goodwater 我也遇到了这个问题,这个问题你解决了吗?

先关闭所有的防火墙,然后确定端口都没有冲突,因为这个端口冲突信息并没有在日志里面体现出来, 我是在一台机器上部署ha的。错误也是类似,后来找了很多帮助,终于从一条信息里面得到提示, 要几乎同时启动3个实例,这是才出现端口冲突提示。

回到顶部