[[Support] jasonbean - MongoDB]

On 8/27/2022 at 12:23 PM, danktankk said:

A quick fix until setting the featureCompatibilityVersion higher, is to add `:5` to the tag and it will work as expected.  Credit goes to @HalienElf.

 

That worked perfectly, thanks.

 

For the benefit of anyone else with the same issue, changing version to "5" as demonstrated by @danktankk allowed mongoDB to run, and therefore get terminal access.

 

from there, to access the database I ran:

mongosh

 

then, to verify the current featureCompatibilityVersion I ran:

db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )

 

then, to set the featureCompatibilityVersion to 5 I ran:

db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )

 

Once that was completed, I was able to revert back to "latest" for the MongoDB repository and it's happily humming on 6.0.1 now

 

[[Support] jasonbean - MongoDB]

Anyone else suddenly having issues with MongoDB since the latest update(s)?

 

I'm getting the following error:

{"t":{"$date":"2022-08-27T10:57:28.631+12:00"},"s":"F",  "c":"CONTROL",  "id":20573,   "ctx":"initandlisten","msg":"Wrong mongod version","attr":{"error":"UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: Location4926900: Invalid featureCompatibilityVersion document in admin.system.version: { _id: \"featureCompatibilityVersion\", version: \"4.4\" }. See https://docs.mongodb.com/master/release-notes/5.0-compatibility/#feature-compatibility. :: caused by :: Invalid feature compatibility version value, expected '5.0' or '5.3' or '6.0. See https://docs.mongodb.com/master/release-notes/5.0-compatibility/#feature-compatibility.). If the current featureCompatibilityVersion is below 5.0, see the documentation on upgrading at https://docs.mongodb.com/master/release-notes/5.0/#upgrade-procedures."}}

 

I take it my featureCompatibilityVersion is set at 4.4, and the minimum it's wanting to accept is 5.0 now?

My MongoDB is sitting on version 6.0.1 so I'm willing to change the featureCompatibilityVersion to 6.0, but it won't let me start the DB to make any changes because of the above error.

 

 

[[Support] ich777 - Gameserver Dockers]

On 9/12/2020 at 6:04 AM, ich777 said:

Forget the post above, this was actually a easy fix, please force an update of the container and it will work as usual (turn on Advanced View in the top right corner on the Docker page and then click on Force Update).

Has your fix (thanks, by the way) removed the ECO Management Window vnc option? (Note, I'm not too sure how to enable set 'Server Management' to 'true')

It no longer adds port 8080 as a default