[SERVER-3841] Profiling in admin DB can stick entries in other DBs (listDatabases command) Created: 14/Sep/11 Updated: 19/Mar/13 Resolved: 11/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Security, Tools |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jared D. Cottrell | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | cloud, profiling, security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
64-bit Mac OS X Lion |
||
| Issue Links: |
|
||||||||
| Operating System: | OS X | ||||||||
| Participants: | |||||||||
| Description |
|
Not quite sure how to accurately characterize the problem. But clearly with a DB that started in auth mode with no bowtiesarecool database it seems like a problem that without anyone with credentials mentioning the database it got created and populated with data. Certainly related to % mongo localhost/admin -u *** -p *** > show dbs reslen:308 bytes:292", "millis" : 0 } |
| Comments |
| Comment by Spencer Brody (Inactive) [ 11/Mar/13 ] |
|
Reproduced in 1.8.5, but could not repro in 2.0.7, 2.2.3 or 2.4.0-RC2. |
| Comment by Tony Hannan [ 19/Sep/11 ] |
|
This is probably a duplicate of |
| Comment by Angela Shulman [ 17/Sep/11 ] |
|
Following on to Jared's bug report above, we've been seeing the same databases come back again even after dropping them. And sometimes they can come back again with the following state: MongoDB shell version: 1.8.2 |