learninglocker icon indicating copy to clipboard operation
learninglocker copied to clipboard

Fresh install AMI not creating user credentials

Open dkjensen opened this issue 5 years ago • 0 comments

What version were you using?

4.10.0 AMI Open source

What steps can we follow to reproduce the behaviour?

Deploy new EC2 instance using Learning Locker 4.10.0 from HT2 Labs - ami-002ad1007ce3910f8

What is the actual behaviour?

I am able to view the login screen, but no credentials file is created under /home/ubuntu/ll_credentials.txt

Is there any additional information that will help us replicate/understand the problem?

Tried manually creating a user using the CLI but was given the following error:

Unhandled rejection MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
    at Pool.<anonymous> (/usr/local/learninglocker/releases/ll-20190913-ac88386491c3a71c1cede7da23a4281a4b91a428/webapp/node_modules/mongodb-core/lib/topologies/server.js:431:11)
    at emitOne (events.js:116:13)
    at Pool.emit (events.js:211:7)
    at connect (/usr/local/learninglocker/releases/ll-20190913-ac88386491c3a71c1cede7da23a4281a4b91a428/webapp/node_modules/mongodb-core/lib/connection/pool.js:557:14)
    at makeConnection (/usr/local/learninglocker/releases/ll-20190913-ac88386491c3a71c1cede7da23a4281a4b91a428/webapp/node_modules/mongodb-core/lib/connection/connect.js:39:11)
    at callback (/usr/local/learninglocker/releases/ll-20190913-ac88386491c3a71c1cede7da23a4281a4b91a428/webapp/node_modules/mongodb-core/lib/connection/connect.js:261:5)
    at Socket.err (/usr/local/learninglocker/releases/ll-20190913-ac88386491c3a71c1cede7da23a4281a4b91a428/webapp/node_modules/mongodb-core/lib/connection/connect.js:286:7)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)

dkjensen avatar Mar 23 '20 18:03 dkjensen