Hi GB! We’ve been running GB on K8s and recently, we’ve started getting errors along the lines of `E...
c

Cheng Dai

over 2 years ago
Hi GB! We’ve been running GB on K8s and recently, we’ve started getting errors along the lines of
Error connecting to the GrowthBook API at <https://api.growthbook>.[...].com
with the
Failed to fetch
error. When we try to manually request the API, we get the following
❯ curl <https://api.growthbook>.[...].com
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
Looking at the logs, it seems like the main application pod encounters the following error:
yarn run v1.22.19
$ wsrun -p '*-end' -m start
back-end
 | $ node dist/server.js
front-end
 | $ next start
 | ready - started server on 0.0.0.0:3000, url: <http://localhost:3000>
back-end
 |   Back-end is running at <http://localhost:3100> in production mode
 |   Press CTRL-C to stop
 |
 | MongooseServerSelectionError: connection timed out
 |     at NativeConnection.Connection.openUri (/usr/local/src/app/node_modules/mongoose/lib/connection.js:847:32)
 |     at /usr/local/src/app/node_modules/mongoose/lib/index.js:351:10
 |     at /usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:32:5
 |     at Promise._execute (/usr/local/src/app/node_modules/bluebird/js/release/debuggability.js:384:9)
 |     at Promise._resolveFromExecutor (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:518:18)
 |     at new Promise (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:103:10)
 |     at promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:31:10)
 |     at Mongoose._promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/index.js:1149:10)
 |     at Mongoose.connect (/usr/local/src/app/node_modules/mongoose/lib/index.js:350:20)
 |     at /usr/local/src/app/packages/back-end/dist/init/mongo.js:26:41
 |     at Generator.next (<anonymous>)
 |     at /usr/local/src/app/packages/back-end/dist/init/mongo.js:8:71
 |     at new Promise (<anonymous>)
 |     at __awaiter (/usr/local/src/app/packages/back-end/dist/init/mongo.js:4:12)
 |     at exports.default (/usr/local/src/app/packages/back-end/dist/init/mongo.js:19:25)
 |     at /usr/local/src/app/packages/back-end/dist/app.js:106:43
 |     at Generator.next (<anonymous>)
 |     at /usr/local/src/app/packages/back-end/dist/app.js:31:71
 |     at new Promise (<anonymous>)
 |     at __awaiter (/usr/local/src/app/packages/back-end/dist/app.js:27:12)
 |     at /usr/local/src/app/packages/back-end/dist/app.js:105:34
 |     at /usr/local/src/app/packages/back-end/dist/app.js:108:16 {
 |   reason: TopologyDescription {
 |     type: 'Single',
 |     setName: null,
 |     maxSetVersion: null,
 |     maxElectionId: null,
 |     servers: Map(1) { 'growthbook-mongodb:27017' => [ServerDescription] },
 |     stale: false,
 |     compatible: true,
 |     compatibilityError: null,
 |     logicalSessionTimeoutMinutes: null,
 |     heartbeatFrequencyMS: 10000,
 |     localThresholdMS: 15,
 |     commonWireVersion: null
 |   }
 | }
 | Error: MongoDB connection error.
 |     at /usr/local/src/app/packages/back-end/dist/init/mongo.js:34:15
 |     at Generator.throw (<anonymous>)
 |     at rejected (/usr/local/src/app/packages/back-end/dist/init/mongo.js:6:65)
 | error Command failed with exit code 1.
 | info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
 | `yarn start` failed with exit code 1
The fix that has worked thus far is restarting the pod hosting the frontend/backend. However, we were wondering if there is a way for the system to failover. Even though ``yarn start` failed with exit code 1` , the application pod was deemed
Running
on K8s. Since both back-end and front-end are packaged into one container, what is the best way to perform a liveliness and readiness probe on the application so that it checks both the front-end and back-end system? Many thanks in advance!
Hi All, I tried to connect growthbook app in the documentdb aws, but I received this error below: |...
a

Andreia Feitosa

about 2 years ago
Hi All, I tried to connect growthbook app in the documentdb aws, but I received this error below: | {"level":50,"time":1682458961139,"pid":59,"hostname":"ip-xxxx.ec2.internal", "err":{"type":"MongooseServerSelectionError", "message":"unable to get local issuer certificate","stack":"MongooseServerSelectionError: unable to get local issuer certificate\n at NativeConnection.Connection.openUri (/usr/local/src/app/node_modules/mongoose/lib/connection.js84732)\n at /usr/local/src/app/node_modules/mongoose/lib/index.js35110\n at /usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js325\n at Promise._execute (/usr/local/src/app/node_modules/bluebird/js/release/debuggability.js3849)\n at Promise._resolveFromExecutor (/usr/local/src/app/node_modules/bluebird/js/release/promise.js51818)\n at new Promise (/usr/local/src/app/node_modules/bluebird/js/release/promise.js10310)\n at promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js3110)\n at Mongoose._promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/index.js114910)\n at Mongoose.connect (/usr/local/src/app/node_modules/mongoose/lib/index.js35020)\n at /usr/local/src/app/packages/back-end/dist/init/mongo.js2741\n at Generator.next (<anonymous>)\n at /usr/local/src/app/packages/back-end/dist/init/mongo.js871\n at new Promise (<anonymous>)\n at __awaiter (/usr/local/src/app/packages/back-end/dist/init/mongo.js412)\n at exports.default (/usr/local/src/app/packages/back-end/dist/init/mongo.js2025)\n at /usr/local/src/app/packages/back-end/dist/init/index.js2543\n at Generator.next (<anonymous>)\n at /usr/local/src/app/packages/back-end/dist/init/index.js871\n at new Promise (<anonymous>)\n at __awaiter (/usr/local/src/app/packages/back-end/dist/init/index.js412)\n at /usr/local/src/app/packages/back-end/dist/init/index.js2434\n at /usr/local/src/app/packages/back-end/dist/init/index.js2816","reason":{"type":"ReplicaSetNoPrimary","setName":null,"maxSetVersion":null,"maxElectionId":null,"servers":{},"stale":false,"compatible":true,"compatibilityError":null,"logicalSessionTimeoutMinutes":null,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"commonWireVersion":null}},"msg":"Failed to connect to MongoDB"} I run the application on ecs.... Do you have any example how I make this connection with the documentdb aws - mongo? Thanks