You should now be able to start your Neo4j server process in the foreground:
bin/neo4j console
This yields the following output:
Active database: graph.db
Directories in use:
home: /local/neo4j
config: /local/neo4j/conf
logs: /local/neo4j/logs
plugins: /local/neo4j/plugins
import: /local/neo4j/import
data: /local/neo4j/data
certificates: /local/neo4j/certificates
run: /local/neo4j/run
Starting Neo4j.
2017-07-09 17:10:05.300+0000 INFO ======== Neo4j 3.2.2 ========
2017-07-09 17:10:05.342+0000 INFO Starting...
2017-07-09 17:10:06.464+0000 INFO Bolt enabled on 192.168.0.100:7687.
2017-07-09 17:10:09.576+0000 INFO Started.
2017-07-09 17:10:10.982+0000 INFO Remote interface available at http://192.168.0.100:7474/
Alternatively, Neo4j can be started with the start command (instead of console) to run the process in the background. For this, current logs for the server process can be obtained by tailing the log/debug.log file:
tail -f /local/neo4j/log/debug.log
If Neo4j is running as a service, it will respond to the service start/stop commands as well:
sudo service neo4j start
Similarly, the Neo4j process can be stopped in the following ways:
- Foreground process: Ctrl + C (key combination)
- Background process: bin/neo4j stop
- Service: sudo service neo4j stop
When the Neo4j process is started, it returns output describing the on-disk locations of various server components. This information is helpful for operators to apply changes to the configuration quickly. It also clearly lists the addresses and ports that it is listening on for Bolt and HTTP connections.