[SERVER-22004] Upgrading from 2.6.8 to 3.2 fails due to "Old 2.4 style user index identified. The authentication schema needs to be updated by running authSchemaUpgrade on a 2.6 server." Created: 23/Dec/15  Updated: 23/Dec/15  Resolved: 23/Dec/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Elad Moshe Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

I am trying to upgrade mongoDB replica set. It was created as standalone server in version 2.4 and then upgraded to 2.6.8 about a year ago.
Apparently at some early stage authentication was enabled but this was long ago removed (i.e. no authentication is currently required).
I tried to upgrade to 3.2 by shutting down one replica member, delete the data files, upgrade to 3.2 and let it sync with the replica set (which is obviously still 2.6.8). I successfully synced about 12GB of data before the server crashed with the aforementioned error. Everytime I try to start the server again I get the same error.
When checking the collection admin.system.users there was indeed one user, but removing and trying to start the server again did not help. I also tried to remove the indexes in that collection.

Log output

2015-12-23T13:48:35.166+0000 I -        [initandlisten] Detected data files in /var/lib/mongodb/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2015-12-23T13:48:35.166+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2015-12-23T13:48:37.575+0000 I STORAGE  [initandlisten] Starting WiredTigerRecordStoreThread local.oplog.rs
2015-12-23T13:48:37.575+0000 I STORAGE  [initandlisten] The size storer reports that the oplog contains 32029 records totaling to 22370434 bytes
2015-12-23T13:48:37.576+0000 I STORAGE  [initandlisten] Sampling from the oplog between Dec 23 09:26:32:2 and Dec 23 11:48:41:1 to determine where to place markers for truncation
2015-12-23T13:48:37.576+0000 I STORAGE  [initandlisten] Taking 0 samples and assuming that each section of oplog contains approximately 358809 records totaling to 250607669 bytes
2015-12-23T13:48:37.783+0000 I CONTROL  [initandlisten]
2015-12-23T13:48:37.783+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2015-12-23T13:48:37.783+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2015-12-23T13:48:37.783+0000 I CONTROL  [initandlisten]
2015-12-23T13:48:37.828+0000 I STORAGE  [initandlisten] Old 2.4 style user index identified. The authentication schema needs to be updated by running authSchemaUpgrade on a 2.6 server.
2015-12-23T13:48:37.828+0000 W REPL     [initandlisten] ReplicationCoordinatorImpl::shutdown() called before startReplication() finished.  Shutting down without cleaning up the replication system
2015-12-23T13:48:37.828+0000 I CONTROL  [initandlisten] now exiting
2015-12-23T13:48:37.828+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2015-12-23T13:48:37.828+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2015-12-23T13:48:37.828+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2015-12-23T13:48:37.829+0000 I NETWORK  [initandlisten] shutdown: going to close sockets...
2015-12-23T13:48:37.829+0000 I STORAGE  [initandlisten] WiredTigerKVEngine shutting down
2015-12-23T13:48:40.850+0000 I STORAGE  [initandlisten] shutdown: removing fs lock...
2015-12-23T13:48:40.850+0000 I CONTROL  [initandlisten] dbexit:  rc: 4



 Comments   
Comment by Kelsey Schubert [ 23/Dec/15 ]

Hi emoshe,

Thanks for the report. I have made a couple of observations:

  • It appears you did not upgrade the authentication schema after upgrading from 2.4. This document explains the steps to upgrade the authorization.
  • We do not support upgrading from 2.6 directly to 3.2. Please review our documentation on the upgrade process here.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag.

Regards,
Thomas

Generated at Thu Feb 08 03:59:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.