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

Already on GitHub? Sign in to your account

Server startup fails in a bad way if lsof is not in path #139

Closed
lassewesth opened this Issue Nov 12, 2012 · 2 comments

Comments

Projects
None yet
4 participants
Owner

lassewesth commented Nov 12, 2012

@gorbachev: 'Using 1.6.1 on Unix.

If lsof is not in path, the server startup fails and leaves the database in a dirty state.

$ bin/neo4j start
WARNING: Detected a limit of 16384 for maximum open files, while a minimum value of 40000 is recommended.
WARNING: Problems with the operation of the server may occur. Please refer to the Neo4j manual regarding lifting this limitation.
Starting Neo4j Server...WARNING: not changing user
process [10861]... waiting for server to be ready.bin/neo4j: line 213: lsof: command not found
.bin/neo4j: line 213: lsof: command not found
.bin/neo4j: line 213: lsof: command not found
.bin/neo4j: line 213: lsof: command not found
[several more of the same errors omitted]
.bin/neo4j: line 213: lsof: command not found
. BAD.
another server-process is running with []

The script should check that lsof is in path before proceeding.'

Owner

lassewesth commented Nov 12, 2012


values:

@davidegrohmann davidegrohmann removed the server label Oct 22, 2015

@jakewins jakewins added the operability label Dec 5, 2015

@benbc benbc self-assigned this Dec 18, 2015

@srbaker srbaker closed this in #6158 Jan 7, 2016

Contributor

benbc commented Jan 7, 2016

Our scripts no longer use lsof.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment