Assertion: 10334:Invalid BSONObj size

[Michael]

Hello.

I see this error on secondary once in an hour:

Thu May 26 10:58:17 [conn1193] Assertion: 10334:Invalid BSONObj size:
1635873339 (0x3B728161) first element: .0: ?type=-105
Thu May 26 10:58:17 [conn1193] assertion 10334 Invalid BSONObj size:
1635873339 (0x3B728161) first element: .0: ?type=-105
ns:local.oplog.rs query:{ ts: { $gt: Times
tamp 1306407480000|220 } }
Thu May 26 10:58:17 [conn1193] query local.oplog.rs exception 13818ms

I don't see this error on primary. According to this thread:
http://groups.google.com/group/mongodb-user/browse_thread/thread/78f788e4bb59251

it can be due to problem on oplog of the primary. Is there a way how
to fix this error without downtime?

[Tony Hannan]

This usually due to some kind of corruption. Have you had any unclean shutdowns? Are you running with --journal? What mongo version? Have you wrote any non-utf8 strings? Which driver and version? Can you think of anything that is happening once an hour when the error happens?

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

[Tony Hannan]

Can you post primary and secondary logs (to pastebin for example) and the result of rs.status()?

[Michael]

Mongodb 1.8.1 with journaling both on primary and secondary. Probably
had unclean shutdown long time ago. Additionally i had this problem:
http://groups.google.com/group/mongodb-user/browse_thread/thread/42c679597832ee2c

status and logs +- minute around error:
http://pastebin.com/r7XPPmHg

[k]

That's very weird... this happens exactly once an hour?

Also, in the log you pasted, the lines are:

Thu May 26 18:58:00 [initandlisten] connection accepted from
secondary.server:34840 #1785
Thu May 26 18:58:12 [conn1785] Assertion: 10334:Invalid BSONObj size:
1937059444 (0x742E7573) first element: rs: ?type=101
Thu May 26 18:58:12 [conn1785] assertion 10334 Invalid BSONObj size:
1937059444 (0x742E7573) first element: rs: ?type=101 ns:local.oplog.rs
query:{ ts: { $gt: Timest
Thu May 26 18:58:12 [conn1785] query local.oplog.rs exception 8274ms
Thu May 26 18:58:12 [conn1785] end connection secondary.server:34840

Is the connection actually from the secondary server to the secondary
server? (Totally possible, just making sure it wasn't a search/
replace error.)

What version are you using?

On May 26, 5:38 pm, Michael <m...@mzlab.net> wrote:
> Mongodb 1.8.1 with journaling both on primary and secondary. Probably

> had unclean shutdown long time ago. Additionally i had this problem:http://groups.google.com/group/mongodb-user/browse_thread/thread/42c6...

[Michael]

Yes the connection is from secondary, i found out that it happens
during backup with the help of mongodump --oplog, that's why it's once
per hour.

It's mongodb 1.8.1

[Michael]

1) I made a whole db resync, but that didn't help
2) I made a repair of local db on the secondary, that didn't help too
3) I remembered, that i have too big keys in DB:
Wed May 25 10:35:41 [replica set sync] myproj Btree::insert: key too
large to index, skipping myproj.users.$email_1 2069 { : "....." }
i removed them, made a resync, and it seems that this error gone.

On May 26, 2:12 pm, Michael <m...@mzlab.net> wrote:
> Hello.
>
> I see this error on secondary once in an hour:
>
> Thu May 26 10:58:17 [conn1193] Assertion: 10334:Invalid BSONObj size:
> 1635873339 (0x3B728161) first element: .0: ?type=-105
> Thu May 26 10:58:17 [conn1193] assertion 10334 Invalid BSONObj size:
> 1635873339 (0x3B728161) first element: .0: ?type=-105
> ns:local.oplog.rs query:{ ts: { $gt: Times
> tamp 1306407480000|220 } }
> Thu May 26 10:58:17 [conn1193] query local.oplog.rs exception  13818ms
>

> I don't see this error on primary. According to this thread:http://groups.google.com/group/mongodb-user/browse_thread/thread/78f7...