Hi, I am trying to setup multi Machine cluster for Neo4j 3.0.1(Milestone). I am repeatedly getting the following error from my Log Files.
2016-05-13 06:26:35.251+0000 INFO Attempting to join cluster of [192.168.0.231:5001, 192.168.1.90:5001, 192.168.1.183:5001] 2016-05-13 06:27:05.754+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@51e5cc21' was successfully initialized, but failed to start. Please see attached cause exception. Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@51e5cc21' was successfully initialized, but failed to start. Please see attached cause exception. org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@51e5cc21' was successfully initialized, but failed to start. Please see attached cause exception. at org.neo4j.server.exception.ServerStartupErrors.translateToServerStartupError(ServerStartupErrors.java:68) at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:217) at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:81) at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:60) at org.neo4j.server.enterprise.EnterpriseEntryPoint.main(EnterpriseEntryPoint.java:32) Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.server.database.LifecycleManagingDatabase@51e5cc21' was successfully initialized, but failed to start. Please see attached cause exception. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:189) ... 3 more Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.ha.factory.HighlyAvailableFacadeFactory, /home/yayati.sule/Master/neo4j-enterprise-3.0.1/data/databases/graph.db at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:144) at org.neo4j.kernel.ha.factory.HighlyAvailableFacadeFactory.newFacade(HighlyAvailableFacadeFactory.java:42) at org.neo4j.kernel.ha.HighlyAvailableGraphDatabase.<init>(HighlyAvailableGraphDatabase.java:41) at org.neo4j.server.enterprise.EnterpriseNeoServer.lambda$static$0(EnterpriseNeoServer.java:80) at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:89) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) ... 5 more Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.cluster.client.ClusterJoin@d8af863' was successfully initialized, but failed to start. Please see attached cause exception. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:444) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.newFacade(GraphDatabaseFacadeFactory.java:140) ... 10 more Caused by: java.util.concurrent.TimeoutException at org.neo4j.cluster.statemachine.StateMachineProxyFactory$ResponseFuture.get(StateMachineProxyFactory.java:300) at org.neo4j.cluster.client.ClusterJoin.joinByConfig(ClusterJoin.java:143) at org.neo4j.cluster.client.ClusterJoin.start(ClusterJoin.java:82) at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:434) I have also attached a copy of my "neo4j.conf" file . Kindly help me on this. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
#***************************************************************** # Neo4j configuration #***************************************************************** # The name of the database to mount dbms.active_database=graph.db # Paths of directories in the installation. #dbms.directories.data=data #dbms.directories.plugins=plugins #dbms.directories.certificates=certificates # This setting constrains all `LOAD CSV` import files to be under the `import` directory. Remove or uncomment it to # allow files to be loaded from anywhere in filesystem; this introduces possible security problems. See the `LOAD CSV` # section of the manual for details. dbms.directories.import=import # Whether requests to Neo4j are authenticated. # To disable authentication, uncomment this line #dbms.security.auth_enabled=false # Enable this to be able to upgrade a store from an older version. #dbms.allow_format_migration=true # The amount of memory to use for mapping the store files, in bytes (or # kilobytes with the 'k' suffix, megabytes with 'm' and gigabytes with 'g'). # If Neo4j is running on a dedicated server, then it is generally recommended # to leave about 2-4 gigabytes for the operating system, give the JVM enough # heap to hold all your transaction state and query context, and then leave the # rest for the page cache. # The default page cache memory assumes the machine is dedicated to running # Neo4j, and is heuristically set to 50% of RAM minus the max Java heap size. #dbms.memory.pagecache.size=10g # Enable online backups to be taken from this database. #dbms.backup.enabled=true # To allow remote backups, uncomment this line: #dbms.backup.address=0.0.0.0:6362 #***************************************************************** # Network connector configuration #***************************************************************** # Bolt connector dbms.connector.bolt.type=BOLT dbms.connector.bolt.enabled=true dbms.connector.bolt.tls_level=OPTIONAL # To have Bolt accept non-local connections, uncomment this line # dbms.connector.bolt.address=0.0.0.0:7687 # HTTP Connector dbms.connector.http.type=HTTP dbms.connector.http.enabled=true #dbms.connector.http.encryption=NONE # To have HTTP accept non-local connections, uncomment this line dbms.connector.http.address=0.0.0.0:7474 # HTTPS Connector dbms.connector.https.type=HTTP dbms.connector.https.enabled=true dbms.connector.https.encryption=TLS dbms.connector.https.address=localhost:7473 # Number of Neo4j worker threads. #dbms.threads.worker_count= #***************************************************************** # Logging configuration #***************************************************************** # To enable HTTP logging, uncomment this line #dbms.logs.http.enabled=true # To enable GC Logging, uncomment this line #dbms.logs.gc.enabled=true # GC Logging Options # see http://docs.oracle.com/cd/E19957-01/819-0084-10/pt_tuningjava.html#wp57013 for more information. #dbms.logs.gc.options=-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -XX:+PrintTenuringDistribution # Number of GC logs to keep. #dbms.logs.gc.rotation.keep_number=5 # Size of each GC log that is kept. #dbms.logs.gc.rotation.size=20m # Size threshold for rotation of the debug log. If set to zero then no rotation will occur. Accepts a binary suffix "k", # "m" or "g". #dbms.logs.debug.rotation.size=20m # Maximum number of history files for the internal log. #dbms.logs.debug.rotation.keep_number=7 # Log executed queries that takes longer than the configured threshold. Enable by uncommenting this line. #dbms.logs.query.enabled=true # If the execution of query takes more time than this threshold, the query is logged. If set to zero then all queries # are logged. #dbms.logs.query.threshold=0 # The file size in bytes at which the query log will auto-rotate. If set to zero then no rotation will occur. Accepts a # binary suffix "k", "m" or "g". #dbms.logs.query.rotation.size=20m # Maximum number of history files for the query log. #dbms.logs.query.rotation.keep_number=7 #***************************************************************** # HA configuration #***************************************************************** # Uncomment and specify these lines for running Neo4j in High Availability mode. # See the High availability setup tutorial for more details on these settings # http://neo4j.com/docs/3.0.1/ha-setup-tutorial.html # Database mode # Allowed values: # HA - High Availability # SINGLE - Single mode, default. # To run in High Availability mode uncomment this line: dbms.mode=HA # ha.server_id is the number of each instance in the HA cluster. It should be # an integer (e.g. 1), and should be unique for each cluster instance. ha.server_id=1 # ha.initial_hosts is a comma-separated list (without spaces) of the host:port # where the ha.host.coordination of all instances will be listening. Typically # this will be the same for all cluster instances. ha.initial_hosts=192.168.0.231:5001,192.168.1.90:5001,192.168.1.183:5001 # IP and port for this instance to listen on, for communicating cluster status # information iwth other instances (also see ha.initial_hosts). The IP # must be the configured IP address for one of the local interfaces. #ha.host.coordination=127.0.0.1:5001 # IP and port for this instance to listen on, for communicating transaction # data with other instances (also see ha.initial_hosts). The IP # must be the configured IP address for one of the local interfaces. #ha.host.data=127.0.0.1:6001 # The interval at which slaves will pull updates from the master. Comment out # the option to disable periodic pulling of updates. Unit is seconds. ha.pull_interval=10 # Amount of slaves the master will try to push a transaction to upon commit # (default is 1). The master will optimistically continue and not fail the # transaction even if it fails to reach the push factor. Setting this to 0 will # increase write performance when writing through master but could potentially # lead to branched data (or loss of transaction) if the master goes down. #ha.tx_push_factor=1 # Strategy the master will use when pushing data to slaves (if the push factor # is greater than 0). There are three options available "fixed_ascending" (default), # "fixed_descending" or "round_robin". Fixed strategies will start by pushing to # slaves ordered by server id (accordingly with qualifier) and are useful when # planning for a stable fail-over based on ids. #ha.tx_push_strategy=fixed_ascending # Policy for how to handle branched data. #ha.branched_data_policy=keep_all # How often heartbeat messages should be sent. Defaults to ha.default_timeout. #ha.heartbeat_interval=5s # Timeout for heartbeats between cluster members. Should be at least twice that of ha.heartbeat_interval. #ha.heartbeat_timeout=11s # If you are using a load-balancer that doesn't support HTTP Auth, you may need to turn off authentication for the # HA HTTP status endpoint by uncommenting the following line. #dbms.security.ha_status_auth_enabled=false # Whether this instance should only participate as slave in cluster. If set to # true, it will never be elected as master. #ha.slave_only=false #***************************************************************** # Miscellaneous configuration #***************************************************************** # Enable this to specify a parser other than the default one. #cypher.default_language_version=3.0 # Determines if Cypher will allow using file URLs when loading data using # `LOAD CSV`. Setting this value to `false` will cause Neo4j to fail `LOAD CSV` # clauses that load data from the file system. #dbms.security.allow_csv_import_from_file_urls=true # Retention policy for transaction logs needed to perform recovery and backups. #dbms.tx_log.rotation.retention_policy=7 days # Limit the number of IOs the background checkpoint process will consume per second. # This setting is advisory, is ignored in Neo4j Community Edition, and is followed to # best effort in Enterprise Edition. # An IO is in this case a 8 KiB (mostly sequential) write. Limiting the write IO in # this way will leave more bandwidth in the IO subsystem to service random-read IOs, # which is important for the response time of queries when the database cannot fit # entirely in memory. The only drawback of this setting is that longer checkpoint times # may lead to slightly longer recovery times in case of a database or system crash. # A lower number means lower IO pressure, and consequently longer checkpoint times. # The configuration can also be commented out to remove the limitation entirely, and # let the checkpointer flush data as fast as the hardware will go. # Set this to -1 to disable the IOPS limit. # dbms.checkpoint.iops.limit=1000 # Enable a remote shell server which Neo4j Shell clients can log in to. #dbms.shell.enabled=true # The network interface IP the shell will listen on (use 0.0.0.0 for all interfaces). #dbms.shell.host=127.0.0.1 # The port the shell will listen on, default is 1337. #dbms.shell.port=1337 # Only allow read operations from this Neo4j instance. This mode still requires # write access to the directory for lock purposes. #dbms.read_only=false # Comma separated list of JAX-RS packages containing JAX-RS resources, one # package name for each mountpoint. The listed package names will be loaded # under the mountpoints specified. Uncomment this line to mount the # org.neo4j.examples.server.unmanaged.HelloWorldResource.java from # neo4j-server-examples under /examples/unmanaged, resulting in a final URL of # http://localhost:7474/examples/unmanaged/helloworld/{nodeId} #dbms.unmanaged_extension_classes=org.neo4j.examples.server.unmanaged=/examples/unmanaged
