Segmentation fault in MongoDB 1.6
37 views
Skip to first unread message
odo
Aug 19, 2010, 5:32:51 AM8/19/10
to mongodb-user
Hi,
I am experiencing segmentation faults every few hours with moderate
load.
Here is my setup:
Ubuntu 10.04.1 LTS
mongod --version
db version v1.6.0, pdfile version 4.5
Thu Aug 19 09:17:37 git version:
2c7f164b653f0d703947572ede064aed41cc2185
MongoDB was installed via apt-get from http://downloads.mongodb.org/distros/ubuntu
The config file looks like this:
# mongodb.conf
replSet=apiv3
logpath=/var/log/mongodb/mongod.node1.log
port = 27017
logappend=true
#dbpath=/var/lib/mongodb/node1
dbpath=/db-storage/mongodb/node1
fork = true
rest = true
In /etc/init.d/mongodb we do "ulimit -n 65535" to increase the number
of open files.
On the client side, we use Ruby. Here are the gem versions:
mongo: 1.0.7
bson: 1.0.4
bson_ext: 1.0.4
Below are the last words from mongodb.
Any suggestions are very welcome.
Best,
Florian
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.137:33342 #6457
Thu Aug 19 08:58:38 [conn6457] end connection 10.0.235.137:33342
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.137:33343 #6458
Thu Aug 19 08:58:38 [conn932] ClientCursor::find(): cursor not found
in map 0 (ok after a drop)
killcursors: found 0 of 1
Thu Aug 19 08:58:38 [conn6458] end connection 10.0.235.137:33343
Thu Aug 19 08:58:38 [conn932] killcursors: found 0 of 1
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.150:33265 #6459
Thu Aug 19 08:58:38 [conn6459] end connection 10.0.235.150:33265
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.150:33266 #6460
Thu Aug 19 08:58:39 [conn267] killcursors: found 0 of 1
Thu Aug 19 08:58:39 [conn932] killcursors: found 0 of 1
Thu Aug 19 08:58:39 [conn108] killcursors: found 0 of 1
Thu Aug 19 08:58:39 Got signal: 11 (Segmentation fault).
Thu Aug 19 08:58:39 Backtrace:
0x815f59 0x7f6f6e065af0 0x7f6f6e0b9071 0x6102b3 0x61069f 0x610bc5
0x733016 0x73b8cc 0x73e868 0x741da5 0x742707 0x5fbf73 0x6fca0a
0x7022ee 0x8185bf 0x82bcb0 0x7f6f6eb699ca 0x7f6f6e1186fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f6f6e065af0]
/lib/libc.so.6(memcpy+0x411) [0x7f6f6e0b9071]
/usr/bin/
mongod(_ZN5mongo22fillQueryResultFromObjERNS_10BufBuilderEPNS_12FieldMatcherERNS_7BSONObjEPNS_7DiskLocE
+0xb03) [0x6102b3]
/usr/bin/mongod(_ZN5mongo11UserQueryOp6finishEb+0x1ff) [0x61069f]
/usr/bin/mongod(_ZN5mongo11UserQueryOp4nextEv+0x325) [0x610bc5]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner6nextOpERNS_7QueryOpE
+0x56) [0x733016]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner3runEv+0x48c)
[0x73b8cc]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet5runOpERNS_7QueryOpE+0x58)
[0x73e868]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner9runOpOnceERNS_7QueryOpE
+0x65) [0x741da5]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner5runOpERNS_7QueryOpE+0x17)
[0x742707]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x933) [0x5fbf73]
/usr/bin/mongod() [0x6fca0a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x158e) [0x7022ee]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f6f6eb699ca]
/lib/libc.so.6(clone+0x6d) [0x7f6f6e1186fd]
Thu Aug 19 08:58:39 dbexit:
Thu Aug 19 08:58:39 [conn104] shutdown: going to close listening
sockets...
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 12
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 13
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 14
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 15
Thu Aug 19 08:58:39 [conn104] shutdown: going to flush oplog...
Thu Aug 19 08:58:39 [conn104] shutdown: going to close sockets...
Thu Aug 19 08:58:39 [conn104] shutdown: waiting for fs
preallocator...
Thu Aug 19 08:58:39 [conn104] shutdown: closing all files...
Thu Aug 19 08:58:39 [conn3] end connection 127.0.0.1:41244
Thu Aug 19 08:58:39 [conn6409] end connection 10.0.235.146:41546
Thu Aug 19 08:58:39 [conn267] end connection 10.0.235.162:59561
Thu Aug 19 08:58:39 closeAllFiles() finished
Thu Aug 19 08:58:39 [conn104] shutdown: removing fs lock...
Thu Aug 19 08:58:39 dbexit: really exiting now
I am experiencing segmentation faults every few hours with moderate
load.
Here is my setup:
Ubuntu 10.04.1 LTS
mongod --version
db version v1.6.0, pdfile version 4.5
Thu Aug 19 09:17:37 git version:
2c7f164b653f0d703947572ede064aed41cc2185
MongoDB was installed via apt-get from http://downloads.mongodb.org/distros/ubuntu
The config file looks like this:
# mongodb.conf
replSet=apiv3
logpath=/var/log/mongodb/mongod.node1.log
port = 27017
logappend=true
#dbpath=/var/lib/mongodb/node1
dbpath=/db-storage/mongodb/node1
fork = true
rest = true
In /etc/init.d/mongodb we do "ulimit -n 65535" to increase the number
of open files.
On the client side, we use Ruby. Here are the gem versions:
mongo: 1.0.7
bson: 1.0.4
bson_ext: 1.0.4
Below are the last words from mongodb.
Any suggestions are very welcome.
Best,
Florian
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.137:33342 #6457
Thu Aug 19 08:58:38 [conn6457] end connection 10.0.235.137:33342
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.137:33343 #6458
Thu Aug 19 08:58:38 [conn932] ClientCursor::find(): cursor not found
in map 0 (ok after a drop)
killcursors: found 0 of 1
Thu Aug 19 08:58:38 [conn6458] end connection 10.0.235.137:33343
Thu Aug 19 08:58:38 [conn932] killcursors: found 0 of 1
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.150:33265 #6459
Thu Aug 19 08:58:38 [conn6459] end connection 10.0.235.150:33265
Thu Aug 19 08:58:38 [initandlisten] connection accepted from
10.0.235.150:33266 #6460
Thu Aug 19 08:58:39 [conn267] killcursors: found 0 of 1
Thu Aug 19 08:58:39 [conn932] killcursors: found 0 of 1
Thu Aug 19 08:58:39 [conn108] killcursors: found 0 of 1
Thu Aug 19 08:58:39 Got signal: 11 (Segmentation fault).
Thu Aug 19 08:58:39 Backtrace:
0x815f59 0x7f6f6e065af0 0x7f6f6e0b9071 0x6102b3 0x61069f 0x610bc5
0x733016 0x73b8cc 0x73e868 0x741da5 0x742707 0x5fbf73 0x6fca0a
0x7022ee 0x8185bf 0x82bcb0 0x7f6f6eb699ca 0x7f6f6e1186fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f6f6e065af0]
/lib/libc.so.6(memcpy+0x411) [0x7f6f6e0b9071]
/usr/bin/
mongod(_ZN5mongo22fillQueryResultFromObjERNS_10BufBuilderEPNS_12FieldMatcherERNS_7BSONObjEPNS_7DiskLocE
+0xb03) [0x6102b3]
/usr/bin/mongod(_ZN5mongo11UserQueryOp6finishEb+0x1ff) [0x61069f]
/usr/bin/mongod(_ZN5mongo11UserQueryOp4nextEv+0x325) [0x610bc5]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner6nextOpERNS_7QueryOpE
+0x56) [0x733016]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner3runEv+0x48c)
[0x73b8cc]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet5runOpERNS_7QueryOpE+0x58)
[0x73e868]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner9runOpOnceERNS_7QueryOpE
+0x65) [0x741da5]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner5runOpERNS_7QueryOpE+0x17)
[0x742707]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x933) [0x5fbf73]
/usr/bin/mongod() [0x6fca0a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x158e) [0x7022ee]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f6f6eb699ca]
/lib/libc.so.6(clone+0x6d) [0x7f6f6e1186fd]
Thu Aug 19 08:58:39 dbexit:
Thu Aug 19 08:58:39 [conn104] shutdown: going to close listening
sockets...
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 12
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 13
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 14
Thu Aug 19 08:58:39 [conn104] going to close listening socket: 15
Thu Aug 19 08:58:39 [conn104] shutdown: going to flush oplog...
Thu Aug 19 08:58:39 [conn104] shutdown: going to close sockets...
Thu Aug 19 08:58:39 [conn104] shutdown: waiting for fs
preallocator...
Thu Aug 19 08:58:39 [conn104] shutdown: closing all files...
Thu Aug 19 08:58:39 [conn3] end connection 127.0.0.1:41244
Thu Aug 19 08:58:39 [conn6409] end connection 10.0.235.146:41546
Thu Aug 19 08:58:39 [conn267] end connection 10.0.235.162:59561
Thu Aug 19 08:58:39 closeAllFiles() finished
Thu Aug 19 08:58:39 [conn104] shutdown: removing fs lock...
Thu Aug 19 08:58:39 dbexit: really exiting now
Eliot Horowitz
Aug 19, 2010, 9:32:45 AM8/19/10
to mongod...@googlegroups.com
Can you send some more info about types of operations you're doing?
A sample mongostat output would be great
> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
>
odo
Aug 19, 2010, 9:58:42 AM8/19/10
to mongodb-user
We have waves of activity, each wave basically consists of:
1. removing and/or updating dozens to hundreds of documents
2. one upsert
3. dozens to hundreds of query-remove-insert and query-upsert series
During one wave (1s - 40s) steps 2-3 are repeated 4-25 times,
sometimes spaces, sometimes overlapping.
In addition to that there is a baseline of queries, using many indexes
(also geospatial with large min and max).
The database has six collections.
Here is a mongostat output (although not from the exact same crash):
insert/s query/s update/s delete/s getmore/s command/s flushes/s
mapped vsize res faults/s locked % idx miss % q t|r|w
conn time
330 331 6 182 238 16 0
6302 6984 3983 0 11.6 0 0|0|0 35
11:06:07
392 405 7 67 251 34 0
6302 6984 3983 1 6.2 0 0|0|0 33
11:06:08
235 295 5 85 199 135 0
6302 6984 3983 0 7.4 0 0|0|0 33
11:06:09
346 349 6 135 323 258 0
6302 6984 3984 0 10 0 0|0|0 32
11:06:10
75 83 5 58 88 86 0
6302 6964 3984 0 2.2 0 0|0|0 30
11:06:11
222 241 0 198 234 233 0
6302 6964 3984 0 7.3 0 0|0|0 30
11:06:12
70 61 2 51 73 76 0
6302 6964 3984 0 2 0 0|0|0 30
11:06:13
16 25 5 14 23 29 0
6302 6954 3984 0 0.6 0 0|0|0 29
11:06:14
114 128 0 28 84 2 0
6302 6934 3984 0 2.2 0 0|0|0 27
11:06:15
53 60 2 24 46 8 0
6302 6934 3984 0 1.8 0 0|0|0 27
11:06:16
0 3 1 0 1 4 0
6302 6924 3984 0 0 0 0|0|0 26
11:06:17
12 28 3 0 10 29 0
6302 6914 3984 0 0.1 0 0|0|0 25
11:06:18
0 19 0 0 0 13 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:19
0 2 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:20
28 4 4 0 17 42 0
6302 6914 3984 0 0.1 0 0|0|0 28
11:06:21
3 1 0 0 2 5 0
6302 6914 3984 0 0 0 0|0|0 27
11:06:22
10 9 5 3 12 24 0
6302 6914 3984 0 0.1 0 0|0|0 26
11:06:23
11 4 5 0 12 23 0
6302 6914 3984 0 0.1 0 0|0|0 25
11:06:24
0 0 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:25
0 2 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:26
insert/s query/s update/s delete/s getmore/s command/s flushes/s
mapped vsize res faults/s locked % idx miss % q t|r|w
conn time
0 4 0 0 1 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:27
0 8 1 0 2 9 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:28
14 10 1 0 8 21 0
6302 6914 3984 0 0 0 0|0|0 26
11:06:29
Thu Aug 19 11:06:30 MessagingPort recv() errno:104 Connection reset by
peer 127.0.0.1:27017
Thu Aug 19 11:06:30 SocketException: 9001 socket exception
can't get data: DBClientBase::findOne: transport error
Thu Aug 19 11:06:31 trying reconnect to 127.0.0.1
Thu Aug 19 11:06:31 reconnect 127.0.0.1 failed couldn't connect to
server 127.0.0.1}
Thu Aug 19 11:06:31 MessagingPort say send() errno:9 Bad file
descriptor 127.0.0.1:27017
can't get data: socket exception
On Aug 19, 3:32 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> Can you send some more info about types of operations you're doing?
>
> A sample mongostat output would be great
>
>
>
> On Thu, Aug 19, 2010 at 5:32 AM, odo <android...@googlemail.com> wrote:
> > Hi,
>
> > I am experiencing segmentation faults every few hours with moderate
> > load.
> > Here is my setup:
>
> > Ubuntu 10.04.1 LTS
>
> > mongod --version
> > db version v1.6.0, pdfile version 4.5
> > Thu Aug 19 09:17:37 git version:
> > 2c7f164b653f0d703947572ede064aed41cc2185
>
> > MongoDB was installed via apt-get fromhttp://downloads.mongodb.org/distros/ubuntu
1. removing and/or updating dozens to hundreds of documents
2. one upsert
3. dozens to hundreds of query-remove-insert and query-upsert series
During one wave (1s - 40s) steps 2-3 are repeated 4-25 times,
sometimes spaces, sometimes overlapping.
In addition to that there is a baseline of queries, using many indexes
(also geospatial with large min and max).
The database has six collections.
Here is a mongostat output (although not from the exact same crash):
insert/s query/s update/s delete/s getmore/s command/s flushes/s
mapped vsize res faults/s locked % idx miss % q t|r|w
conn time
330 331 6 182 238 16 0
6302 6984 3983 0 11.6 0 0|0|0 35
11:06:07
392 405 7 67 251 34 0
6302 6984 3983 1 6.2 0 0|0|0 33
11:06:08
235 295 5 85 199 135 0
6302 6984 3983 0 7.4 0 0|0|0 33
11:06:09
346 349 6 135 323 258 0
6302 6984 3984 0 10 0 0|0|0 32
11:06:10
75 83 5 58 88 86 0
6302 6964 3984 0 2.2 0 0|0|0 30
11:06:11
222 241 0 198 234 233 0
6302 6964 3984 0 7.3 0 0|0|0 30
11:06:12
70 61 2 51 73 76 0
6302 6964 3984 0 2 0 0|0|0 30
11:06:13
16 25 5 14 23 29 0
6302 6954 3984 0 0.6 0 0|0|0 29
11:06:14
114 128 0 28 84 2 0
6302 6934 3984 0 2.2 0 0|0|0 27
11:06:15
53 60 2 24 46 8 0
6302 6934 3984 0 1.8 0 0|0|0 27
11:06:16
0 3 1 0 1 4 0
6302 6924 3984 0 0 0 0|0|0 26
11:06:17
12 28 3 0 10 29 0
6302 6914 3984 0 0.1 0 0|0|0 25
11:06:18
0 19 0 0 0 13 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:19
0 2 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:20
28 4 4 0 17 42 0
6302 6914 3984 0 0.1 0 0|0|0 28
11:06:21
3 1 0 0 2 5 0
6302 6914 3984 0 0 0 0|0|0 27
11:06:22
10 9 5 3 12 24 0
6302 6914 3984 0 0.1 0 0|0|0 26
11:06:23
11 4 5 0 12 23 0
6302 6914 3984 0 0.1 0 0|0|0 25
11:06:24
0 0 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:25
0 2 0 0 0 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:26
insert/s query/s update/s delete/s getmore/s command/s flushes/s
mapped vsize res faults/s locked % idx miss % q t|r|w
conn time
0 4 0 0 1 2 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:27
0 8 1 0 2 9 0
6302 6914 3984 0 0 0 0|0|0 25
11:06:28
14 10 1 0 8 21 0
6302 6914 3984 0 0 0 0|0|0 26
11:06:29
Thu Aug 19 11:06:30 MessagingPort recv() errno:104 Connection reset by
peer 127.0.0.1:27017
Thu Aug 19 11:06:30 SocketException: 9001 socket exception
can't get data: DBClientBase::findOne: transport error
Thu Aug 19 11:06:31 trying reconnect to 127.0.0.1
Thu Aug 19 11:06:31 reconnect 127.0.0.1 failed couldn't connect to
server 127.0.0.1}
Thu Aug 19 11:06:31 MessagingPort say send() errno:9 Bad file
descriptor 127.0.0.1:27017
can't get data: socket exception
On Aug 19, 3:32 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> Can you send some more info about types of operations you're doing?
>
> A sample mongostat output would be great
>
>
>
> On Thu, Aug 19, 2010 at 5:32 AM, odo <android...@googlemail.com> wrote:
> > Hi,
>
> > I am experiencing segmentation faults every few hours with moderate
> > load.
> > Here is my setup:
>
> > Ubuntu 10.04.1 LTS
>
> > mongod --version
> > db version v1.6.0, pdfile version 4.5
> > Thu Aug 19 09:17:37 git version:
> > 2c7f164b653f0d703947572ede064aed41cc2185
>
odo
Aug 23, 2010, 4:49:44 AM8/23/10
to mongodb-user
I have some details to add that might be helpful:
This happens in a replica set with two nodes, the segmentation fault
always occurs on the machine which is the master at that time.
The timely distribution roughly coincides with traffic.
Please let me know if there is any more information I can provide in
order to resolve this.
This happens in a replica set with two nodes, the segmentation fault
always occurs on the machine which is the master at that time.
The timely distribution roughly coincides with traffic.
Please let me know if there is any more information I can provide in
order to resolve this.
Eliot Horowitz
Aug 23, 2010, 7:43:06 AM8/23/10
to mongod...@googlegroups.com
I think we've found this issue.
Can you try the 1.6 nightly tomorrow?
Can you try the 1.6 nightly tomorrow?
odo
Aug 24, 2010, 3:41:00 AM8/24/10
to mongodb-user
That sounds encouraging.
At first glance the two tickets cited in the latest commits
(SERVER-1663 and SERVER-1661) do not seem to be related to the
problem.
Did the fix make it into the build?
At first glance the two tickets cited in the latest commits
(SERVER-1663 and SERVER-1661) do not seem to be related to the
problem.
Did the fix make it into the build?
Eliot Horowitz
Aug 24, 2010, 8:40:16 AM8/24/10
to mongod...@googlegroups.com
The potential fix is in the regular nightly.
There aren't cases for the fixes yet.
There aren't cases for the fixes yet.
odo
Aug 25, 2010, 3:44:04 AM8/25/10
to mongodb-user
We installed the nightly build but to no avail. We are still seeing
the segmentation faults:
Mon Aug 23 15:05:09 Got signal: 11 (Segmentation fault).
Mon Aug 23 15:05:09 Backtrace:
0x815f59 0x7f4670a83af0 0x53b81c 0x535f42 0x819041 0x82bcb0
0x7f46715879ca 0x7f4670b366fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f4670a83af0]
/usr/bin/
mongod(_ZNSt8_Rb_treeIPN5mongo13MessagingPortES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE5eraseERKS2_
+0x3c) [0x53b81c]
/usr/bin/mongod(_ZN5mongo13MessagingPortD0Ev+0x72) [0x535f42]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0xda1)
[0x819041]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f46715879ca]
/lib/libc.so.6(clone+0x6d) [0x7f4670b366fd]
_____
Mon Aug 23 15:05:10 Got signal: 11 (Segmentation fault).
Mon Aug 23 15:05:10 Backtrace:
0x815f59 0x7f4670a83af0 0x82af27 0x4e3861 0x818f5f 0x82bcb0
0x7f46715879ca 0x7f4670b366fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f4670a83af0]
/usr/bin/mongod(_ZN5boost6detail12get_tss_dataEPKv+0x27) [0x82af27]
/usr/bin/mongod(_ZN5mongo9Logstream3getEv+0x31) [0x4e3861]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0xcbf)
[0x818f5f]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f46715879ca]
/lib/libc.so.6(clone+0x6d) [0x7f4670b366fd]
_____
Tue Aug 24 05:44:20 Backtrace:
0x815f59 0x7f98fdc4caf0 0x5ffe20 0x70010b 0x702303 0x8185bf 0x82bcb0
0x7f98fe7509ca 0x7f98fdcff6fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f98fdc4caf0]
/usr/bin/mongod(_ZN5mongo14processGetMoreEPKcixRNS_5CurOpEiRb+0x60)
[0x5ffe20]
/usr/bin/
mongod(_ZN5mongo15receivedGetMoreERNS_10DbResponseERNS_7MessageERNS_5CurOpE
+0x23b) [0x70010b]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x15a3) [0x702303]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f98fe7509ca]
/lib/libc.so.6(clone+0x6d) [0x7f98fdcff6fd]
_____
Tue Aug 24 12:12:03 Got signal: 11 (Segmentation fault).
Tue Aug 24 12:12:03 Backtrace:
0x815f59 0x7fd216287af0 0x7fd2162cef13 0x7fd2162d058e 0x7fd216b3c26d
0x5fb679 0x6fca0a 0x7022ee 0x8185bf 0x82bcb0 0x7fd216d8b9ca
0x7fd21633a6fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7fd216287af0]
/lib/libc.so.6(+0x7af13) [0x7fd2162cef13]
/lib/libc.so.6(__libc_malloc+0x6e) [0x7fd2162d058e]
/usr/lib/libstdc++.so.6(_Znwm+0x1d) [0x7fd216b3c26d]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x39) [0x5fb679]
/usr/bin/mongod() [0x6fca0a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
/lib/libc.so.6(clone+0x6d) [0x7fd21633a6fd]
_____
Tue Aug 24 22:42:06 Got signal: 11 (Segmentation fault).
Tue Aug 24 22:42:06 Backtrace:
0x813389 0x7fde5008eaf0 0x7fde500e208a 0x611993 0x611d7c 0x612665
0x72ec96 0x73ce27 0x73d7a2 0x73d9f5 0x73e307 0x5faeb9 0x6fac5a
0x6fe814 0x815242 0x8290d0 0x7fde50b929ca 0x7fde501416fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x813389]
/lib/libc.so.6(+0x33af0) [0x7fde5008eaf0]
/lib/libc.so.6(memcpy+0x42a) [0x7fde500e208a]
/usr/bin/
mongod(_ZN5mongo22fillQueryResultFromObjERNS_10BufBuilderEPNS_12FieldMatcherERNS_7BSONObjEPNS_7DiskLocE
+0xb03) [0x611993]
/usr/bin/mongod(_ZN5mongo11UserQueryOp6finishEb+0x1fc) [0x611d7c]
/usr/bin/mongod(_ZN5mongo11UserQueryOp4nextEv+0x2f5) [0x612665]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner6nextOpERNS_7QueryOpE
+0x56) [0x72ec96]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner3runEv+0x6f7)
[0x73ce27]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet5runOpERNS_7QueryOpE+0x232)
[0x73d7a2]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner9runOpOnceERNS_7QueryOpE
+0x65) [0x73d9f5]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner5runOpERNS_7QueryOpE+0x17)
[0x73e307]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x959) [0x5faeb9]
/usr/bin/mongod() [0x6fac5a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x14d4) [0x6fe814]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x312)
[0x815242]
/usr/bin/mongod(thread_proxy+0x80) [0x8290d0]
/lib/libpthread.so.0(+0x69ca) [0x7fde50b929ca]
/lib/libc.so.6(clone+0x6d) [0x7fde501416fd]
the segmentation faults:
Mon Aug 23 15:05:09 Got signal: 11 (Segmentation fault).
Mon Aug 23 15:05:09 Backtrace:
0x815f59 0x7f4670a83af0 0x53b81c 0x535f42 0x819041 0x82bcb0
0x7f46715879ca 0x7f4670b366fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f4670a83af0]
/usr/bin/
mongod(_ZNSt8_Rb_treeIPN5mongo13MessagingPortES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE5eraseERKS2_
+0x3c) [0x53b81c]
/usr/bin/mongod(_ZN5mongo13MessagingPortD0Ev+0x72) [0x535f42]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0xda1)
[0x819041]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f46715879ca]
/lib/libc.so.6(clone+0x6d) [0x7f4670b366fd]
_____
Mon Aug 23 15:05:10 Got signal: 11 (Segmentation fault).
Mon Aug 23 15:05:10 Backtrace:
0x815f59 0x7f4670a83af0 0x82af27 0x4e3861 0x818f5f 0x82bcb0
0x7f46715879ca 0x7f4670b366fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f4670a83af0]
/usr/bin/mongod(_ZN5boost6detail12get_tss_dataEPKv+0x27) [0x82af27]
/usr/bin/mongod(_ZN5mongo9Logstream3getEv+0x31) [0x4e3861]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0xcbf)
[0x818f5f]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f46715879ca]
/lib/libc.so.6(clone+0x6d) [0x7f4670b366fd]
_____
Tue Aug 24 05:44:20 Backtrace:
0x815f59 0x7f98fdc4caf0 0x5ffe20 0x70010b 0x702303 0x8185bf 0x82bcb0
0x7f98fe7509ca 0x7f98fdcff6fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7f98fdc4caf0]
/usr/bin/mongod(_ZN5mongo14processGetMoreEPKcixRNS_5CurOpEiRb+0x60)
[0x5ffe20]
/usr/bin/
mongod(_ZN5mongo15receivedGetMoreERNS_10DbResponseERNS_7MessageERNS_5CurOpE
+0x23b) [0x70010b]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x15a3) [0x702303]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7f98fe7509ca]
/lib/libc.so.6(clone+0x6d) [0x7f98fdcff6fd]
_____
Tue Aug 24 12:12:03 Got signal: 11 (Segmentation fault).
Tue Aug 24 12:12:03 Backtrace:
0x815f59 0x7fd216287af0 0x7fd2162cef13 0x7fd2162d058e 0x7fd216b3c26d
0x5fb679 0x6fca0a 0x7022ee 0x8185bf 0x82bcb0 0x7fd216d8b9ca
0x7fd21633a6fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x815f59]
/lib/libc.so.6(+0x33af0) [0x7fd216287af0]
/lib/libc.so.6(+0x7af13) [0x7fd2162cef13]
/lib/libc.so.6(__libc_malloc+0x6e) [0x7fd2162d058e]
/usr/lib/libstdc++.so.6(_Znwm+0x1d) [0x7fd216b3c26d]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x39) [0x5fb679]
/usr/bin/mongod() [0x6fca0a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x158e) [0x7022ee]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libpthread.so.0(+0x69ca) [0x7fd216d8b9ca]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x31f)
[0x8185bf]
/usr/bin/mongod(thread_proxy+0x80) [0x82bcb0]
/lib/libc.so.6(clone+0x6d) [0x7fd21633a6fd]
_____
Tue Aug 24 22:42:06 Got signal: 11 (Segmentation fault).
Tue Aug 24 22:42:06 Backtrace:
0x813389 0x7fde5008eaf0 0x7fde500e208a 0x611993 0x611d7c 0x612665
0x72ec96 0x73ce27 0x73d7a2 0x73d9f5 0x73e307 0x5faeb9 0x6fac5a
0x6fe814 0x815242 0x8290d0 0x7fde50b929ca 0x7fde501416fd
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x813389]
/lib/libc.so.6(+0x33af0) [0x7fde5008eaf0]
/lib/libc.so.6(memcpy+0x42a) [0x7fde500e208a]
/usr/bin/
mongod(_ZN5mongo22fillQueryResultFromObjERNS_10BufBuilderEPNS_12FieldMatcherERNS_7BSONObjEPNS_7DiskLocE
+0xb03) [0x611993]
/usr/bin/mongod(_ZN5mongo11UserQueryOp6finishEb+0x1fc) [0x611d7c]
/usr/bin/mongod(_ZN5mongo11UserQueryOp4nextEv+0x2f5) [0x612665]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner6nextOpERNS_7QueryOpE
+0x56) [0x72ec96]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner3runEv+0x6f7)
[0x73ce27]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet5runOpERNS_7QueryOpE+0x232)
[0x73d7a2]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner9runOpOnceERNS_7QueryOpE
+0x65) [0x73d9f5]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner5runOpERNS_7QueryOpE+0x17)
[0x73e307]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x959) [0x5faeb9]
/usr/bin/mongod() [0x6fac5a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x14d4) [0x6fe814]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x312)
[0x815242]
/usr/bin/mongod(thread_proxy+0x80) [0x8290d0]
/lib/libpthread.so.0(+0x69ca) [0x7fde50b929ca]
/lib/libc.so.6(clone+0x6d) [0x7fde501416fd]
Eliot Horowitz
Aug 25, 2010, 7:49:27 AM8/25/10
to mongod...@googlegroups.com
Can you send the startup banner so we can make sure its the right version?
Also - can you run a repair with the new version.
Also - can you run a repair with the new version.
odo
Aug 30, 2010, 6:30:37 AM8/30/10
to mongodb-user
"mongod --version" gives me:
db version v1.6.2-pre-, pdfile version 4.5
Mon Aug 30 10:28:13 git version:
0e78196fd59c067933b36aa4f0021b73158ef545
db version v1.6.2-pre-, pdfile version 4.5
Mon Aug 30 10:28:13 git version:
0e78196fd59c067933b36aa4f0021b73158ef545
odo
Aug 30, 2010, 9:33:06 AM8/30/10
to mongodb-user
We experienced another rather annoying variation of the problem:
After the segmentation fault, the server kept accepting connections
but never ended them, wreaked havoc across the application layer.
Thu Aug 26 17:09:28 [conn12374] end connection 10.0.235.149:52815
Thu Aug 26 17:09:28 [initandlisten] connection accepted from
10.0.235.149:52816 #12375
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.146:34996 #12376
Thu Aug 26 17:09:30 [conn12376] end connection 10.0.235.146:34996
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.146:34997 #12377
Thu Aug 26 17:09:30 [conn12347] end connection 10.0.235.149:52800
Thu Aug 26 17:09:30 [conn11859] killcursors: found 0 of 1
Thu Aug 26 17:09:30 [conn12371] end connection 10.0.235.138:49888
Thu Aug 26 17:09:30 [conn12375] end connection 10.0.235.149:52816
Thu Aug 26 17:09:30 [conn12377] end connection 10.0.235.146:34997
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.143:45299 #12378
Thu Aug 26 17:09:30 [conn12378] end connection 10.0.235.143:45299
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.143:45300 #12379
Thu Aug 26 17:09:30 Got signal: 11 (Segmentation fault).
Thu Aug 26 17:09:30 Got signal: 6 (Aborted).
Thu Aug 26 17:09:30 Got signal: 11 (Segmentation fault).
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.149:52825 #12380
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.149:52826 #12381
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.139:34275 #12382
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.139:34276 #12383
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.147:40117 #12384
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.147:40118 #12385
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.145:35476 #12386
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.145:35477 #12387
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.141:52554 #12388
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.141:52555 #12389
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.144:52055 #12390
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.144:52056 #12391
Thu Aug 26 17:09:34 [initandlisten] connection accepted from
10.0.235.96:33422 #12392
Thu Aug 26 17:09:34 [initandlisten] connection accepted from
10.0.235.96:33423 #12393
Thu Aug 26 17:09:35 [initandlisten] connection accepted from
10.0.235.137:47592 #12394
Thu Aug 26 17:09:35 [initandlisten] connection accepted from
10.0.235.137:47593 #12395
After the segmentation fault, the server kept accepting connections
but never ended them, wreaked havoc across the application layer.
Thu Aug 26 17:09:28 [conn12374] end connection 10.0.235.149:52815
Thu Aug 26 17:09:28 [initandlisten] connection accepted from
10.0.235.149:52816 #12375
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.146:34996 #12376
Thu Aug 26 17:09:30 [conn12376] end connection 10.0.235.146:34996
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.146:34997 #12377
Thu Aug 26 17:09:30 [conn12347] end connection 10.0.235.149:52800
Thu Aug 26 17:09:30 [conn11859] killcursors: found 0 of 1
Thu Aug 26 17:09:30 [conn12371] end connection 10.0.235.138:49888
Thu Aug 26 17:09:30 [conn12375] end connection 10.0.235.149:52816
Thu Aug 26 17:09:30 [conn12377] end connection 10.0.235.146:34997
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.143:45299 #12378
Thu Aug 26 17:09:30 [conn12378] end connection 10.0.235.143:45299
Thu Aug 26 17:09:30 [initandlisten] connection accepted from
10.0.235.143:45300 #12379
Thu Aug 26 17:09:30 Got signal: 11 (Segmentation fault).
Thu Aug 26 17:09:30 Got signal: 6 (Aborted).
Thu Aug 26 17:09:30 Got signal: 11 (Segmentation fault).
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.149:52825 #12380
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.149:52826 #12381
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.139:34275 #12382
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.139:34276 #12383
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.147:40117 #12384
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.147:40118 #12385
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.145:35476 #12386
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.145:35477 #12387
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.141:52554 #12388
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.141:52555 #12389
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.144:52055 #12390
Thu Aug 26 17:09:31 [initandlisten] connection accepted from
10.0.235.144:52056 #12391
Thu Aug 26 17:09:34 [initandlisten] connection accepted from
10.0.235.96:33422 #12392
Thu Aug 26 17:09:34 [initandlisten] connection accepted from
10.0.235.96:33423 #12393
Thu Aug 26 17:09:35 [initandlisten] connection accepted from
10.0.235.137:47592 #12394
Thu Aug 26 17:09:35 [initandlisten] connection accepted from
10.0.235.137:47593 #12395
Eliot Horowitz
Aug 30, 2010, 9:40:41 AM8/30/10
to mongod...@googlegroups.com
The fix is only in the regular nightly so far.
odo
Sep 1, 2010, 4:12:14 AM9/1/10
to mongodb-user
We are now on
db version v1.7.0-pre-, pdfile version 4.5
Wed Sep 1 08:07:19 git version:
387e0e4fcdb3498fc84f3f5386a15e450ea4c5f1
and it works without problems so far. Thanks for resolving this.
It would be great if this fix could be backported to the 1.6 branch,
it does not feel good to have the development branch running in
production. Is there a Jira-ticket I can watch?
Best,
Florian
On Aug 30, 3:40 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> The fix is only in the regular nightly so far.
>
> Can you tryhttp://downloads.mongodb.org/linux/mongodb-linux-x86_64-latest.tgz
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsubscribe@google groups.com>
> > .
> > .
> > .
> > .
db version v1.7.0-pre-, pdfile version 4.5
Wed Sep 1 08:07:19 git version:
387e0e4fcdb3498fc84f3f5386a15e450ea4c5f1
and it works without problems so far. Thanks for resolving this.
It would be great if this fix could be backported to the 1.6 branch,
it does not feel good to have the development branch running in
production. Is there a Jira-ticket I can watch?
Best,
Florian
On Aug 30, 3:40 pm, Eliot Horowitz <eliothorow...@gmail.com> wrote:
> The fix is only in the regular nightly so far.
>
> > .
> > > >> >> > For more options, visit this group athttp://
> > groups.google.com/group/mongodb-user?hl=en.
>
> > groups.google.com/group/mongodb-user?hl=en.
>
> > > >> > --
> > > >> > You received this message because you are subscribed to the Google
> > Groups "mongodb-user" group.
> > > >> > To post to this group, send email to mongod...@googlegroups.com.
> > > >> > To unsubscribe from this group, send email to
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsubscribe@google groups.com>
> > > >> > You received this message because you are subscribed to the Google
> > Groups "mongodb-user" group.
> > > >> > To post to this group, send email to mongod...@googlegroups.com.
> > > >> > To unsubscribe from this group, send email to
> > .
> > > >> > For more options, visit this group athttp://
> > groups.google.com/group/mongodb-user?hl=en.
>
> > groups.google.com/group/mongodb-user?hl=en.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups "mongodb-user" group.
> > > > To post to this group, send email to mongod...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsubscribe@google groups.com>
> > > > You received this message because you are subscribed to the Google
> > Groups "mongodb-user" group.
> > > > To post to this group, send email to mongod...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > .
> > > > For more options, visit this group athttp://
> > groups.google.com/group/mongodb-user?hl=en.
>
> > groups.google.com/group/mongodb-user?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mongodb-user" group.
> > To post to this group, send email to mongod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsubscribe@google groups.com>
> > You received this message because you are subscribed to the Google Groups
> > "mongodb-user" group.
> > To post to this group, send email to mongod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
Eliot Horowitz
Sep 1, 2010, 8:02:43 AM9/1/10
to mongod...@googlegroups.com
The 2 fixes we think fixed this are going in 1.6.2 coming out today
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages