killOp causes server failure on MongoDB 1.6.3

[Christoph Preissner]

I had this process:

{
"opid" : 333298,
"active" : true,
"lockType" : "read",
"waitingForLock" : true,
"secs_running" : 408,
"op" : "query",
"ns" : "stream.s_1234",
"query" : {
"count" : "s_1234",
"query" : {
"oid" : NumberLong(777),
"ot" : 1
}
},
"client" : "0.0.0.0:0",
"desc" : "conn"
}

I tried to kill it with "db.killOp(333298)":

db.killOp(333298)
{ "info" : "attempting to kill op" }
> db.killOp(333298)
Fri Oct 15 16:00:40 query failed : stream.$cmd.sys.killop { op:
333298.0 } to: 127.0.0.1
Fri Oct 15 16:00:40 Error: error doing query: failed (anon):1509

causing the following logs, and a server shutdown:

Fri Oct 15 16:00:31 [conn598] going to kill op: op: 333298.0
Fri Oct 15 16:00:32 [conn611] Count with ns: stream.s_1234 and query:
{ oid: 777, ot: 1 } failed with exception: exception: 11601
interrupted
Fri Oct 15 16:00:32 [conn611] query stream.$cmd ntoreturn:1 command:
{ count: "s_1234", query: { oid: 777, ot: 1 } } reslen:64 414956ms
warning: hit on in-active ProgressMeter
Fri Oct 15 16:00:32 Got signal: 8 (Floating point exception).

Fri Oct 15 16:00:32 Backtrace:
0x8212f9 0x7fc32a7bf1e0 0x760bcd 0x794c07 0x796028 0x5fb775 0x60022f
0x70547a 0x708ab6 0x8235ef 0x837460 0x7fc32b2a18ba 0x7fc32a85c02d
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x8212f9]
/lib/libc.so.6(+0x321e0) [0x7fc32a7bf1e0]
/usr/bin/
mongod(_ZN5mongo2mr16MapReduceCommand3runERKSsRNS_7BSONObjERSsRNS_14BSONObjBuilderEb
+0x79d) [0x760bcd]
/usr/bin/
mongod(_ZN5mongo11execCommandEPNS_7CommandERNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb
+0x597) [0x794c07]
/usr/bin/
mongod(_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_10BufBuilderERNS_14BSONObjBuilderEbi
+0x798) [0x796028]
/usr/bin/
mongod(_ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_10BufBuilderERNS_14BSONObjBuilderEbi
+0x35) [0x5fb775]
/usr/bin/
mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_
+0x1bbf) [0x60022f]
/usr/bin/mongod() [0x70547a]
/usr/bin/
mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE
+0x14d6) [0x708ab6]
/usr/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x30f)
[0x8235ef]
/usr/bin/mongod(thread_proxy+0x80) [0x837460]
/lib/libpthread.so.0(+0x68ba) [0x7fc32b2a18ba]
/lib/libc.so.6(clone+0x6d) [0x7fc32a85c02d]

Fri Oct 15 16:00:32 dbexit:

Fri Oct 15 16:00:32 [conn611] shutdown: going to close listening
sockets...
Fri Oct 15 16:00:32 [conn611] closing listening socket: 11
Fri Oct 15 16:00:32 [conn611] closing listening socket: 12
Fri Oct 15 16:00:32 [conn611] closing listening socket: 13
Fri Oct 15 16:00:32 [conn611] closing listening socket: 14
Fri Oct 15 16:00:32 [conn611] shutdown: going to flush oplog...
Fri Oct 15 16:00:32 [conn611] shutdown: going to close sockets...
Fri Oct 15 16:00:32 [conn611] shutdown: waiting for fs preallocator...
Fri Oct 15 16:00:32 [conn611] shutdown: closing all files...
Fri Oct 15 16:00:32 closeAllFiles() finished

Fri Oct 15 16:00:32 [conn611] shutdown: removing fs lock...
Fri Oct 15 16:00:32 dbexit: really exiting now
Fri Oct 15 16:00:32 ERROR: Client::~Client _context should be null but
is not; client:conn

[Dwight Merriman]

looks like a bug

can you make a jira for it?  jira.mongodb.org

tx

--
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.