[SERVER-2536] mongodump causes exception on mongod Created: 11/Feb/11 Updated: 30/Mar/12 Resolved: 14/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.7.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Reinaldo Giudici | Assignee: | Aaron Staple |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
When running a mongodump on all members of a replica set, I see this error on the mongod server (all of them). I ran a db.repairDatabase() and still getting the same. This is new since 1.7.5 upgrade from 1.6.5 Fri Feb 11 14:39:11 [initandlisten] connection accepted from 10.12.57.162:37054 #56322 |
| Comments |
| Comment by Aaron Staple [ 14/Jun/11 ] |
|
sounds like it's probably |
| Comment by Bryon Ross [ 02/Jun/11 ] |
|
It seems like this issue may be related to |
| Comment by Emrys Ingersoll [ 14/Apr/11 ] |
|
I think I am also running into this issue. When running mongodump against my database, I get the following error vimana-cwshelby.utilization.devices.d4d7c5fce8c65cdabd01fbde4.cycletimeline.$id to dump/vimana-cwshelby/utilization.devices.d4d7c5fce8c65cdabd01fbde4.cycletimeline.$id.bson here is the mongod log output during this operation Thu Apr 14 17:28:48 [initandlisten] MongoDB starting : pid=90208 port=27017 dbpath=/usr/local/var/mongodb master=1 64-bit These errors were from a Mongo 1.8.1 server, the application server that originally created the database is running 1.8.0, I see the same error when running mongodump on it as well. The app server is running on Ubuntu 10.04.1 LTS using the following kernel 2.6.33.5-rscloud #2 SMP Thu Jun 10 15:26:23 UTC 2010 x86_64 GNU/Linux filesystem is ext3 the java application writing to the database is using the mongo java driver, version 2.5 I have successfully ran mongodb with --repair on this database, but it has no effect and the aforementioned error persists. |
| Comment by Aaron Staple [ 24/Feb/11 ] |
|
Hi Reinaldo - What driver are you using? (Please include version #) Have you tried running with --objcheck mode? Did you ever have a hard crash on one of these servers? This may have occurred for example before you ran your first repair. |
| Comment by Reinaldo Giudici [ 23/Feb/11 ] |
|
Hi Reinaldo - What driver are you using? (Please include version #) Have you tried running with --objcheck mode? When you did db.repairDatabase() are you sure you were 'using' the proper database? Have you tried using the --repair command line option instead? I think. Is this issue occurring in conjunction with Did you ever have a hard crash on one of these servers? This may have occurred for example before you ran your first repair. |
| Comment by Aaron Staple [ 23/Feb/11 ] |
|
Hi Reinaldo - What driver are you using? (Please include version #) |
| Comment by Reinaldo Giudici [ 17/Feb/11 ] |
|
tried again on the latest 1.7.5 and after some changes on our app. I get this on the mongodump side: Wed Feb 16 19:01:36 MessagingPort flush send() errno:9 Bad file descriptor 10.36.58.22:27017 and this on the mongod side: 3c5d4757be2885586235f19d.LEADEBOARD_sb_local_level_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_dev2_totalMoney_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_dev2_level_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_dev2_picksMade_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_dev2_buzzPoints_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_local_redeemedCollections_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_qa2_overall_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_qa2_picksWin_l for 094410ee3c5d4757be2885586235f19d.LEADEBOARD_sb_qa2_buzzPoints:tennis:atp:241_l reslen:53 445ms reslen:60 300000ms reslen:60 300000ms |