Cannot redeploy Mongo DB container service

Questions and Answers Deployment
1

Hi,

I created a post a few weeks ago about issue with deployments Issue deploying existing services - #4 but I cannot understand the issue with the resources.

I tried to increase resources for the service
https://console.qovery.com/organization/b3e8ebc3-4097-4673-9aed-7ff14ddf1f25/project/85b266e8-c56c-4c35-8fb9-1c7f4c65264c/environment/f0b8dc95-38ea-4f1f-91f7-a9e1c81a666a/logs/96054054-c67b-4607-b3c9-d2564401e95d/deployment-logs/f0b8dc95-38ea-4f1f-91f7-a9e1c81a666a-9 but that didn’t fix the issue, and I cannot deploy the server. The cluster has enough resources, but I’m unsure about storage as it’s unclear where I can see the info on AWS or Qovery.

What exactly needs to be done to fix the deployment? I tried using Loki and Cloudwatch to check the log for errors but couldn’t find the deployment logs. It would be helpful to understand where to look.

Thanks,
Simon

2

Hello @simofacc,

I checked with the team and I can give you more logs on your error:

message: chart mongodb-z96054054: Error: UPGRADE FAILED: execution error at (mongodb/templates/secrets.yaml:43:17):
message: chart mongodb-z96054054: PASSWORDS ERROR: The secret "mongodbz96054054" does not contain the key "mongodb-passwords"

I don’t think this is a resource problem, it looks more like a missing secret in your configuration.

Please let me know if this is helpful,

Regards,
Charles-Edouar

3

Hi,

The error is unclear because I am trying to redeploy the MongoDB container. The service or project does not have any mongodb-passwords variable.

The value is built-in QOVERY_MONGODB_Z96054054_PASSWORD and I cannot try to recreate it.
Screenshot 2024-11-14 at 10.59.31

Simon

4

Hello @simofacc,

This is the same problem you faced in the previous thread.

Your MongoDB was stopped for too long, and we updated the helm charts. When you tried to redeploy your Mongo, the Helm chart was not valid anymore and you faced an error.

We fixed the error, so your MongoDB is now starting without error.

But you are facing another problem, you need to increase the resources for your MongoDB pods. You also need to do this for your Production Mongo.
cf:

image
image1806×462 49.6 KB

To do this, you go to your pod, open the settings, and try new values for CPU and RAM.

image
image1974×1316 200 KB

You can start by doubling the RAM. If your DB keeps getting killed, you can try doubling the RAM again.

I hope this is helpful,

Regards,
Charles-Edouard

5

@simofacc ,

We also noticed you have other Mongo which have been stopped for a very long time,

Do you plan to restart them?
If yes, you will face the same error. We can fix them for you, but we need to restart the service.

Please let me know how you want to proceed.

Regards,
Charles-Edouard

6

This topic was automatically closed after 22 hours. New replies are no longer allowed.