Interestingly, other queries appear to run just fine, but there appears to be a problem with any query using the 'Start' directive...
On Friday, 12 May 2017 14:58:10 UTC+1, [email protected] wrote: > > > Hi, > > Noticing that the latest Neo4j Enterprise release was available today, I > downloaded it and gave it a try. > > On trying to start the DB I noticed that there was a message saying that I > need to set dbms.allow_format_migration=true > > Following setting this parameter, the DB started with no apparent errors: > > 2017-05-12 08:27:01.207+0000 INFO ======== Neo4j 3.2.0 ======== > 2017-05-12 08:27:01.605+0000 INFO No SSL certificate found, generating a > self-signed certificate.. > 2017-05-12 08:27:06.233+0000 INFO Starting... > 2017-05-12 08:27:14.724+0000 INFO Bolt enabled on 127.0.0.1:7687. > 2017-05-12 08:27:14.942+0000 INFO Initiating metrics... > 2017-05-12 08:27:17.608+0000 ERROR Neo4j cannot be started, because the > database files require upgrading and upgrades are disabled in > configuration. Please set 'dbms.allow_format_migration' to 'true' in your > configuration file and try again. > 2017-05-12 08:27:17.610+0000 INFO Neo4j Server shutdown initiated by > request > nohup: ignoring input > 2017-05-12 08:42:42.694+0000 INFO ======== Neo4j 3.2.0 ======== > 2017-05-12 08:42:43.346+0000 INFO Starting... > 2017-05-12 08:42:44.754+0000 INFO Bolt enabled on 127.0.0.1:7687. > 2017-05-12 08:42:44.786+0000 INFO Initiating metrics... > 2017-05-12 08:42:44.996+0000 INFO Starting upgrade of database > 2017-05-12 08:42:47.047+0000 INFO Migrating Indexes (1/3): > 2017-05-12 08:42:47.052+0000 INFO 10% completed > 2017-05-12 08:42:47.052+0000 INFO 20% completed > 2017-05-12 08:42:47.052+0000 INFO 30% completed > 2017-05-12 08:42:47.052+0000 INFO 40% completed > 2017-05-12 08:42:47.052+0000 INFO 50% completed > 2017-05-12 08:42:47.053+0000 INFO 60% completed > 2017-05-12 08:42:47.053+0000 INFO 70% completed > 2017-05-12 08:42:47.053+0000 INFO 80% completed > 2017-05-12 08:42:47.053+0000 INFO 90% completed > 2017-05-12 08:42:47.054+0000 INFO 100% completed > 2017-05-12 08:42:47.054+0000 INFO Migrating Legacy indexes (2/3): > 2017-05-12 08:42:47.055+0000 INFO 10% completed > 2017-05-12 08:42:47.055+0000 INFO 20% completed > 2017-05-12 08:42:47.055+0000 INFO 30% completed > 2017-05-12 08:42:47.056+0000 INFO 40% completed > 2017-05-12 08:42:47.056+0000 INFO 50% completed > 2017-05-12 08:42:47.056+0000 INFO 60% completed > 2017-05-12 08:42:47.056+0000 INFO 70% completed > 2017-05-12 08:42:47.056+0000 INFO 80% completed > 2017-05-12 08:42:47.057+0000 INFO 90% completed > 2017-05-12 08:42:47.057+0000 INFO 100% completed > 2017-05-12 08:42:47.057+0000 INFO Migrating Store files (3/3): > 2017-05-12 08:42:47.093+0000 INFO 10% completed > 2017-05-12 08:42:47.093+0000 INFO 20% completed > 2017-05-12 08:42:47.094+0000 INFO 30% completed > 2017-05-12 08:42:47.094+0000 INFO 40% completed > 2017-05-12 08:42:47.094+0000 INFO 50% completed > 2017-05-12 08:42:47.094+0000 INFO 60% completed > 2017-05-12 08:42:47.094+0000 INFO 70% completed > 2017-05-12 08:42:47.095+0000 INFO 80% completed > 2017-05-12 08:42:47.095+0000 INFO 90% completed > 2017-05-12 08:42:47.095+0000 INFO 100% completed > 2017-05-12 08:42:48.195+0000 INFO Successfully finished upgrade of > database > 2017-05-12 08:56:00.372+0000 INFO Started. > 2017-05-12 08:56:04.001+0000 INFO Mounted REST API at: /db/manage > 2017-05-12 08:56:11.852+0000 INFO Remote interface available at > http://localhost:7474/ > > > Then a couple of quick tests: > > > neo4j> match (n:Entity) with n.name as name return count(*); > > Completes ok, BUT: > > neo4j> START r=rel(*) return distinct type(r) ; > Internal error - should have used fall back to execute query, but > something went horribly wrong > > From the Neo4j logfile: > > 2017-05-12 13:37:14.457+0000 INFO ======== Neo4j 3.2.0 ======== > 2017-05-12 13:37:14.714+0000 INFO Starting... > 2017-05-12 13:37:16.054+0000 INFO Bolt enabled on 127.0.0.1:7687. > 2017-05-12 13:37:16.079+0000 INFO Initiating metrics... > 2017-05-12 13:37:25.890+0000 INFO Started. > 2017-05-12 13:37:26.201+0000 INFO Mounted REST API at: /db/manage > 2017-05-12 13:37:27.994+0000 INFO Remote interface available at > http://localhost:7474/ > 2017-05-12 13:49:19.544+0000 ERROR Client triggered an unexpected error > [UnknownError]: Internal error - should have used fall back to execute > query, but something went horribly wrong, reference > 7e442559-25d6-47ea-84c5-16b84ed9ae4e. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
