Well, when I came across the crashing issue, I restart the neo4j, and it blocks at "performing recovery..", and I came back the next morning, and it's still that information. Should I wait much longer for recovery?
On Thursday, February 18, 2016 at 3:06:55 AM UTC+8, David Fauth wrote: > > How long did you let 2.2.3 try and recover? It has to recover the database > successfully before it can be loaded into a new database. > > On Tuesday, February 16, 2016 at 7:51:26 AM UTC-5, 宋鹏 wrote: >> >> Hello, wish to get some help here... >> >> I deployed a neo4j server of version 2.2.3 several months ago, but it >> crashed last week, and I can never restart it again. >> The starting process was blocked after printing the message: >> >> Detected incorrectly shut down database, performing recovery.. >>> >> >> To work around, I re-deployed a new instance of version 2.3.2, and copy >> graph.db to the data folder of this new instance. >> However, with no luck, it also failed with the following message printed >> many many times... >> >> Caused by: >>> org.neo4j.kernel.impl.storemigration.StoreUpgrader$UnexpectedUpgradingStoreVersionException: >>> >>> '/var/lib/neo4j/data/graph.db/neostore.nodestore.db' has a store version >>> number that we cannot upgrade from. Expected 'v0.A.3' but file is version >>> ''. >>> >> >> Of course, I checked that the configuration was correct: >> allow_store_upgrade=true >> >> It would be a great help if any body happens to know something about >> this. Thanks! >> >> >> >> -- 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.
