Cann't start Neo4j Enterprise Casual Cluster from AWS Marketplace

Neo4j Graph Platform Installation
1

hello, guys.
couldn’t start neo4j enterprise casual cluster from the aws marketplace (AWS Marketplace: Neo4j Enterprise Causal Cluster).
I tried 2 times, both times CloudFormation service ends up with error

The following resource(s) failed to create: [WaitOnPasswordReset]. . Rollback requested by user.

2019-01-23_13-06-35
2019-01-23_13-06-352436×664 193 KB

Can somebody help with this issue?

2

Hi @mikhail I believe we solved this issue together via the public slack. The issue is that sometimes AWS creates the infrastructure too slowly, and the stack misses a timeout. I believe you were able to create the stack successfully simply by retrying.

Sometimes AWS provisions slowly, unfortunately.

1 Like
3

Hello,

I have this issue and I retried several times but always failing, any idea how to fix this?

Thanks

4

Please follow up with what version you're launching, how you're launching it, and what error you're seeing. It's been a while since this thread, and a number of things have changed, so updated context is important.

5

Hi David,

Thanks for follow up

6

Hey,

I have more details, I logged in the EC2 instances and checked the logs:

so the script failed due to this:

/var/lib/cloud/instance/scripts/part-001: line 64: /usr/local/bin/cfn-signal: No such file or directory

but the main issue is from the EC2 not possible to connect to ec2.eu-west-1.amazonaws.com

/var/log/cloud-init-output.log:196:HTTPSConnectionPool(host='ec2.eu-west-1.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7ffb81796e10>, 'Connection to ec2.eu-west-1.amazonaws.com timed out. (connect timeout=60)'))
/var/log/cloud-init-output.log:198:HTTPSConnectionPool(host='ec2.eu-west-1.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fcf82daae10>, 'Connection to ec2.eu-west-1.amazonaws.com timed out. (connect timeout=60)'))
/var/log/cloud-init-output.log:213:HTTPSConnectionPool(host='ec2.eu-west-1.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7efcb9590e48>, 'Connection to ec2.eu-west-1.amazonaws.com timed out. (connect timeout=60)'))
/var/log/cloud-init-output.log:255:tar: Error is not recoverable: exiting now
/var/log/cloud-init-output.log:257:error: Couldn't find a setup script in /aws-cfn-bootstrap-latest
/var/log/cloud-init.log:859:2020-03-13 14:11:51,557 - main.py[DEBUG]: Ran 15 modules with 0 failures
/var/log/cloud-init.log:984:2020-03-13 14:12:06,011 - main.py[DEBUG]: Ran 14 modules with 0 failures
/var/log/cloud-init.log:1109:2020-03-13 14:12:06,754 - main.py[DEBUG]: Ran 20 modules with 0 failures
/var/log/cloud-init.log:1992:2020-03-30 07:56:00,808 - main.py[DEBUG]: Ran 15 modules with 0 failures
7

I think I found the issue, the problem with the route set in the cloudformation template which allow the whitelisted IP only to use the internet gateway which for me doesn't make sense.

        "Route": {
            "Type": "AWS::EC2::Route", 
            "DependsOn": "AttachGateway", 
            "Properties": {
                "RouteTableId": {
                    "Ref": "RouteTable"
                }, 
                "DestinationCidrBlock": {
                    "Ref": "NetworkWhitelist"    <-------------- 
                }, 
                "GatewayId": {
                    "Ref": "InternetGateway"
                }
            }
        }
8

Can you say more about why that bit doesn't make sense?

9

Hello @medsaeed.88 , this was a mistake made during packaging, I fixed it now and made sure that it works like it should.
Please try to get the new fixed 3.5.16 cft template from the s3 bucket and run it again.
Thanks.

1 Like
10

I am also having this issue Launching the Cloud Formation Template with 4.0.4

11

How do you retry a failed template. Everytime I retry it says the stack already exists

12

you need to either choose a different name to deploy under, or delete your failed stack using cloudformation to get rid of the old one which didn't form properly before redeploying under the same name

13

Yep, I had figured it out, not very intuitive on Amazon's part how that works. I am still having the other issue, but there is another thread that you answered where we are talking about that issue.

Thanks for your help,

Mike

1 Like