-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.0.3
-
Component/s: Admin
-
Labels:None
-
ALL
I'm deploying a single node mongodb (4.0.3) via Kubernetes/helm (chart 4.6.2) and docker. I often, but do not always, see the system initialization fail because it does not find the `featureCompatibilityVersion` file in the container
it is similar to an issue reported earlier this year: https://jira.mongodb.org/browse/SERVER-33362
*Welcome to the Bitnami mongodb container*
Subscribe to project updates by watching *https://github.com/bitnami/bitnami-docker-mongodb*
Submit issues and feature requests at *https://github.com/bitnami/bitnami-docker-mongodb/issues*
nami INFO Initializing mongodb
mongodb INFO ==> Deploying MongoDB from scratch...
mongodb INFO ==> No injected configuration files found. Creating default config files...
mongodb INFO ==> Creating root user...
mongodb INFO ==> Enabling authentication...
mongodb INFO
mongodb INFO ########################################################################
mongodb INFO Installation parameters for mongodb:
mongodb INFO Root Password: **********
mongodb INFO (Passwords are not shown for security reasons)
mongodb INFO ########################################################################
mongodb INFO
nami INFO mongodb successfully initialized
INFO ==> Starting mongodb...
2018-10-25T22:33:43.072+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] MongoDB starting : pid=82 port=27017 dbpath=/opt/bitnami/mongodb/data/db 64-bit host=vantiq-ostest-mongodb-749df5cd-cmjjp
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] db version v4.0.3
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] git version: 7ea530946fa7880364d88c8d8b6026bbc9ffa48c
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.0f 25 May 2017
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] allocator: tcmalloc
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] modules: none
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] build environment:
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] distmod: debian92
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] distarch: x86_64
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] target_arch: x86_64
2018-10-25T22:33:43.077+0000 I CONTROL [initandlisten] options: \{ config: "/opt/bitnami/mongodb/conf/mongodb.conf", net: { bindIpAll: true, ipv6: true, port: 27017, unixDomainSocket: { enabled: true, pathPrefix: "/opt/bitnami/mongodb/tmp" } }, processManagement: \{ fork: false, pidFilePath: "/opt/bitnami/mongodb/tmp/mongodb.pid" }, security: \{ authorization: "enabled" }, setParameter: \{ enableLocalhostAuthBypass: "false" }, storage: \{ dbPath: "/opt/bitnami/mongodb/data/db", journal: { enabled: true } }, systemLog: \{ destination: "file", logAppend: true, logRotate: "reopen", path: true } }
2018-10-25T22:33:43.078+0000 I STORAGE [initandlisten] Detected data files in /opt/bitnami/mongodb/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-10-25T22:33:43.078+0000 I STORAGE [initandlisten]
2018-10-25T22:33:43.078+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2018-10-25T22:33:43.078+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
2018-10-25T22:33:43.078+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2018-10-25T22:33:44.171+0000 I STORAGE [initandlisten] WiredTiger message [1540506824:171851][82:0x7f441ac3b9c0], txn-recover: Main recovery loop: starting at 1/9088
2018-10-25T22:33:44.258+0000 I STORAGE [initandlisten] WiredTiger message [1540506824:258481][82:0x7f441ac3b9c0], txn-recover: Recovering log 1 through 2
2018-10-25T22:33:44.384+0000 I STORAGE [initandlisten] WiredTiger message [1540506824:384339][82:0x7f441ac3b9c0], txn-recover: Recovering log 2 through 2
2018-10-25T22:33:44.421+0000 I STORAGE [initandlisten] WiredTiger message [1540506824:421322][82:0x7f441ac3b9c0], txn-recover: Set global recovery timestamp: 0
2018-10-25T22:33:45.370+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2018-10-25T22:33:46.297+0000 W CONTROL [initandlisten]
2018-10-25T22:33:46.297+0000 W CONTROL [initandlisten]
2018-10-25T22:33:46.297+0000 I CONTROL [initandlisten]
2018-10-25T22:33:46.801+0000 F STORAGE [initandlisten] Unable to start up mongod due to missing featureCompatibilityVersion document.
2018-10-25T22:33:46.801+0000 F STORAGE [initandlisten] Please run with --repair to restore the document.
2018-10-25T22:33:46.802+0000 F - [initandlisten] Fatal Assertion 40652 at src/mongo/db/repair_database_and_check_version.cpp 579
2018-10-25T22:33:46.802+0000 F - [initandlisten]
***aborting after fassert() failure
ERROR ==> error: mongod does not appear to be running -- perhaps it had an error?
It seems impossible that a freshly created install would need repair. further, when i run the deploy in isolation (nothing else deploying at the same time) it works reliably.