Neo4j does not start with systemd after changing cpu type on the server

General
,
1

I have a neo4j server in an ec2 instance and after changing the instance type it does not start using systemctl, has anyone experienced this?

2

@braulio.gomes

a. Neo4j version?

b. does

journalctl -u neo4j

reveal the cause for failure to start? Does it attempt to at least start and then fails some N seconds there after?

if there anything in logs/debug.log which describes the failure?

3

So Dana, the version is 2.1.6, it starts and after about 10 seconds it stops on its own

Jun 12 11:44:57 ip-10-20-169-79 systemd[1]: neo4j.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 11:44:57 ip-10-20-169-79 neo4j[2072]: ERROR: Neo4j Server not running
Jun 12 11:44:57 ip-10-20-169-79 systemd[1]: neo4j.service: Unit entered failed state.
Jun 12 11:44:57 ip-10-20-169-79 systemd[1]: neo4j.service: Failed with result 'exit-code'.
Jun 12 11:44:58 ip-10-20-169-79 systemd[1]: neo4j.service: Service hold-off time over, scheduling restart.
Jun 12 11:44:58 ip-10-20-169-79 systemd[1]: Stopped Neo4j Management Service.
Jun 12 11:44:58 ip-10-20-169-79 systemd[1]: Starting Neo4j Management Service...
Jun 12 11:44:58 ip-10-20-169-79 neo4j[2197]: Using additional JVM arguments: -server -XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties -Djava.util.logging.config.file=conf/logging.properties -Dlog4j.configu
Jun 12 11:44:58 ip-10-20-169-79 neo4j[2197]: Starting Neo4j Server...WARNING: not changing user
Jun 12 11:44:58 ip-10-20-169-79 systemd[1]: Started Neo4j Management Service.
Jun 12 11:44:59 ip-10-20-169-79 systemd[1]: neo4j.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 11:44:59 ip-10-20-169-79 neo4j[2400]: ERROR: Neo4j Server not running
Jun 12 11:44:59 ip-10-20-169-79 systemd[1]: neo4j.service: Unit entered failed state.
Jun 12 11:44:59 ip-10-20-169-79 systemd[1]: neo4j.service: Failed with result 'exit-code'.
Jun 12 11:45:00 ip-10-20-169-79 systemd[1]: neo4j.service: Service hold-off time over, scheduling restart.
Jun 12 11:45:00 ip-10-20-169-79 systemd[1]: Stopped Neo4j Management Service.

4

@braulio.gomes

the version is 2.1.6? if so thats nearly a 10+ yr old Neo4j version. I cant find the release notes but 2.3.1 Neo4j 2.3.1 - Graph Database & Analytics which came out post 2.1.6 was released in 2016

5

@braulio.gomes

also, can't explain but i would check the file permissions for the files neo4j installed. See File locations - Operations Manual for said locations etc based upon install methodology

6

Thank you very much Dana, I talked to the team and we will update the version to a more recent one so that it can be supported on another cpu