Question

我一直在尝试在容器中使用neo4j社区并且遇到错误。我认为这可能更多是docker使用问题，而不是neo4j的使用。

我已经从https://github.com/neo4j/docker-neo4j-publish 2.3.9,3.3.3,3.3.4和3.3.5构建了一个容器映像（只有差异是更高版本中的一些新端口）。我甚至从dockerhub.com拉出了原生的3.3.3

mkdir /tmp/data
chmod 777 /tmp/data
docker run --detach=true --name=neo4j --publish=7474:7474 --publish=7687:7687 --publish=7473:7473 --volume=/tmp/data:/data neo4j:3.3.3
docker exec -it neo4j find / -name '*.log'

虽然它似乎与

一起使用

neo4j> CREATE (n);
0 rows available after 50 ms, consumed after another 0 ms
Added 1 nodes
neo4j> CREATE (m),(o);
0 rows available after 15 ms, consumed after another 0 ms
Added 2 nodes
neo4j> MATCH (n) RETURN n;
+----+
| n  |
+----+
| () |
| () |
| () |
+----+

3 rows available after 21 ms, consumed after another 8 ms

我实际上遇到这样的错误：

docker exec -it neo4j neo4j status
Neo4j is not running

现在这个看起来我错误地试图在正在运行的实例上启动另一个Neo4j实例：

 docker exec -it neo4j neo4j console
Active database: graph.db
Directories in use:
  home:         /var/lib/neo4j
  config:       /var/lib/neo4j/conf
  logs:         /var/lib/neo4j/logs
  plugins:      /var/lib/neo4j/plugins
  import:       /var/lib/neo4j/import
  data:         /var/lib/neo4j/data
  certificates: /var/lib/neo4j/certificates
  run:          /var/lib/neo4j/run
Starting Neo4j.
2018-04-15 06:30:13.119+0000 WARN  Unknown config option: causal_clustering.discovery_listen_address
2018-04-15 06:30:13.123+0000 WARN  Unknown config option: causal_clustering.raft_advertised_address
2018-04-15 06:30:13.123+0000 WARN  Unknown config option: causal_clustering.raft_listen_address
2018-04-15 06:30:13.123+0000 WARN  Unknown config option: ha.host.coordination
2018-04-15 06:30:13.124+0000 WARN  Unknown config option: causal_clustering.transaction_advertised_address
2018-04-15 06:30:13.124+0000 WARN  Unknown config option: causal_clustering.discovery_advertised_address
2018-04-15 06:30:13.124+0000 WARN  Unknown config option: ha.host.data
2018-04-15 06:30:13.124+0000 WARN  Unknown config option: causal_clustering.transaction_listen_address
2018-04-15 06:30:13.146+0000 INFO  ======== Neo4j 3.3.3 ========
2018-04-15 06:30:13.186+0000 INFO  Starting...
2018-04-15 06:30:13.997+0000 INFO  Bolt enabled on 0.0.0.0:7687.
2018-04-15 06:30:14.094+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@44a59da3' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /var/lib/neo4j/data/databases/graph.db/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@44a59da3' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /var/lib/neo4j/data/databases/graph.db/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)".
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@44a59da3' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /var/lib/neo4j/data/databases/graph.db/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)".

有没有人有Neo4j的docker实现经验？这是一个单线程问题，这意味着我需要以不同于容器的方式调用CLI工具吗？

Answer 1

neo4j status命令仅在您使用neo4j start启动neo4j时才有效。 Start创建一个neo4j.pid文件，状态用于查看neo4j是否正在运行。从docker开始使用console选项而不是start选项。这不会创建PID文件，因此状态不起作用。但这几乎不重要，因为neo4j只是运行的唯一过程;如果neo4j死了，容器将退出。如果docker ps -a表示容器已启动，则neo4j已启动。

从docker容器显示启动neo4j＆＃34; Neo4j没有运行＆＃34;

1 个答案: