[SERVER-5766] mongorestore procedes with no authentication Created: 04/May/12 Updated: 15/Aug/12 Resolved: 17/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Haakon Lindquist | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 64 bit |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
Hi, I had a clean remote database I was running mongorestore.exe against, and the process mirrored that of a successful one even though I completely forgot username and password. Database size was under 64MB, and no rows were restore of course but three specific collections (though empty) kept comming through. It took some time before I discovered this, it might help others if they get a warning. Standard dump restore with deletion of the system.index (I even got an error during restore when index was included, but no docs came over anyway). |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 17/Jul/12 ] |
|
I believe this is fixed if you use the latest 2.1.2 build. |
| Comment by Scott Hernandez (Inactive) [ 05/May/12 ] |
|
Can you post the output of the mongorestore? It sounds like it worked correctly and failed to do the restore without authentication credentials. Can you also test the restore using latest 2.1.1 version? I think this will generate better error warnings/errors. |
| Comment by Haakon Lindquist [ 04/May/12 ] |
|
Ignore the part about the three collections, that was surely morphia`s fault. |