我有一个不知道如何解决的Bolt身份验证问题。我已将备份从在线提供商还原到本地计算机。我可以启动浏览器并运行“ CALL db.schema
”,然后查询返回。但是,当我尝试仅选择一个样本数据集时,我在日志中看到了这一点,查询将永远不会返回。
2018-06-25 14:39:23.778+0000 ERROR Unexpected error detected in bolt session 'ace2d3fffe92e75d-0005b714-00000004-4c1990029792d052-f94315d8'. The client is unauthorized due to authentication failure.
org.neo4j.bolt.v1.runtime.BoltConnectionFatality: The client is unauthorized due to authentication failure.
at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:742)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.handleFailure(BoltStateMachine.java:728)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.access$500(BoltStateMachine.java:62)
at org.neo4j.bolt.v1.runtime.BoltStateMachine$State$1.init(BoltStateMachine.java:435)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.init(BoltStateMachine.java:145)
at org.neo4j.bolt.v1.messaging.BoltMessageRouter.lambda$onInit$0(BoltMessageRouter.java:70)
at org.neo4j.bolt.runtime.MetricsReportingBoltConnection.lambda$enqueue$0(MetricsReportingBoltConnection.java:69)
at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:195)
at org.neo4j.bolt.runtime.MetricsReportingBoltConnection.processNextBatch(MetricsReportingBoltConnection.java:87)
at org.neo4j.bolt.runtime.DefaultBoltConnection.processNextBatch(DefaultBoltConnection.java:143)
at org.neo4j.bolt.runtime.ExecutorBoltScheduler.executeBatch(ExecutorBoltScheduler.java:170)
at org.neo4j.bolt.runtime.ExecutorBoltScheduler.lambda$scheduleBatchOrHandleError$2(ExecutorBoltScheduler.java:153)
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
在我的配置文件中,我可以关闭安全性:dbms.security.auth_enabled=false
,然后一切正常。但我想了解为什么/如何收到此错误,因此不必这样做。在桌面的“管理”选项卡中,我尝试过更改密码,它说成功了,但是错误仍然存在?
答案 0 :(得分:1)
恢复为相同版本可以解决问题。要拥有足够的知识,必须将备份还原到相同的版本。或至少将v3.3.5恢复到3.4会出现此问题。