Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
two routing servers with mongos (3.2.4)
three config servers with mongod (3.2.4)
twelve shard servers organized in a two-sharded replicasets rs1/rs2 with currently each three old (3.2.4) and new (3.2.5) shard-servers with mongod (shard{1,2}{a,b,c,d,e,f} with a/b/c 3.2.4 and d/e/f 3.2.5)
*Location*: https://docs.mongodb.org/manual/search/?query=authorization
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
*Referrer*: https://docs.mongodb.org/manual/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: search
two routing servers with mongos (3.2.4) three config servers with mongod (3.2.4) twelve shard servers organized in a two-sharded replicasets rs1/rs2 with currently each three old (3.2.4) and new (3.2.5) shard-servers with mongod (shard{1,2}{a,b,c,d,e,f} with a/b/c 3.2.4 and d/e/f 3.2.5) *Location*: https://docs.mongodb.org/manual/search/?query=authorization *User-Agent*: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 *Referrer*: https://docs.mongodb.org/manual/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: search
Description
Searched for "authorization",
expected to find information about the error message (introduced in 3.2.5?) that contains "WARNING: Access control is not enabled for the database." and "Read and write access to data and configuration is unrestricted."
The 3.2.4 instances that are configured identically (same replica sets, identical /etc/mongod.conf) don't have this message.
Kind regards,
Dominik