recv(): message len xxx is too large

[D Boyd]

All:
I am using 1.8.164bit on a windows 7 64bit system.
In a number of my scripts/programsI am getting the the following
message is too large from the mongo shell:

Tue Apr 26 22:06:20 recv(): message len -788499871 is too
large-788499871
Tue Apr 26 22:06:20 Error: dbclient error communicating with server:
127.0.0.1 s
hell/query.js:104Tue Apr 26 22:06:20 recv(): message len -788499871 is
too large-788499871
Tue Apr 26 22:06:20 Error: dbclient error communicating with server:
127.0.0.1 s
hell/query.js:104

The size varies depending on what I am doing but the rest of the
message is the
same.

The following is how I am running the server:

David Boyd@DavidBoyd-PC /cygdrive/c/Program Files/mongodb-win32-
x86_64-1.8.1
$ bin/mongod --dbpath ./db/ --logpath data.log --logappend --journal

The following is the relevant part of the log file:

Tue Apr 26 22:23:36 [initandlisten] MongoDB starting : pid=4868
port=27017 dbpat
h=./db/ 64-bit
Tue Apr 26 22:23:36 [initandlisten] db version v1.8.1, pdfile version
4.5
Tue Apr 26 22:23:36 [initandlisten] git version:
a429cd4f535b2499cc4130b06ff7c26
f41c00f04
Tue Apr 26 22:23:36 [initandlisten] build sys info: windows (6, 1,
7600, 2, '')
BOOST_LIB_VERSION=1_42
Tue Apr 26 22:23:36 [initandlisten] journal dir=./db/journal
Tue Apr 26 22:23:36 [initandlisten] recover : no journal files
present, no recov
ery needed
Tue Apr 26 22:23:36 [initandlisten] waiting for connections on port
27017
Tue Apr 26 22:23:36 [websvr] web admin interface listening on port
28017
Tue Apr 26 22:23:53 [initandlisten] connection accepted from
127.0.0.1:49467 #1
Tue Apr 26 22:23:57 [conn1] end connection 127.0.0.1:49467
Tue Apr 26 22:24:12 [initandlisten] connection accepted from
127.0.0.1:49475 #2
Tue Apr 26 22:24:24 [conn2] CMD: drop BankData.GeneralBalance
Tue Apr 26 22:24:32 [initandlisten] connection accepted from
127.0.0.1:49476 #3
Tue Apr 26 22:24:32 [conn3] building new index on { _id: 1 } for
BankData.Genera
lBalance
Tue Apr 26 22:24:32 [conn3] done for 0 records 0.004secs
Tue Apr 26 22:24:33 [conn3] end connection 127.0.0.1:49476
Tue Apr 26 22:24:36 [dur] lsn set 59723
Tue Apr 26 22:25:20 [initandlisten] connection accepted from
127.0.0.1:49477 #4
Tue Apr 26 22:25:31 [conn4] terminating, shutdown command received
Tue Apr 26 22:25:31 dbexit: shutdown called
Tue Apr 26 22:25:31 [conn4] shutdown: going to close listening
sockets...
Tue Apr 26 22:25:31 [conn4] closing listening socket: 248
Tue Apr 26 22:25:31 [conn4] closing listening socket: 256
Tue Apr 26 22:25:31 [conn4] shutdown: going to flush diaglog...
Tue Apr 26 22:25:31 [conn4] shutdown: going to close sockets...
Tue Apr 26 22:25:31 [conn4] shutdown: waiting for fs preallocator...
Tue Apr 26 22:25:31 [conn4] shutdown: lock for final commit...
Tue Apr 26 22:25:31 [conn4] shutdown: final commit...
Tue Apr 26 22:25:31 [conn2] end connection 127.0.0.1:49475
Tue Apr 26 22:25:31 [conn4] shutdown: closing all files...
Tue Apr 26 22:25:31 closeAllFiles() finished
Tue Apr 26 22:25:31 [conn4] shutdown: journalCleanup...
Tue Apr 26 22:25:31 [conn4] removeJournalFiles
Tue Apr 26 22:25:31 [conn4] shutdown: removing fs lock...
Tue Apr 26 22:25:31 dbexit: really exiting now
~

The collection I am reading that is causing the error was loaded from
a number of
CSV files using mongoimport. There were no errors on the loading.
There are slightly more than 1M records in the collection.
The javascript I am running is trying to reformat the data and just
does a
find and loops through the cursor.

I had similar issues the other day trying to do some restores to the
same install.

[D Boyd]

More information:
The same process ran without errors on a 64bit Linux VM.
So either the problem sits with my windows system or
with the windows 1.8.1 install.

[sridhar]

Hi,
What driver/access mechanism are you using to access your data. Also
what options are you using when starting on Linux vs Windows. Can you
paste your javascript somewhere?

[sridhar]

Hi,
Are you able to export this collection using mongexport? also what do
you get if you trying validate on the offending collection. More info
on validate can be found at http://www.mongodb.org/display/DOCS/Validate+Command

[Adam C]

Grant,

For a bug we generally attempt to reproduce the problem and then fix whatever is causing it from the MongoDB perspective.  You seem to have already tested and confirmed that this is in fact not reproducible.  Hence your machine/OS/config appears to be the problem.  By proving that everything works as expected on other machines and OSes you essentially point the finger squarely at your own configuration.  We can suggest general things like turn off firewalls, check anti-virus or anti-spyware software etc. but in the end we have no way to diagnose an issue specific to your host only. 

Given that this issue only exists on your machine, and you yourself have mentioned that you have a lot of applications installed, how would you suggest we proceed to investigate further without a way to reproduce your issue?

Adam

On Saturday, November 17, 2012 8:22:46 AM UTC+11, grant li wrote:

Hi,

  I'm getting the exact same error.

D:\nodejs>mongoexport -d myDb -c terms -o output.json

connected to: 127.0.0.1

Fri Nov 16 16:09:01 recv(): message len -1988783528 is too large-1988783528

assertion: 10278 dbclient error communicating with server: 127.0.0.1:27017

I gave db file to another person. He tested the mongoexport in both windows x64 and linux x64, he was able to export the collection just fine.

The I gave db file to a third person who's using the exact same machine as mine. Windows x64 fresh install. He was able to export the collection just fine as well.

I read from other posts that some people suspect this is caused by nssize or a single collection is bigger than 16MB. That is definitely not the case here.

I don't know the exact cause, but I'm very certain that this is nothing from mongodb or from corrupted database or bad configuration.

mongodb wise, I can export this db using mongo 2.0.0 from the 2nd person's machine.

corrupted database wise, the export from another person who got db from me can export just fine, go through item by item just fine and check length just fine.

configuration wise, the other 2 person both had clean basic config.

I'm 100% sure this is some other windows setting that is causing this. But can anyone help me find out what setting/app is causing this?

I have a lot of apps installed in my machine.

And please don't tell me to reinstall or swap to linux. Stick to this issue.