Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with CentOS 7's Systemd #53

Open
cobrin opened this issue Sep 9, 2019 · 0 comments
Open

Incompatibility with CentOS 7's Systemd #53

cobrin opened this issue Sep 9, 2019 · 0 comments

Comments

@cobrin
Copy link

cobrin commented Sep 9, 2019

Just noticed a couple of possible issues, or error in my installation. Or just observations

Firstly I did a standard install of Neo4j on CentOS 7, it creates a Systemd startup as user "neo4j"

I then wanted to install ineo, so I thought I'd install that as "neo4j"

  1. Am I supposed to disable systemd start up and then manually startup with ineo?

  2. The ineo install script edits .bashrc but that doesn't take effect if I "su - neo4j", but does if I rename it to .bash_profile

  3. ineo start script doesn't use systemd startup scripts or environment variable settings

[17:24|neo4j@gbjhvice108:~]$ ineo start my_db

  start 'my_db'
  Active database: graph.db
Directories in use:
  home:         /var/lib/neo4j/.ineo/instances/my_db
  config:       /var/lib/neo4j/.ineo/instances/my_db/conf
  logs:         /var/lib/neo4j/.ineo/instances/my_db/logs
  plugins:      /var/lib/neo4j/.ineo/instances/my_db/plugins
  import:       /var/lib/neo4j/.ineo/instances/my_db/import
  data:         /var/lib/neo4j/.ineo/instances/my_db/data
  certificates: /var/lib/neo4j/.ineo/instances/my_db/certificates
  run:          /var/lib/neo4j/.ineo/instances/my_db/run
Starting Neo4j.
WARNING: Max 1024 open files allowed, minimum of 40000 recommended. See the Neo4j manual.
Started neo4j (pid 11443). It is available at http://0.0.0.0:7474/
There may be a short delay until the server is ready.
See /var/lib/neo4j/.ineo/instances/my_db/logs/neo4j.log for current status.

However the normal systemd startup works correctly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant