[SERVER-18561] Incorrect message displayed during mongorestore Created: 19/May/15  Updated: 01/Jul/15  Resolved: 01/Jul/15

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

Type: Bug Priority: Minor - P4
Reporter: Geoff Meakin Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

MongoDB 2.4.10

I thought you'd like to know about this bug which is closely related to SERVER-7181.

If you set up a user with only readWrite, and dbAdmin but not userAdmin privileges on a database, and then try and restore a previous DB into that database, you get the following error during a mongorestore:

Tue May 19 15:23:19.700 Assertion: 13111:field not found, expected type 2
0xdecc61 0xdafbab 0xdb00ec 0x6d5d7d 0x6e5bfb 0x6e3acb 0x6e7ddc 0xda34b8 0xda9248 0x6ccf37 0x3d68e1ecdd 0x6ccda9
mongorestore(_ZN5mongo15printStackTraceERSo+0x21) [0xdecc61]
mongorestore(_ZN5mongo11msgassertedEiPKc+0x9b) [0xdafbab]
mongorestore() [0xdb00ec]
mongorestore(_ZNK5mongo11BSONElement3chkEi+0x1fd) [0x6d5d7d]
mongorestore(_ZN7Restore9drillDownEN5boost11filesystem34pathEbbbb+0x24bb) [0x6e5bfb]
mongorestore(_ZN7Restore9drillDownEN5boost11filesystem34pathEbbbb+0x38b) [0x6e3acb]
mongorestore(_ZN7Restore5doRunEv+0xc7c) [0x6e7ddc]
mongorestore(_ZN5mongo8BSONTool3runEv+0x458) [0xda34b8]
mongorestore(_ZN5mongo4Tool4mainEiPPc+0x13d8) [0xda9248]
mongorestore(main+0x37) [0x6ccf37]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x3d68e1ecdd]
mongorestore(__gxx_personality_v0+0x459) [0x6ccda9]
assertion: 13111 field not found, expected type 2

From the other issue SERVER-7181 it is clear that it is supposed to print a message about lack of authorisation, but instead you get this lowlevel error.



 Comments   
Comment by Ramon Fernandez Marina [ 18/Jun/15 ]

Hi geoff.meakin2@bskyb.com, we haven't heard back from you for some time. Have you been able to try the newer tools from 3.0 to see if they solve this issue?

Thanks,
Ramón.

Comment by Ramon Fernandez Marina [ 29/May/15 ]

Thanks for your report geoff.meakin2@bskyb.com. As you may already know the tools have been completely re-written for 3.0, so I'd like to ask you to re-run the same scenario with a recent version of the tools. The new tools are backwards compatible with older versions of mongod and greatly improved. If the error message continues to not be very useful we can move this ticket to the TOOLS project and re-classify it as an improvement request.

Can you please try with a newer version of the tools and report back?

Thanks,
Ramón.

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