Priority: Normal
Current State: Closed
Released In: n/a
Target Release: n/a
The full log entry from the
MongoDB side is attached.
I've seen it happen prior to my recent m4 update but now appears to be happening very regularly.
This can even cause
MongoDB to segfault.
This error message is the target of this bug item, but came from a long running series of observations noted in
Item10672.
I am turning up verbose logging as
advised by Scott.
Apparently we've got periods in the db names. Can we filter them out? Scott seems to think they're a problem.
--
PaulHarvey - 09 May 2011
I'm pretty sure the cause is the same as
Item10670. In fact, these may be considered duplicates, perhaps.
--
PaulHarvey - 13 May 2011
Here's one:
TaxonProfile/Definitions.FlOz_VolumeFigure: SEARCH{"(form.name='TaxonProfile.Relati
onships.RelationshipForm' OR form.name='TaxonProfile/Relationships.RelationshipForm' OR form.name='TaxonProfile/Relationships/Re
lationshipForm' OR form.name='TaxonProfile.Relationships/RelationshipForm' OR form.name='RelationshipForm') AND
Source/Namespace = 'WC' AND Destination/Namespace = 'WC'
--
PaulHarvey - 18 May 2011
Also getting a lot of
SEARCH crash: System.DefaultWidgets: SEARCH{"1"...
Caused the following error:
Can't call method "getRevisionInfo" on unblessed reference
Even with mongo disabled
--
PaulHarvey - 18 May 2011
This is waiting on me to build the courage to turn off my memory-leak safeguards on the production site (daily restart, custom mongod with 8M -> 128M memory JS engine). And then to try to invent a test-case which is reproducible for the 10gen guys to work with.
--
PaulHarvey - 01 Jun 2011
Less urgent now - we run with mongod 1.9 (development releases), which doesn't seem to fall over even after a week between restarts.
--
PaulHarvey - 07 Jul 2011
This task seems to have run its course. Closing. See also
Item10672
--
PaulHarvey - 05 Sep 2011