[SERVER-3099] Problems in importing the indexes using mongorestore Created: 15/May/11  Updated: 29/Feb/12  Resolved: 24/Oct/11

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

Type: Bug Priority: Major - P3
Reporter: rajan sthapit Assignee: Aaron Staple
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 64 bit, 700 MB RAM and 8 GB hardisk


Operating System: ALL
Participants:

 Description   

I am having a segmentation fault when I try to import a database using mongorestore. The error occurs while importing the indexes. I am trying to import the database from a 64 bit server to my local 32 bit server

The error log is given below

Wed May 11 16:42:14 [initandlisten] connection accepted from 127.0.0.1:50532 #35
Wed May 11 16:42:14 [FileAllocator] allocating new datafile /var/lib/mongodb/twitter.ns, filling with zeroes...
Wed May 11 16:42:14 [FileAllocator] done allocating datafile /var/lib/mongodb/twitter.ns, size: 16MB, took 0 secs
Wed May 11 16:42:14 [FileAllocator] allocating new datafile /var/lib/mongodb/twitter.0, filling with zeroes...
Wed May 11 16:42:14 [FileAllocator] done allocating datafile /var/lib/mongodb/twitter.0, size: 16MB, took 0 secs
Wed May 11 16:42:14 [FileAllocator] allocating new datafile /var/lib/mongodb/twitter.1, filling with zeroes...
Wed May 11 16:42:14 [FileAllocator] done allocating datafile /var/lib/mongodb/twitter.1, size: 32MB, took 0 secs
Wed May 11 16:42:14 [conn35] building new index on

{ _id: 1 }

for twitter.home_timeline
Wed May 11 16:42:14 [conn35] done for 0 records 0secs
Wed May 11 16:42:14 [FileAllocator] allocating new datafile /var/lib/mongodb/twitter.2, filling with zeroes...
Wed May 11 16:42:14 [FileAllocator] done allocating datafile /var/lib/mongodb/twitter.2, size: 64MB, took 0 secs
Wed May 11 16:42:14 [conn35] building new index on

{ _id: 1 }

for twitter.direct_messages
Wed May 11 16:42:14 [conn35] done for 0 records 0secs
Wed May 11 16:42:14 [conn35] building new index on

{ aves_user_id: 1.0 }

for twitter.home_timeline
Wed May 11 16:42:14 [conn35] done for 3838 records 0.027secs
Wed May 11 16:42:14 [conn35] building new index on

{ parsed: 1.0 }

for twitter.home_timeline
Wed May 11 16:42:14 [conn35] done for 3838 records 0.03secs
Wed May 11 16:42:14 [conn35] building new index on

{ parsed: 1.0 }

for twitter.direct_messages
Wed May 11 16:42:14 Invalid access at address: 0x11dc218a

Wed May 11 16:42:14 Got signal: 11 (Segmentation fault).



 Comments   
Comment by Aaron Staple [ 24/Oct/11 ]

SERVER-3961

Comment by Aaron Staple [ 24/Oct/11 ]

Potentially this was SERVER-3961. If you are able to provide more information on the circumstances when this occurred, please reopen the ticket.

Comment by Aaron Staple [ 05/Sep/11 ]

Can you send the full log?
Is there stack trace along with the seg fault?

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

What version was this on?
Most likely issue was data is too big for 32-bit server

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