[Pkg-mongodb-maintainers] Bug#851220: mongodb-server: broken upgrade from 2.6 to 3.2

Eric Cooper ecc at cooper-siegel.org
Fri Jan 13 01:18:21 UTC 2017

Package: mongodb-server
Version: 1:3.2.11-2
Severity: normal

My mongo database stopped working after upgrading to the latest
version in stretch, which changed from mongo 2.6 to 3.2.

mongod would not start, complaining that authSchemaUpgrade needed to
be run first (and only on a 2.6 server, which was no longer

I ended up downloading the 2.6 tarball from the mongo website
and running that version of mongod against my database in /var/lib so
I could do the authSchemaUpgrade.  After that the new 3.2 version
seemed to work OK.

In case anyone else gets stuck like this, I basically did this:

$ sudo mongod2.6 --noauth --dbpath /var/lib/mongodb &
$ mongo
> use admin
> db.runCommand({authSchemaUpgrade:1})

I'm not sure if this could be detected or automated, but I wasted a
lot of time.  I don't think there should be a "silent" upgrade across
major versions like this when there are such incompatible changes.
Perhaps have mongodb-2.6, mongodb-3.2, etc. packages available concurrently
in the archive, with mongodb pulling in the "current" one.

More information about the Pkg-mongodb-maintainers mailing list