Problem with 0.7x and mongo 3.0.1

[Leonardo Galani]

Hi, after i did all the upgrades (and move my nodebb to a fresh new server), everthing where just fine but this morning nodebb just crashed..

the trace with erros is kind of big.. but some of them are like

015-04-06T09:03:36.065-0400 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { expires: 1 }, name: "expires_1", ns: "nodebb.sessions", expireAfterSeconds: 0 } -- 0 assertion src/mongo/db/storage/mmap_v1/btree/key   .cpp:439
2015-04-06T09:04:36.070-0400 I -        [TTLMonitor] Assertion failure false src/mongo/db/storage/mmap_v1/btree/key.cpp 439
2015-04-06T09:04:36.081-0400 I CONTROL  [TTLMonitor]
 0xf4d299 0xeeda71 0xed301e 0xcff648 0xcf0b76 0xcea15c 0xceb937 0xa939e3 0xa0df2f 0x9ffb5c 0xbd0264 0xbd0614 0xbd0c4d 0xafd686 0xd7d675 0xd7e390 0xed52a0 0xf9b304 0x7f2804914182 0x7f28033dc47d

and when i try to repair..

2015-04-06T10:17:46.178-0400 I INDEX    [initandlisten] build index on: nodebb.sessions properties: { v: 1, key: { expires: 1 }, name: "expires_1", ns: "nodebb.sessions", expireAfterSeconds: 0 }
2015-04-06T10:17:46.178-0400 I INDEX    [initandlisten]          building index using bulk method
2015-04-06T10:17:46.196-0400 I STORAGE  [initandlisten] cleaning up failed repair db: nodebb path: /data/db/_tmp_repairDatabase_0
2015-04-06T10:17:46.204-0400 I -        [initandlisten] Fatal assertion 18506 InvalidLength record has to be >= 4 bytes
2015-04-06T10:17:46.208-0400 I CONTROL  [initandlisten]
0xf4d299 0xeeda71 0xed42fa 0x80a38b 0x7d5654 0x7fa6a25a3ec5 0x8066e7

Any clue on how to solve it?

[nhl.pl]

@Leonardo-Galani said:

015-04-06T09:03:36.065-0400 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { expires: 1 }, name: "expires_1", ns: "nodebb.sessions", expireAfterSeconds: 0 } -- 0 assertion src/mongo/db/storage/mmap_v1/btree/key   .cpp:439

First of all I'm only guessing but... TTLMonitor reports something about nodebb.sessions to expire.

I've checked it in the MongoDB docs:

Expire Data from Collections by Setting TTL — MongoDB Manual

For me it means you can safely remove sessions data.

It can be also post-upgrade issue.

Release Notes for MongoDB 2.2 — MongoDB Manual

TTL collections remove expired data from a collection, using a special index and a background thread that deletes expired documents every minute. These collections are useful as an alternative to capped collections in some cases, such as for data warehousing and caching cases, including: machine generated event data, logs, and session information that needs to persist in a database for only a limited period of time.

[Leonardo Galani]

I got my last backup and delete the collection "sessions" ... seems everthing is working............ for now.

[Leonardo Galani]

thats it.. i wish i could mark it as "resolved"