[SERVER-10003] AssertionException handling request, closing client connection: 16141 cannot translate opcode 17747 Created: 24/Jun/13  Updated: 01/Dec/15  Resolved: 19/Dec/13

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

Type: Bug Priority: Critical - P2
Reporter: Venkat Reddimachu Assignee: Siyuan Zhou
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux greendb308p.prod.ch3.s.com 2.6.32-358.0.1.el6.x86_64 #1 SMP Wed Feb 27 06:06:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux


Issue Links:
Duplicate
is duplicated by SERVER-10132 MONGO - ASSERTION ERROR Closed
is duplicated by SERVER-21712 AssertionException handling request, ... Closed
Operating System: Linux
Participants:

 Description   

We were keep getting these messages multiple times from this early morning and so would like to know that anything needs to be fixed on db end:

 
Mon Jun 24 08:01:43.259 [conn68987] recv(): message len 1414876743 is too large. Max is 48000000
Mon Jun 24 08:01:43.259 [conn68987] end connection 10.235.36.42:60554 (92 connections now open)
Mon Jun 24 08:01:43.311 [conn68980] recv(): message len 223496516 is too large. Max is 48000000
Mon Jun 24 08:01:43.311 [conn68980] end connection 10.235.36.42:60547 (91 connections now open)
Mon Jun 24 08:01:43.363 [conn68981] recv(): message len -822083581 is too large. Max is 48000000
Mon Jun 24 08:01:43.363 [conn68981] end connection 10.235.36.42:60548 (90 connections now open)
Mon Jun 24 08:01:43.415 [conn68982] OpCounters::gotOp unknown op: 17747
Mon Jun 24 08:01:43.415 [conn68982] Assertion: 16141:cannot translate opcode 17747
0xdcf361 0xd90a1b 0xd90f5c 0x9f6342 0x6e747a 0xdbbb7e 0x3d80c07851 0x3d808e890d
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xdcf361]
 /usr/bin/mongod(_ZN5mongo11msgassertedEiPKc+0x9b) [0xd90a1b]
 /usr/bin/mongod() [0xd90f5c]
 /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xef2) [0x9f6342]
 /usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x9a) [0x6e747a]
 /usr/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x42e) [0xdbbb7e]
 /lib64/libpthread.so.0() [0x3d80c07851]
 /lib64/libc.so.6(clone+0x6d) [0x3d808e890d]
Mon Jun 24 08:01:43.417 [conn68982] AssertionException handling request, closing client connection: 16141 cannot translate opcode 17747
Mon Jun 24 08:01:43.467 [conn68983] recv(): message len 1702131056 is too large. Max is 48000000
Mon Jun 24 08:01:43.467 [conn68983] end connection 10.235.36.42:60550 (88 connections now open)
Mon Jun 24 08:01:43.519 [conn68984] recv(): message len 1952543859 is too large. Max is 48000000 



 Comments   
Comment by Siyuan Zhou [ 19/Dec/13 ]

Since we haven't heard from you for a while, I will mark this issue as resolved. Please don't hesitate to get back to us with the requested information.

Comment by Siyuan Zhou [ 08/Nov/13 ]

Hi Venkat,

As dan@10gen.com mentioned, the error message indicates the actual message is garbled. For example, "cannot translate opcode" here in the code shows the operation is not understood by the server.

You mentioned this issue kept coming on regular intervals. How often does it happen? Did you observe any other pattern on the server and on the client side? It would be great if we could have more information to reproduce this issue. Once we could reproduce it, I believe mongosniff will give more insights into this problem by monitoring the traffic.

Comment by Venkat Reddimachu [ 19/Aug/13 ]

Steve,
We still have this issue and it is keep coming on regular intervals and if you provide any other suggestions that would be appreciated.

Mon Aug 19 10:38:30.751 [conn98692] Assertion: 16141:cannot translate opcode 17747
0xdcf361 0xd90a1b 0xd90f5c 0x9f6342 0x6e747a 0xdbbb7e 0x3d80c07851 0x3d808e890d
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xdcf361]
/usr/bin/mongod(_ZN5mongo11msgassertedEiPKc+0x9b) [0xd90a1b]
/usr/bin/mongod() [0xd90f5c]
/usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xef2) [0x9f6342]
/usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x9a) [0x6e747a]
/usr/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x42e) [0xdbbb7e]
/lib64/libpthread.so.0() [0x3d80c07851]
/lib64/libc.so.6(clone+0x6d) [0x3d808e890d]
Mon Aug 19 10:38:30.761 [conn98692] AssertionException handling request, closing client connection: 16141 cannot translate opcode 17747
Mon Aug 19 10:38:30.803 [conn98693] recv(): message len 1702131056 is too large. Max is 48000000

Thanks,
Venkat

Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ]

Hi Venkat,

Are you still seeing these error messages, or have you been able to resolve the problem?

Regards,
Stephen

Comment by Venkat Reddimachu [ 09/Jul/13 ]

Following is the Java driver version:

Java driver version 2.11.0

Comment by Venkat Reddimachu [ 08/Jul/13 ]

I have posted mongo server version and will provide client details asap.

Comment by Venkat Reddimachu [ 08/Jul/13 ]

MongoDB shell version: 2.4.3

Comment by Daniel Pasette (Inactive) [ 28/Jun/13 ]

This actually looks like there is something wrong on your client side. The error messages indicate that the actual message is garbled. Can you provide your mongodb server version number as well as details regarding your client application and driver language and version?

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