Neo4J on ami-03de3ac0f7ecf9ece cannot start

Hello,

I set up my own AWS instance using the ami-03de3ac0f7ecf9ece AMI. It's a t2.micro in the eu-central-1 region. The machine starts and i can SSH into it.

However, neo4j fails to start. The neo4j logs are empty, but checking /var/log/syslog shows the following

eb 11 05:23:30 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:30 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:32 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:32 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:33 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:33 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:34 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:34 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:35 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:35 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:37 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:37 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:38 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:38 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:40 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:40 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:41 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:41 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: Tue Feb 11 05:23:42 UTC 2020 Waiting for neo4j to come up
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: Exception in thread "main" java.lang.IllegalArgumentException: Error evaluating value for setting 'dbms.connector.bolt.listen_address'. Configured socket address must be in the format "hostname:port". "" does not conform to this format
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.Config.evaluateSetting(Config.java:552)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.Config.evaluateSettingValues(Config.java:384)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.Config.<init>(Config.java:357)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.Config$Builder.build(Config.java:260)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:103)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:89)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.server.CommunityEntryPoint.main(CommunityEntryPoint.java:35)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: Caused by: java.lang.IllegalArgumentException: Configured socket address must be in the format "hostname:port". "" does not conform to this format
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.helpers.SocketAddressParser.socketAddress(SocketAddressParser.java:90)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.SettingValueParsers$12.parse(SettingValueParsers.java:401)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.SettingValueParsers$12.parse(SettingValueParsers.java:397)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.SettingImpl.parse(SettingImpl.java:85)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011at org.neo4j.configuration.Config.evaluateSetting(Config.java:537)
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: #011... 6 more
Feb 11 05:23:42 ip-172-31-37-192 pre-neo4j.sh[5754]: 2020-02-11 05:23:42.945+0000 INFO [o.n.s.CommunityBootstrapper] Neo4j Server shutdown initiated by request
Feb 11 05:23:43 ip-172-31-37-192 systemd[1]: neo4j.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 05:23:43 ip-172-31-37-192 systemd[1]: neo4j.service: Unit entered failed state.
Feb 11 05:23:43 ip-172-31-37-192 systemd[1]: neo4j.service: Failed with result 'exit-code'.
Feb 11 05:23:43 ip-172-31-37-192 systemd[1]: neo4j.service: Service hold-off time over, scheduling restart.
Feb 11 05:23:43 ip-172-31-37-192 systemd[1]: Stopped Neo4j Graph Database.

Can someone let me know if they used the same AMI and if it worked for them? Or, alternatively, how to fix this issue?

Thank you,
Silviu

I'm not seeing this one under our ownership, it might not be ours. Can you confirm the AMI's owner number?

Hi @andrew.bowman,

Thanks for taking a look at my issue!

You can see the AMI here: https://eu-central-1.console.aws.amazon.com/ec2/v2/home?region=eu-central-1#Images:visibility=public-images;imageId=ami-03de3ac0f7ecf9ece;sort=name

The owner is 385155106615, the same one mentioned here: https://neo4j.com/developer/neo4j-cloud-aws-ec2-ami/

Cheers,
Silviu

Ah, okay I think I see what's going on.

The 4.0 AMIs should not have been made publicly available. These are not in a good state to use right now, they're still being built out, I'm checking if we can disable public exposure for these.

Any ideas when thell become available?

I believe we're aiming for a release within the next week or two.

Thanks, @andrew.bowman! Looking forward to the release.