Hi folks,
I'm trying to run mongodb on my gentoo box.
So I emerged =dev-db/mongodb-2.6.7.
If I start the mongo cli client without the server running I get
$ mongo
127.0.0.1/asd
14
MongoDB shell version: 2.6.6
connecting to: 127.0.0.1/asd
2015-02-26T15:55:23.945+0100 warning: Failed to connect to
127.0.0.1:27017, reason: errno:111 Connection refused
2015-02-26T15:55:23.946+0100 Error: couldn't connect to server
127.0.0.1:27017 (127.0.0.1), connection attempt failed at
src/mongo/shell/mongo.js:148
exception: connect failed
as everyone would expect.
If I start the client with the server running I get:
MongoDB shell version: 2.6.6
connecting to: 127.0.0.1/asd
2015-02-26T15:56:22.488+0100 mongo got signal 11 (Segmentation
fault), stack trace:
2015-02-26T15:56:22.490+0100 0x7d1c99 0x5e4d09 0x7f3025a3eb00
0x9c1222 0xa31bd8 0xa31c14 0xa36fbe 0x9cf84b 0x9dac68 0x9db085
0x8787d0 0x99b4a8 0x937ebd 0x3ea764206362
mongo(_ZN5mongo15printStackTraceERSo+0x39) [0x7d1c99]
mongo(_Z12quitAbruptlyi+0x119) [0x5e4d09]
/lib64/libc.so.6(+0x33b00) [0x7f3025a3eb00]
mongo(_ZN2v88internal6String11WriteToFlatItEEvPS1_PT_ii+0x692)
[0x9c1222]
mongo(_ZN2v88internal33GenericStringUtf16CharacterStream10FillBufferEjj+0x38)
[0xa31bd8]
mongo(_ZN2v88internal28BufferedUtf16CharacterStream9ReadBlockEv+0x34)
[0xa31c14]
mongo(_ZN2v88internal7Scanner10InitializeEPNS0_20Utf16CharacterStreamE+0x5e)
[0xa36fbe]
mongo(_ZN2v88internal6Parser9ParseLazyEPNS0_20Utf16CharacterStreamEPNS0_9ZoneScopeE+0x3b)
[0x9cf84b]
mongo(_ZN2v88internal6Parser9ParseLazyEv+0x158) [0x9dac68]
mongo(_ZN2v88internal9ParserApi5ParseEPNS0_15CompilationInfoEi+0x205)
[0x9db085]
mongo(_ZN2v88internal8Compiler11CompileLazyEPNS0_15CompilationInfoE+0xf0)
[0x8787d0]
mongo(_ZN2v88internal10JSFunction11CompileLazyENS0_6HandleIS1_EENS0_18ClearExceptionFlagE+0x1a8)
[0x99b4a8]
mongo(_ZN2v88internal11CallIC_MissENS0_9ArgumentsEPNS0_7IsolateE+0x27d)
[0x937ebd]
[0x3ea764206362]
Boom. This problem applies to mongo 2.6.6 and mongo 2.6.7.
Anyone having the same issues with mongodb?
And anyone any suggestions how this can be fixed?
The server *seems* to run fine.
Cheers
Ralf