[Neo4j] Re: Neo4j database ALWAYS shuts down incorrectly if start/stop as a service from a list of windows services
Ok, After having an email thread with neo4j support team (thanks them for quick and full responses for all my questions) I have decided to use neo4jshell.bat as a workaround for closing the database properly. Also, it is important to note that neo4j 1.9.5 cannot be directly upgraded to 2.1.2. 1.9.5 must be upgraded to 2.0.3 first, then to 2.1.2. Thanks, Denys On Wednesday, June 18, 2014 3:04:19 PM UTC+3, Denys Hryvastov wrote: > > Thank you, Jim! > > Your post was really very useful for me, it has given me some more > thoughts and information. > I will continue with my experiments and will post here the results that I > will get. > > -Denys > > On Wednesday, June 18, 2014 12:45:08 AM UTC+3, Jim Salmons wrote: >> >> Hi Denys, >> >> I think you're experience is a variation of mine as related here >> <https://groups.google.com/d/msg/neo4j/Qp2azbKy2_8/u4jDbiBLlesJ>. Seems >> to be a long-standing issue that hasn't bitten too many but is problematic >> for the 2.1 database migration. There are some tips/insight on the link. >> The Neo folks are aware of the issue so I expect we'll see a fix at some >> point, maybe soon. >> >> Have you tried the "Ole Out and In" -- dump it from your 'corrupt' DB and >> load it in an empty 2.1? I had a number of tiny to small research and >> self-learning DBs that it was so much easier to go out and back in on a >> fresh 2.1 store. >> >> That tip about timeouts might help you, too. And the Neo4j Mojo that I am >> not qualified to comment on and I suspect is a big factor has to do with >> leveraging 2.0+ version indexing and constraints, etc. There might be some >> tweaks to the schema that you can make before migrating that, along with >> the increased timeout value, might give the migration process the room to >> work its one-time-only procedure. >> >> It's a painful problem but, as you can imagine, hits a relative small >> segment of the broader Neo4j community. BTW, if you run Neo4j as a Windows >> Service, have you tried my mini Control Panel? :-) >> http://jim-salmons.github.io/neo4jcp/ >> >> I've subscribed to this thread and will let you know if I learn anything >> more, etc. >> >> --Jim-- >> >> www.FactMiners.org and www.SoftalkApple.com >> >> On Tuesday, June 17, 2014 4:50:09 AM UTC-5, Denys Hryvastov wrote: >>> >>> Here is a stack trace that I get when I try to do upgrade from 1.9.5 to >>> 2.0: >>> >>> 2014-06-17 09:48:27.319+ INFO [API] Setting startup timeout to: >>> 12ms based on -1 >>> Detected incorrectly shut down database, performing recovery.. >>> 2014-06-17 09:48:28.108+ DEBUG [API] >>> org.neo4j.server.ServerStartupException: Starting Neo4j Server failed: >>> Error starting org.neo4j.kernel.EmbeddedGraphDatabase, >>> D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db >>> at >>> org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:209) >>> ~[neo4j-server-2.0.0.jar:2.0.0] >>> at org.neo4j.server.Bootstrapper.start(Bootstrapper.java:87) >>> [neo4j-server-2.0.0.jar:2.0.0] >>> at org.neo4j.server.Bootstrapper.main(Bootstrapper.java:50) >>> [neo4j-server-2.0.0.jar:2.0.0] >>> Caused by: java.lang.RuntimeException: Error starting >>> org.neo4j.kernel.EmbeddedGraphDatabase, >>> D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db >>> at >>> org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:333) >>> >>> ~[neo4j-kernel-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.kernel.EmbeddedGraphDatabase.(EmbeddedGraphDatabase.java:63) >>> >>> ~[neo4j-kernel-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.graphdb.factory.GraphDatabaseFactory$1.newDatabase(GraphDatabaseFactory.java:92) >>> >>> ~[neo4j-kernel-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.graphdb.factory.GraphDatabaseBuilder.newGraphDatabase(GraphDatabaseBuilder.java:198) >>> >>> ~[neo4j-kernel-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.kernel.impl.recovery.StoreRecoverer.recover(StoreRecoverer.java:115) >>> >>> ~[neo4j-kernel-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.server.preflight.PerformRecoveryIfNecessary.run(PerformRecoveryIfNecessary.java:59) >>> >>> ~[neo4j-server-2.0.0.jar:2.0.0] >>> at >>> org.neo4j.server.preflight.PreFlightTasks.run(PreFlightTasks.java:7
[Neo4j] Re: Neo4j database ALWAYS shuts down incorrectly if start/stop as a service from a list of windows services
Thank you, Jim! Your post was really very useful for me, it has given me some more thoughts and information. I will continue with my experiments and will post here the results that I will get. -Denys On Wednesday, June 18, 2014 12:45:08 AM UTC+3, Jim Salmons wrote: > > Hi Denys, > > I think you're experience is a variation of mine as related here > <https://groups.google.com/d/msg/neo4j/Qp2azbKy2_8/u4jDbiBLlesJ>. Seems > to be a long-standing issue that hasn't bitten too many but is problematic > for the 2.1 database migration. There are some tips/insight on the link. > The Neo folks are aware of the issue so I expect we'll see a fix at some > point, maybe soon. > > Have you tried the "Ole Out and In" -- dump it from your 'corrupt' DB and > load it in an empty 2.1? I had a number of tiny to small research and > self-learning DBs that it was so much easier to go out and back in on a > fresh 2.1 store. > > That tip about timeouts might help you, too. And the Neo4j Mojo that I am > not qualified to comment on and I suspect is a big factor has to do with > leveraging 2.0+ version indexing and constraints, etc. There might be some > tweaks to the schema that you can make before migrating that, along with > the increased timeout value, might give the migration process the room to > work its one-time-only procedure. > > It's a painful problem but, as you can imagine, hits a relative small > segment of the broader Neo4j community. BTW, if you run Neo4j as a Windows > Service, have you tried my mini Control Panel? :-) > http://jim-salmons.github.io/neo4jcp/ > > I've subscribed to this thread and will let you know if I learn anything > more, etc. > > --Jim-- > > www.FactMiners.org and www.SoftalkApple.com > > On Tuesday, June 17, 2014 4:50:09 AM UTC-5, Denys Hryvastov wrote: >> >> Here is a stack trace that I get when I try to do upgrade from 1.9.5 to >> 2.0: >> >> 2014-06-17 09:48:27.319+ INFO [API] Setting startup timeout to: >> 12ms based on -1 >> Detected incorrectly shut down database, performing recovery.. >> 2014-06-17 09:48:28.108+ DEBUG [API] >> org.neo4j.server.ServerStartupException: Starting Neo4j Server failed: >> Error starting org.neo4j.kernel.EmbeddedGraphDatabase, >> D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db >> at >> org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:209) >> ~[neo4j-server-2.0.0.jar:2.0.0] >> at org.neo4j.server.Bootstrapper.start(Bootstrapper.java:87) >> [neo4j-server-2.0.0.jar:2.0.0] >> at org.neo4j.server.Bootstrapper.main(Bootstrapper.java:50) >> [neo4j-server-2.0.0.jar:2.0.0] >> Caused by: java.lang.RuntimeException: Error starting >> org.neo4j.kernel.EmbeddedGraphDatabase, >> D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db >> at >> org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:333) >> >> ~[neo4j-kernel-2.0.0.jar:2.0.0] >> at >> org.neo4j.kernel.EmbeddedGraphDatabase.(EmbeddedGraphDatabase.java:63) >> ~[neo4j-kernel-2.0.0.jar:2.0.0] >> at >> org.neo4j.graphdb.factory.GraphDatabaseFactory$1.newDatabase(GraphDatabaseFactory.java:92) >> >> ~[neo4j-kernel-2.0.0.jar:2.0.0] >> at >> org.neo4j.graphdb.factory.GraphDatabaseBuilder.newGraphDatabase(GraphDatabaseBuilder.java:198) >> >> ~[neo4j-kernel-2.0.0.jar:2.0.0] >> at >> org.neo4j.kernel.impl.recovery.StoreRecoverer.recover(StoreRecoverer.java:115) >> >> ~[neo4j-kernel-2.0.0.jar:2.0.0] >> at >> org.neo4j.server.preflight.PerformRecoveryIfNecessary.run(PerformRecoveryIfNecessary.java:59) >> >> ~[neo4j-server-2.0.0.jar:2.0.0] >> at >> org.neo4j.server.preflight.PreFlightTasks.run(PreFlightTasks.java:70) >> ~[neo4j-server-2.0.0.jar:2.0.0] >> at >> org.neo4j.server.AbstractNeoServer.runPreflightTasks(AbstractNeoServer.java:319) >> >> ~[neo4j-server-2.0.0.jar:2.0.0] >> at >> org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:144) >> ~[neo4j-server-2.0.0.jar:2.0.0] >> ... 2 common frames omitted >> Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component >> 'org.neo4j.kernel.impl.transaction.XaDataSourceManager@2b1eb67d' was >> successfully initialized, but failed to start. >> Please see attached cause exception. >> at >> org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:504) >> >> ~[neo4j-kernel-2.0.0.jar:2.0.0]
[Neo4j] Re: Neo4j database ALWAYS shuts down incorrectly if start/stop as a service from a list of windows services
Here is a stack trace that I get when I try to do upgrade from 1.9.5 to 2.0: 2014-06-17 09:48:27.319+ INFO [API] Setting startup timeout to: 12ms based on -1 Detected incorrectly shut down database, performing recovery.. 2014-06-17 09:48:28.108+ DEBUG [API] org.neo4j.server.ServerStartupException: Starting Neo4j Server failed: Error starting org.neo4j.kernel.EmbeddedGraphDatabase, D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:209) ~[neo4j-server-2.0.0.jar:2.0.0] at org.neo4j.server.Bootstrapper.start(Bootstrapper.java:87) [neo4j-server-2.0.0.jar:2.0.0] at org.neo4j.server.Bootstrapper.main(Bootstrapper.java:50) [neo4j-server-2.0.0.jar:2.0.0] Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.EmbeddedGraphDatabase, D:\Neo4j\neo4j-enterprise-2.0.0\data\graph.db at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:333) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.EmbeddedGraphDatabase.(EmbeddedGraphDatabase.java:63) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.graphdb.factory.GraphDatabaseFactory$1.newDatabase(GraphDatabaseFactory.java:92) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.graphdb.factory.GraphDatabaseBuilder.newGraphDatabase(GraphDatabaseBuilder.java:198) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.recovery.StoreRecoverer.recover(StoreRecoverer.java:115) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.server.preflight.PerformRecoveryIfNecessary.run(PerformRecoveryIfNecessary.java:59) ~[neo4j-server-2.0.0.jar:2.0.0] at org.neo4j.server.preflight.PreFlightTasks.run(PreFlightTasks.java:70) ~[neo4j-server-2.0.0.jar:2.0.0] at org.neo4j.server.AbstractNeoServer.runPreflightTasks(AbstractNeoServer.java:319) ~[neo4j-server-2.0.0.jar:2.0.0] at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:144) ~[neo4j-server-2.0.0.jar:2.0.0] ... 2 common frames omitted Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.transaction.XaDataSourceManager@2b1eb67d' was successfully initialized, but failed to start. Please see attached cause exception. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:504) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:115) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.InternalAbstractGraphDatabase.run(InternalAbstractGraphDatabase.java:310) ~[neo4j-kernel-2.0.0.jar:2.0.0] ... 10 common frames omitted Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.impl.nioneo.xa.NeoStoreXaDataSource@1bf5df6a' was successfully initialized, but failed to start. P lease see attached cause exception. at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:504) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:115) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.transaction.XaDataSourceManager.start(XaDataSourceManager.java:164) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:498) ~[neo4j-kernel-2.0.0.jar:2.0.0] ... 12 common frames omitted Caused by: org.neo4j.kernel.impl.storemigration.StoreUpgrader$UpgradingStoreVersionNotFoundException: 'neostore' does not contain a store version, please ensure that the original datab ase was shut down in a clean state. at org.neo4j.kernel.impl.storemigration.UpgradableDatabase.checkUpgradeable(UpgradableDatabase.java:85) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.storemigration.StoreUpgrader.attemptUpgrade(StoreUpgrader.java:72) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.nioneo.store.StoreFactory.tryToUpgradeStores(StoreFactory.java:143) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.nioneo.store.StoreFactory.newNeoStore(StoreFactory.java:123) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.impl.nioneo.xa.NeoStoreXaDataSource.start(NeoStoreXaDataSource.java:323) ~[neo4j-kernel-2.0.0.jar:2.0.0] at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:498) ~[neo4j-kernel-2.0.0.jar:2.0.0] ... 15 common frames omitted 2014-06-17 09:48:28.109+ DEBUG [API] Failed to start Neo Server on port [7474] -- 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] Neo4j database ALWAYS shuts down incorrectly if start/stop as a service from a list of windows services
Hi - I use neo4j as a windows service. It was installed using something like "neo4j.bat install". After that "neo4j database" appeared in the list of windows services and I start/stop neo4j server from there. But what I have noticed: when I stop neo4j from the list of windows services - it ALWAYS stops incorrectly. When I start neo4j server using another way - run neo4j.bat file, then new java window is opened and is hanging all the time neo4j server is running. After that if I stop neo4j server by pressing Ctrl+C when this Java window is active, then neo4j server stops correctly (next time when I start neo4j, there is no message that neo4j server was incorrectly shut down). The question is: why does neo4j server always shut down incorrectly if I use neo4j as a service? It causes a real issue, because I cannot upgrade my database from 1.9.5 to 2.0. It says me that upgrade was not performed because the database was incorrectly shut down previous time... Could you please tell me how to workaround this, or what I do wrong? I tried starting neo4j from a list of services and by running neo4j.bat (did comparison of behavior) with 1.9.5, 2.0 and 2.1.2 versions. Thanks, Denys -- 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.
Re: [Neo4j] Web Admin shows that entities counts increased after restarting neo4j server (1.9.5 version)
Ok, so the results of my experience. 1) Installed neo4j as a service (neo-1.9.5), using neo4j.bat install command. Service is installed. 2) Started neo4j. 1 node (root node) and 0 relationships are present. This is expected. 3) Started neoclipse, created new connection, created 4 nodes and 5 relationships. Closed connection. 4) Web Admin shows me 4 nodes and 5 relationships, this is expected. 5) Stopped neo4j server from the list of windows services. 6) Started neo4j server from the list of windows services. Looks like everything was started and stopped correctly. Actual result - web admin shows: 7922 nodes, 95325 relationships. On Friday, January 17, 2014 7:14:14 PM UTC+2, Denys Hryvastov wrote: > > Thank you for quick response, Michael. > I will verify again, but I stopped neo4j server from the list of windows > services, I do not think that this is hard kill... > My only concern is that neo4j server was installed as windows service my > our code, may be there is some issue here. > I will try to install it as a service using neo4j bat file, then add some > nodes and relationships using neoclipse (not my app under Jboss) and will > see the result. > > After making this experiment, I will let you know the results. > > Thanks, > Denys > > > On Friday, January 17, 2014 6:51:03 PM UTC+2, Michael Hunger wrote: >> >> Believe cypher >> Ignore webadmin >> >> This happens after a hard kill >> >> Try to shutdown your Neo4j correctly with the appropriate jboss undeploy >> hooks >> >> >> Sent from mobile device >> >> Am 17.01.2014 um 17:16 schrieb Denys Hryvastov : >> >> Hi - >> >> Our team was previously using neo4j-1.8.2, now we want to upgrade to >> neo4j-1.9.5 (later on we will possibly upgrade to version 2.0). >> >> But I have noticed such strange behavior. After loading data from our >> application to neo4j, I have 226 nodes in neo4j database and 1092 >> relationships. This is correct numbers. >> After that I stop Jboss (our application which is working with neo4j is >> working under Jboss) and restart neo4j server (Jboss is still stopped to be >> sure that nobody creates new entities in neo4j). >> When neo4j restart is done, neo4j web admin shows me 1864 nodes (instead >> of 226) and 23513 relationships (instead of 1092). >> BUT, interesting point is that, when I run cypher query "START >> root=node(*) RETURN root" then 226 nodes are returned. >> When I run cypher query "START root=relationship(*) RETURN root" then >> 1092 relationships are returned. >> >> If I restart neo4j server for the second time, then the numbers do not >> increase any more. >> >> What can cause this issue? What is happening and how this can we fix >> this? Our QA are using neo4j web admin for testing and these numbers looks >> really confusing... >> Also, what result should I believe: should I believe to what web admin >> shows me or should I believe the results of cypher query execution? >> >> Thanks, >> Denys >> >> -- >> 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+un...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- 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/groups/opt_out.
Re: [Neo4j] Web Admin shows that entities counts increased after restarting neo4j server (1.9.5 version)
Thank you for quick response, Michael. I will verify again, but I stopped neo4j server from the list of windows services, I do not think that this is hard kill... My only concern is that neo4j server was installed as windows service my our code, may be there is some issue here. I will try to install it as a service using neo4j bat file, then add some nodes and relationships using neoclipse (not my app under Jboss) and will see the result. After making this experiment, I will let you know the results. Thanks, Denys On Friday, January 17, 2014 6:51:03 PM UTC+2, Michael Hunger wrote: > > Believe cypher > Ignore webadmin > > This happens after a hard kill > > Try to shutdown your Neo4j correctly with the appropriate jboss undeploy > hooks > > > Sent from mobile device > > Am 17.01.2014 um 17:16 schrieb Denys Hryvastov > >: > > Hi - > > Our team was previously using neo4j-1.8.2, now we want to upgrade to > neo4j-1.9.5 (later on we will possibly upgrade to version 2.0). > > But I have noticed such strange behavior. After loading data from our > application to neo4j, I have 226 nodes in neo4j database and 1092 > relationships. This is correct numbers. > After that I stop Jboss (our application which is working with neo4j is > working under Jboss) and restart neo4j server (Jboss is still stopped to be > sure that nobody creates new entities in neo4j). > When neo4j restart is done, neo4j web admin shows me 1864 nodes (instead > of 226) and 23513 relationships (instead of 1092). > BUT, interesting point is that, when I run cypher query "START > root=node(*) RETURN root" then 226 nodes are returned. > When I run cypher query "START root=relationship(*) RETURN root" then 1092 > relationships are returned. > > If I restart neo4j server for the second time, then the numbers do not > increase any more. > > What can cause this issue? What is happening and how this can we fix this? > Our QA are using neo4j web admin for testing and these numbers looks really > confusing... > Also, what result should I believe: should I believe to what web admin > shows me or should I believe the results of cypher query execution? > > Thanks, > Denys > > -- > 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+un...@googlegroups.com . > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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/groups/opt_out.
[Neo4j] Web Admin shows that entities counts increased after restarting neo4j server (1.9.5 version)
Hi - Our team was previously using neo4j-1.8.2, now we want to upgrade to neo4j-1.9.5 (later on we will possibly upgrade to version 2.0). But I have noticed such strange behavior. After loading data from our application to neo4j, I have 226 nodes in neo4j database and 1092 relationships. This is correct numbers. After that I stop Jboss (our application which is working with neo4j is working under Jboss) and restart neo4j server (Jboss is still stopped to be sure that nobody creates new entities in neo4j). When neo4j restart is done, neo4j web admin shows me 1864 nodes (instead of 226) and 23513 relationships (instead of 1092). BUT, interesting point is that, when I run cypher query "START root=node(*) RETURN root" then 226 nodes are returned. When I run cypher query "START root=relationship(*) RETURN root" then 1092 relationships are returned. If I restart neo4j server for the second time, then the numbers do not increase any more. What can cause this issue? What is happening and how this can we fix this? Our QA are using neo4j web admin for testing and these numbers looks really confusing... Also, what result should I believe: should I believe to what web admin shows me or should I believe the results of cypher query execution? Thanks, Denys -- 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/groups/opt_out.
