On Tue, Oct 9, 2012 at 8:27 PM, WennY <
ant...@mail.ru> wrote:
> Hello. When i try to connect, my php said: "PHP Fatal error: Uncaught
> exception 'MongoCursorException' with message 'couldn't send query: [here
> broken encoding]". Sure, it is not php problem. I think problem in mongo
> connections. In the log I found the following:
> if we have exception, in log we may see:
> Wed Oct 10 07:03:15 [initandlisten] connection accepted from
127.0.0.1:60305
> #9
> Wed Oct 10 07:03:15 [conn9] end connection
127.0.0.1:60305
>
> but if we have valid connection we always see:
> Wed Oct 10 07:03:15 [initandlisten] connection accepted from
127.0.0.1:60306
> #10
> Wed Oct 10 07:03:16 [conn10] killcursors: found 0 of 1
> Wed Oct 10 07:03:16 [conn10] end connection
127.0.0.1:60306
We apparently don't kill the cursor when we encounter bad data... It
shouldn't cause any issues though.
We have seen this couple of times in virtualised environments, and we
suspect something is corrupting the network traffic...
Could you try to repair the database (using db.repairDatabase() from
the shell)? Note that it could take some time if you have a lot of
data.
You may want to try just validating the collection first (using
db.collectionName.validate(true)).
That should atleast make sure the database itself isn't at fault :)
-Hannes