Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6

Mup version (mup --version): 1.5.5

Mup config

{
  "servers": {
    "one": {
      "host": "1.2.3.4",
      "username": "root",
      "password": "password"
    }
  },
  "proxy": {
    "domains": "host.com,subdomain.host.com",
    "ssl": {
      "letsEncryptEmail": "[e-mail]",
      "forceSSL": true
    }
  },
  "mongo": {
    "version": "3.4.1",
    "servers": {
      "one": {}
    },
    "dbName": "project_name"
  },
  "app": {
    "name": "my-app",
    "path": "../project_name",
    "volumes": {
      "/images": "/images"
    },
    "servers": {
      "one": {}
    },
    "buildOptions": {
      "serverOnly": true,
      "buildLocation": "/tmp/mup-meteor-46532786-03a5-4a6f-b9ab-8aac9105b59a",
      "cleanBuildLocation": true
    },
    "env": {
      "ROOT_URL": "https://host.com",
      "MONGO_URL": "mongodb://mongodb:27017/my-app",
      "VIRTUAL_HOST": "host.com,subdomain.host.com",
      "HTTPS_METHOD": "redirect",
      "LETSENCRYPT_HOST": "host.com,subdomain.host.com",
      "LETSENCRYPT_EMAIL": "[e-mail]",
      "VIRTUAL_PORT": 3000,
      "HTTP_FORWARDED_COUNT": 1
    },
    "docker": {
      "image": "zodern/meteor:latest",
      "stopAppDuringPrepareBundle": true,
      "imagePort": 3000,
      "args": [
        "--link=mongodb:mongodb"
      ]
    },
    "enableUploadProgressBar": true,
    "type": "meteor"
  }
}

Output of command

Started TaskList: Start Meteor
[159.203.61.14] - Start Meteor
[159.203.61.14] - Start Meteor: SUCCESS
[159.203.61.14] - Verifying Deployment
[159.203.61.14] x Verifying Deployment: FAILED
	
	      ------------------------------------STDERR------------------------------------
	       (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	curl: (7) Failed to connect to 172.17.0.2 port 3000: Connection refused
	=> Logs:
	=> Setting node version
	NODE_VERSION=14.18.3
	v14.18.3 is already installed.
	Now using node v14.18.3 (npm v6.14.15)
	default -> 14.18.3 (-> v14.18.3 *)
	=> Starting meteor app on port 3000
	/built_app/programs/server/node_modules/fibers/future.js:313
							throw(ex);
							^
	
	MongoServerSelectionError: Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)
	    at Timeout._onTimeout (/built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/sdam/topology.js:312:38)
	    at listOnTimeout (internal/timers.js:557:17)
	    at processTimers (internal/timers.js:500:7) {
	  reason: TopologyDescription {
	    type: 'Unknown',
	    servers: Map(1) {
	      'mongodb:27017' => ServerDescription {
	        _hostAddress: HostAddress { isIPv6: false, host: 'mongodb', port: 27017 },
	        address: 'mongodb:27017',
	        type: 'Unknown',
	        hosts: [],
	        passives: [],
	        arbiters: [],
	        tags: {},
	        minWireVersion: 0,
	        maxWireVersion: 0,
	        roundTripTime: -1,
	        lastUpdateTime: 51406758209,
	        lastWriteDate: 0,
	        error: MongoCompatibilityError: Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)
	            at checkSupportedServer (/built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connect.js:62:12)
	            at /built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connect.js:106:40
	            at MessageStream.messageHandler (/built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connection.js:474:9)
	            at MessageStream.emit (events.js:400:28)
	            at processIncomingData (/built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:108:16)
	            at MessageStream._write (/built_app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/message_stream.js:28:9)
	            at writeOrBuffer (internal/streams/writable.js:358:12)
	            at MessageStream.Writable.write (internal/streams/writable.js:303:10)
	            at Socket.ondata (internal/streams/readable.js:731:22)
	            at Socket.emit (events.js:400:28)
	            at addChunk (internal/streams/readable.js:293:12)
	            at readableAddChunk (internal/streams/readable.js:267:9)
	            at Socket.Readable.push (internal/streams/readable.js:206:10)
	            at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
	      }
	    },
	    stale: false,
	    compatible: true,
	    heartbeatFrequencyMS: 10000,
	    localThresholdMS: 15,
	    logicalSessionTimeoutMinutes: undefined
	  }
	}
	=> Setting node version
	NODE_VERSION=14.18.3
	v14.18.3 is already installed.
	Now using node v14.18.3 (npm v6.14.15)
	default -> 14.18.3 (-> v14.18.3 *)
	=> Starting meteor app on port 3000
	 
	=> Redeploying previous version of the app

[philipmjohnson]

@jankapunkt Here’s some documentation I wrote for our system. One section explains how to wipe mongo:

https://www.radgrad.org/docs/developers/deployment/howto/update-mongo-mup

Yes, we did get it working.

[jankapunkt]

@philipmjohnson thanks a lot that worked very well! One note though (for others reading this) - make sure to read the mongorestore documentation as the it behaves slightly different for Mongo 5, for example the --db and --collection options are now replaces by --nsInclude.

After correcting the mongorestore options the DB has been restored and everything is running as expected.