[SERVER-1621] bsondump always crashes on windows Created: 12/Aug/10  Updated: 30/Mar/12  Resolved: 09/Nov/11

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 1.6.0, 1.8.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Matthias Goetzke Assignee: Spencer Brody (Inactive)
Resolution: Cannot Reproduce Votes: 2
Labels: Windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 Ultimate 64Bit.


Attachments: XML File WER8F76.tmp.WERInternalMetadata.xml     File WERA7A9.tmp.mdmp    
Operating System: Windows
Participants:

 Description   

Startung bsondump crashes after connecting to the database.

It says: connected to: 127.0.01 and then windows reports "stopped working"
The exception seems to be "unknown software expection" => 0x400000015

mongo.exe can connect to 127.0.01 without fail.
The database connected to is a replica-set with just one mongod process for testing.



 Comments   
Comment by Spencer Brody (Inactive) [ 11/Oct/11 ]

Just tested with the prebuilt 64 bit packages from mongodb.org/downloads for 1.8.3 and 2.0.0 on Windows 7 64 bit and it worked fine for me.
Can you attach the full output (including the command typed) of a run where it fails?

Comment by Justin Dearing [ 05/Sep/11 ]

I jsut tried this on mongo 1.83. The command "bsondump foo.bson" fails whether I do UAC elevation or not. It generates a bug report that it sends to Microsoft. If your not doing so already, its possible to sign up to be able to retrieve those bug reports from Microsoft. Not sure how.

Comment by Eliot Horowitz (Inactive) [ 02/Sep/11 ]

Hey Justin - this still an issue?

Comment by Justin Dearing [ 31/Jan/11 ]

Attempts to reproduce on WIndows 7 32 bit runing mongodb 1.6.5 as a service.
Ok failed the first time running as an unpriviledged user (local admin but UAC taking that away from me).

C:\Users\DearingJ>bsondump
connected to: 127.0.0.1

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

C:\Users\DearingJ>mongo localhost
MongoDB shell version: 1.6.5
connecting to: localhost
> exit
bye

Ran as an priviledged user and it worked. It then proceeded to work as a priviledged and unpriviledged user multiple times:

C:\Users\DearingJ>mongodump
connected to: 127.0.0.1
all dbs
DATABASE: driveronlinetests to dump/driveronlinetests
driveronlinetests.test to dump/driveronlinetests/test.bson
1 objects
driveronlinetests.system.indexes to dump/driveronlinetests/system.indexes.bson
1 objects
DATABASE: clientRSVP to dump/clientRSVP
clientRSVP.system.users to dump/clientRSVP/system.users.bson
3 objects
clientRSVP.system.indexes to dump/clientRSVP/system.indexes.bson
14 objects
clientRSVP.locations to dump/clientRSVP/locations.bson
1 objects
clientRSVP.events to dump/clientRSVP/events.bson
2 objects
clientRSVP.Locations to dump/clientRSVP/Locations.bson
0 objects
clientRSVP.deleteMe to dump/clientRSVP/deleteMe.bson
1 objects
clientRSVP.Events to dump/clientRSVP/Events.bson
0 objects
clientRSVP.attendees to dump/clientRSVP/attendees.bson
380 objects
clientRSVP.administrators to dump/clientRSVP/administrators.bson
1 objects
clientRSVP.sessions to dump/clientRSVP/sessions.bson
10 objects
DATABASE: test to dump/test
test.magicdiscriminator to dump/test/magicdiscriminator.bson
1 objects
test.system.indexes to dump/test/system.indexes.bson
1 objects
DATABASE: admin to dump/admin
DATABASE: passTheGlass to dump/passTheGlass

This in the logs:

Mon Jan 31 16:38:25 [initandlisten] connection accepted from 127.0.0.1:51451 #64
Mon Jan 31 16:38:26 [conn64] query clientRSVP.$cmd ntoreturn:1 command: { count: "system.users", query: {} } reslen:64 128ms
Mon Jan 31 16:38:26 [conn64] query clientRSVP.attendees reslen:30281 nscanned:101 { query: {}, $snapshot: true } nreturned:101 137ms
Mon Jan 31 16:38:26 [conn64] query passTheToast.$cmd ntoreturn:1 command: { count: "fs.chunks", query: {} } reslen:64 188ms
Mon Jan 31 16:38:27 [conn64] query passTheToast.fs.chunks reslen:115408 nscanned:6 { query: {}, $snapshot: true } nreturned:6 202ms
Mon Jan 31 16:38:27 [conn64] end connection 127.0.0.1:51451
Mon Jan 31 16:38:55 [initandlisten] connection accepted from 127.0.0.1:51454 #65
Mon Jan 31 16:38:55 [conn65] end connection 127.0.0.1:51454
Mon Jan 31 16:39:03 [initandlisten] connection accepted from 127.0.0.1:51455 #66
Mon Jan 31 16:39:03 [conn66] end connection 127.0.0.1:51455
Mon Jan 31 16:39:33 [initandlisten] connection accepted from 127.0.0.1:51462 #67
Mon Jan 31 16:39:33 [conn67] end connection 127.0.0.1:51462
Mon Jan 31 16:39:43 [initandlisten] connection accepted from 127.0.0.1:51464 #68
Mon Jan 31 16:39:43 [conn68] end connection 127.0.0.1:51464

Comment by Testo [ 01/Oct/10 ]

Crashed on 1.6.3 win32 on WinXP SP3 as well

Comment by Matthias Goetzke [ 22/Sep/10 ]

as to 1) ... still crashes upon start. no matter what the options
as to 2) mongorestore works fine in all variations

Comment by Kristina Chodorow (Inactive) [ 13/Sep/10 ]

Okay, thanks. Can you do two things?

1) try running it with "--type debug" and your normal arguments
2) try running mongorestore with a file ("./mongorestore dump" or "./mongorestore foo.bson") and see if that works (they share some code, trying to narrow it down)

Comment by Matthias Götzke [ 12/Sep/10 ]

I tried it using the argument. i tried most combinations but not all since i think a program should not crash when a parameter is missing. Help (--?) is working but the rest consistently crashes. I tried it on two different machines.

Comment by Kristina Chodorow (Inactive) [ 10/Sep/10 ]

How are you running bsondump? It requires a filename:

bsondump.exe dump\foo\bar.bson

Generated at Thu Feb 08 02:57:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.