Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[bitnami/mongodb-sharded] Unrecognized option: storage.journal.enabled when starting mongodb #50109

Closed
muyukha opened this issue Sep 27, 2023 · 7 comments · May be fixed by #65826
Closed

[bitnami/mongodb-sharded] Unrecognized option: storage.journal.enabled when starting mongodb #50109

muyukha opened this issue Sep 27, 2023 · 7 comments · May be fixed by #65826
Assignees
@rafariossaa
Labels
mongodb-sharded solved stale 15 days without activity tech-issues The user has a technical issue about an application

Comments

@muyukha
Copy link

muyukha commented Sep 27, 2023 •
edited by javsalgar

Name and Version

mongodb-sharded-6.6.7

What architecture are you using?

amd64

What steps will reproduce the bug?

I deployed mongodb on the GKE cluster. It has been running well but yesterday all pods in the statefulset went down with an error Unrecognized option: storage.journal.enabled.

I deployed via helm.
Helm repository https://charts.bitnami.com/bitnami

What is the expected behavior?

No response

What do you see instead?

 05:54:06.20 INFO  ==> Setting node as primary
mongodb 05:54:06.23 
mongodb 05:54:06.24 Welcome to the Bitnami mongodb-sharded container
mongodb 05:54:06.24 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 05:54:06.24 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 05:54:06.24 
mongodb 05:54:06.24 INFO  ==> ** Starting MongoDB Sharded setup **
mongodb 05:54:06.27 INFO  ==> Validating settings in MONGODB_* env vars...
mongodb 05:54:06.33 INFO  ==> Initializing MongoDB Sharded...
mongodb 05:54:06.37 INFO  ==> Writing keyfile for replica set authentication...
mongodb 05:54:06.39 INFO  ==> Enabling authentication...
mongodb 05:54:06.39 INFO  ==> Deploying MongoDB Sharded with persisted data...

mongodb 05:54:06.43 INFO  ==> ** MongoDB Sharded setup finished! **
mongodb 05:54:06.47 INFO  ==> ** Starting MongoDB **
Unrecognized option: storage.journal.enabled
try '/opt/bitnami/mongodb/bin/mongod --help' for more information

Additional information

No response
@muyukha muyukha added the tech-issues The user has a technical issue about an application label Sep 27, 2023
@bitnami-bot bitnami-bot added this to Triage in Support Sep 27, 2023
@github-actions github-actions bot added the triage Triage is needed label Sep 27, 2023
@muyukha
Copy link
Author

muyukha commented Sep 27, 2023 •
edited

I got the issue.
I think the latest image tag has a bug.
I updated the image tag to 6.0.10-debian-11-r8 in the helm values and everything is running fine

@javsalgar javsalgar changed the title Unrecognized option: storage.journal.enabled when starting mongodb [bitnami/mongodb-sharded] Unrecognized option: storage.journal.enabled when starting mongodb Sep 27, 2023
@javsalgar
Copy link
Contributor

Hi!

Did you set any custom values or configuration?

@github-actions github-actions bot moved this from Triage to Pending in Support Sep 27, 2023
@muyukha
Copy link
Author

muyukha commented Sep 27, 2023

Yes. I changed the image tag from latest to 6.0.10-debian-11-r8 in the helm values

@bitnami-bot bitnami-bot moved this from Pending to Triage in Support Sep 27, 2023
@javsalgar javsalgar moved this from Triage to In progress in Support Sep 28, 2023
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Sep 28, 2023
@bitnami-bot bitnami-bot assigned rafariossaa and unassigned javsalgar Sep 28, 2023
@rafariossaa
Copy link
Contributor

rafariossaa commented Oct 2, 2023 •
edited

Hi,
Could you indicate which chart version are you using ?
Currently the latest tag is pointing to version 7.x. If you look for 5ccace3b8441 (the current latest digest) in here, you will find it points to 7.0.2-debian-11-r0.

@github-actions github-actions bot moved this from In progress to Pending in Support Oct 2, 2023
@github-actions
Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Oct 18, 2023
@github-actions
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 23, 2023
@bitnami-bot bitnami-bot moved this from Pending to Solved in Support Oct 23, 2023
@github-actions github-actions bot removed this from Solved in Support Oct 25, 2023
@kidstell
Copy link

kidstell commented Dec 17, 2023 •
edited

I recently downloaded version 7.0.4
after reading this article below, i decided to comment out the journal part of my mongod.conf, now the start-up is fine.
https://www.mongodb.com/docs/manual/reference/program/mongod/#options

The journal would always be enabled, perhaps I don't need to enable it myself. Nonetheless, I hope that if this is the case, an official response to confirm this can close this issue.

image

@Xyvran Xyvran mentioned this issue May 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafariossaa rafariossaa

Labels
mongodb-sharded solved stale 15 days without activity tech-issues The user has a technical issue about an application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[bitnami/mongodb] journal doesnt work anymore since 6.1 Xyvran/bitnami-containers
5 participants
@javsalgar @rafariossaa @bitnami-bot @kidstell @muyukha