#Kubernetes migration guide broken? (mongodb authentication issues...)

1 messages · Page 1 of 1 (latest)

dusk anvil
#

I'm following migration guide for k8s (https://docs.appsmith.com/getting-started/setup/installation-guides/kubernetes/migrate-k8s, is this guide broken?) but getting stuck after step 4 Install Helm chart, it seems like mongodb does not get setup correctly. I've made sure that the mongodb host config (APPSMITH_MONGODB_URI) is set as localhost and root user and password is setup according to the guide (APPSMITH_MONGODB_USER, APPSMITH_MONGODB_PASSWORD).

This is the start of the logs from the pod:

Initialize .env file Load environment configuration Checking environment configuration Checking APPSMITH_MONGODB_URI Detected local MongoDB Initializing local database '/appsmith-stacks/data/mongodb/key' -> '/mongodb-key' Checking initialized database Clearing symlinks in /etc/ssl/certs... done. Updating certificates in /etc/ssl/certs... rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL 127 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d...

Further down I see following error:

022-10-11 14:27:23,955 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs) rts stdout | Error watching MongoDB MongoError: Authentication failed. rts stdout | at MessageStream.messageHandler ...

#

Can also add that surfin to the web endpoint show's a stylized web error page, probably because of the issue with the mongodb configuration has not been successfully been setup.

dreamy tokenBOT
#

Hey @dusk anvil! Thanks for reaching out to us. I've asked our devOps
team to take a look at your query. Please give them some time to get back to
you.

dusk anvil
#

Ignore this issue. Problem was that I forgot to delete persisted volumes in between trying out different configurations.