- 
    Type:
Bug
 - 
    Resolution: Duplicate
 - 
    Priority:
Major - P3
 - 
    None
 - 
    Affects Version/s: 2.6.1
 - 
    Component/s: Shell
 - 
    None
 
- 
        ALL
 - 
        
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
I'm using a local, single-process installation (i.e. without sharding or replication). After running the authorization schema upgrade, the former regular users became dbOwner on their databases. But if I try to connect to the MongoDB instance with such a user, I get
MongoDB shell version: 2.6.1 connecting to: xyz Error while trying to show server startup warnings: not authorized on admin to execute command { getLog: "startupWarnings" }
The database process log reads:
2014-05-17T19:11:03.724+0300 [conn3] Auth schema upgrade copying version 3 users from admin.system.new_users to admin.system.users
2014-05-17T19:11:03.725+0300 [conn3] command admin.$cmd command: authSchemaUpgrade { authSchemaUpgrade: 1.0 } keyUpdates:0 numYields:0 locks(mi
cros) R:49 r:83 reslen:44 188ms
2014-05-17T19:49:10.067+0300 [conn4]  authenticate db: xyz { authenticate: 1, nonce: "xxx", user: "xyz", key: "xxx" }
2014-05-17T19:49:10.069+0300 [conn4] Unauthorized not authorized on admin to execute command { getLog: "startupWarnings" }
2014-05-17T19:49:10.070+0300 [conn4] Unauthorized not authorized on admin to execute command { replSetGetStatus: 1.0, forShell: 1.0 }
- duplicates
 - 
                    
SERVER-13588 Shell prints startup warning when auth enabled
-         
 - Closed
 
 -