ci-info | Get details about the current Continuous Integration | Continous Integration library

I modified the code to work. I identified that the main issue is mongodb-clients which causes failures of monogdb. Also your command db.createUser is invalid and will lead to failure as well. I did not fix that, as its not related to your issue about connection refused. You can make new question why your db.createUser is incorrect (I don't know how to fix that, its mongodb specific).

It looks like there is a mismatch between the environments you use. Try the following:

1. Remove sharp completely from your app.

Ok, shortly after posting we figured it out. Seems like a mount point has changed (I expect due to a linux kernel update) and we have not used the nofail option in /etc/fstab as described in the aws knowledge center, this caused the server to hang at boot.

Going forward we will also ensure we use UUID mounting so we are independent on the device naming in /dev/.

Your app is in C:\ServiceNow\foggydev\agent\scripts\NodeJSAWSConnector\APINetworks.js

node_modules are in: C:\Program Files\nodejs\node_modules\npm\node_modules

Seems like You've installed aws-api-gateway-client globally (since You're saying that node_modules folder is in different place)

Steps to check and solve:

1) check package.json file if it exists in dependencies,

2) make sure in Your test server aws-api-gateway-client exists in node_modules folder,

3) do npm i --save aws-api-gateway-client to install it in node_modules folder relative to Your project, which will also add that module to dependencies in package.json

4) deploy to test server again with updated packge.json

Looks to be a problem with ReactBootstrap assuming propTypes is defined in prod.

You can update your Rails babel.config.js file to ignore the babel-plugin-transform-react-remove-prop-types which is effectively what's causing the error.

You could, for example, comment the lines out, leaving a note as to why it's commented out. E.g.