Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

mongo 2.8 and 3.0 segfaults #251

Closed
cytopia opened this issue Mar 8, 2018 · 5 comments
Closed

mongo 2.8 and 3.0 segfaults #251

cytopia opened this issue Mar 8, 2018 · 5 comments
Labels
question Usability question, not directly related to an error with the image

Comments

@cytopia
Copy link

cytopia commented Mar 8, 2018 

docker run -it --rm --entrypoint=/bin/sh mongo:2.8
# mongod
Segmentation fault (core dumped)

 docker run -it --rm --entrypoint=/bin/sh mongo:3.0
# mongod
Segmentation fault (core dumped)

It does however work with mongo 3.2
@cytopia cytopia mentioned this issue Mar 8, 2018
Closed
@yosifkit
Copy link
Member

yosifkit commented Mar 8, 2018

Unable to reproduce (see below). Probably corrupt images. Try deleting them completely and pulling them again.

See also, docker/for-mac#2327, docker-library/openjdk#169, docker-library/ruby#180, docker-library/mysql#372, docker/for-mac#2542, docker-library/python#260, docker-library/php#594, docker-library/ruby#195.

sauron@minas-morgul:~$ docker run -it --rm --entrypoint=/bin/sh mongo:2.8
Unable to find image 'mongo:2.8' locally
2.8: Pulling from library/mongo
a3ed95caeb02: Pull complete 
77e0b6da8731: Pull complete 
2f087c2f6a83: Pull complete 
335b50ca3a32: Pull complete 
7319448bde25: Pull complete 
8113c42ce5c5: Pull complete 
cfda5de530a8: Pull complete 
e567f1961505: Pull complete 
8a77cd9c2154: Pull complete 
Digest: sha256:c556793209711a68d80963475a427536cbc9802eb0023215d231d0801b9a733e
Status: Downloaded newer image for mongo:2.8
# mongod
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] MongoDB starting : pid=7 port=27017 dbpath=/data/db 64-bit host=091f3f71f4b1
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] 
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] db version v2.8.0-rc5
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] git version: 74b351de21c84438b12a83b28e155f5e69e3c1eb
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] build info: Linux build19.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2018-03-08T19:48:26.636+0000 I CONTROL  [initandlisten] options: {}
2018-03-08T19:48:26.648+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal
2018-03-08T19:48:26.648+0000 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
^C2018-03-08T19:48:28.710+0000 I CONTROL  [signalProcessingThread] got signal 2 (Interrupt), will terminate after current cmd ends
2018-03-08T19:48:28.711+0000 I CONTROL  [signalProcessingThread] now exiting
2018-03-08T19:48:28.711+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2018-03-08T19:48:28.711+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2018-03-08T19:48:28.711+0000 I NETWORK  [signalProcessingThread] shutdown: going to flush diaglog...
2018-03-08T19:48:28.711+0000 I NETWORK  [signalProcessingThread] shutdown: going to close sockets...
2018-03-08T19:48:28.711+0000 I STORAGE  [signalProcessingThread] shutdown: waiting for fs preallocator...
2018-03-08T19:48:28.711+0000 I STORAGE  [signalProcessingThread] shutdown: final commit...
2018-03-08T19:48:28.711+0000 I STORAGE  [signalProcessingThread] shutdown: closing all files...
2018-03-08T19:48:28.711+0000 I STORAGE  [signalProcessingThread] closeAllFiles() finished
2018-03-08T19:48:28.711+0000 I JOURNAL  [signalProcessingThread] journalCleanup...
2018-03-08T19:48:28.711+0000 I JOURNAL  [signalProcessingThread] removeJournalFiles
2018-03-08T19:48:28.756+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2018-03-08T19:48:28.757+0000 I CONTROL  [signalProcessingThread] dbexit:  rc: 0
# 
sauron@minas-morgul:~$ docker run -it --rm --entrypoint=/bin/sh mongo:3.0
Unable to find image 'mongo:3.0' locally
3.0: Pulling from library/mongo
a5a533fc62cc: Pull complete 
8999eb72ff1e: Pull complete 
bad29ed50ebf: Pull complete 
b9892e015416: Pull complete 
298de1a84905: Pull complete 
4c28829bb961: Pull complete 
443f89a8d271: Pull complete 
8a3613b6f10a: Pull complete 
d53094768132: Pull complete 
1fb478e12289: Pull complete 
ce4ae95d86e0: Pull complete 
57e66e902724: Pull complete 
Digest: sha256:2635bb0bad8ddcbea0f47bdfc5e0552f7ea6f1bbfecdd345a6f86a2e93e8da0c
Status: Downloaded newer image for mongo:3.0
# mongod
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] MongoDB starting : pid=8 port=27017 dbpath=/data/db 64-bit host=f6abc4c9885f
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] db version v3.0.15
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] git version: b8ff507269c382bc100fc52f75f48d54cd42ec3b
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] build info: Linux ip-10-166-66-3 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 BOOST_LIB_VERSION=1_49
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2018-03-08T19:50:10.597+0000 I CONTROL  [initandlisten] options: {}
2018-03-08T19:50:10.609+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal
2018-03-08T19:50:10.610+0000 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2018-03-08T19:50:13.243+0000 I JOURNAL  [initandlisten] preallocateIsFaster=true 34.92
^C2018-03-08T19:50:15.200+0000 I CONTROL  [signalProcessingThread] got signal 2 (Interrupt), will terminate after current cmd ends
2018-03-08T19:50:15.201+0000 I CONTROL  [signalProcessingThread] now exiting
2018-03-08T19:50:15.201+0000 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
2018-03-08T19:50:15.201+0000 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2018-03-08T19:50:15.201+0000 I NETWORK  [signalProcessingThread] shutdown: going to flush diaglog...
2018-03-08T19:50:15.201+0000 I NETWORK  [signalProcessingThread] shutdown: going to close sockets...
2018-03-08T19:50:15.201+0000 I STORAGE  [signalProcessingThread] shutdown: waiting for fs preallocator...
2018-03-08T19:50:15.201+0000 I STORAGE  [signalProcessingThread] shutdown: final commit...
2018-03-08T19:50:15.201+0000 I STORAGE  [signalProcessingThread] shutdown: closing all files...
2018-03-08T19:50:15.201+0000 I STORAGE  [signalProcessingThread] closeAllFiles() finished
2018-03-08T19:50:15.201+0000 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
2018-03-08T19:50:15.201+0000 I CONTROL  [signalProcessingThread] dbexit:  rc: 0
#

@cytopia
Copy link
Author

cytopia commented Mar 8, 2018

I just deleted the images and tried again:

docker image rm mongo:2.8

Untagged: mongo:2.8
Untagged: mongo@sha256:c556793209711a68d80963475a427536cbc9802eb0023215d231d0801b9a733e
Deleted: sha256:4af37f2deb9727f77a95dd71f3bd76d8883b4e6bc3f4f6bae2c1953f0a67782b
Deleted: sha256:9517cbe10b5ca5c09d281835f44e491f307659431d5a81a4836c4a1883e720eb
Deleted: sha256:7666cd48c08ce6a2a156f7c25076934c420bd5de5749db3e4e7fbf81f70eaa77
Deleted: sha256:e731281cd04379a869653d44c7ae6f5f1e0fca19982ba0e10465b2533fba2e9e
Deleted: sha256:7d664182d1f24b8f9fbb2f8d57f2e523cbdf1f64e57a73fea8f328594dfd126b
Deleted: sha256:32e4ed306e10f344bc9b6e450bf5aba6a761dd06b7a60febea49cd4a83704f6d
Deleted: sha256:828f2e9484b6fab89fb927277edafa7575a4ce89a1cf048dc0b4b29b8bfc5543
Deleted: sha256:acc9168cd13039be48db3b07281856d84cf13c89209a1c7c529839fdcae64f5b
Deleted: sha256:7aacab7d569e613a4465639c9cdd09b8172c2720fd855d4cbbfe2a9b5c9771fa
Deleted: sha256:e1ad797bef1fb0672180e43adda39ffa342418545873183707d7b5ea970dbdd2
Deleted: sha256:f24ec0ee8d0209d63407c12f7a2cc49ed42ee0fc19ca448599558d17695f98ec
Deleted: sha256:4f85a8b41743fe6883ac7e5bf33418bdfd770f56f9a288db95d077cc41e789e4
Deleted: sha256:1438aa1d37a4c1a6c6117e025964d20d33e69428032c32f93c807759552cf5f4
Deleted: sha256:8dd26aaa31a273fc12274fc8eb0076af1676fa39a6c0085b0ed78db3941545e8
Deleted: sha256:c35023c6174bf4f7f10b90ded1f2cdf7407267e520a5791db4a1677e19ac4eae
Deleted: sha256:bf669493716c02fe0ba85c551f2046cb529111b750df3f4937c2db46efbf4cb9
Deleted: sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef
docker run -it --rm --entrypoint=/bin/sh mongo:2.8

Unable to find image 'mongo:2.8' locally
2.8: Pulling from library/mongo
a3ed95caeb02: Pull complete
77e0b6da8731: Pull complete
2f087c2f6a83: Pull complete
335b50ca3a32: Pull complete
7319448bde25: Pull complete
8113c42ce5c5: Pull complete
cfda5de530a8: Pull complete
e567f1961505: Pull complete
8a77cd9c2154: Pull complete
Digest: sha256:c556793209711a68d80963475a427536cbc9802eb0023215d231d0801b9a733e
Status: Downloaded newer image for mongo:2.8
# mongod
Segmentation fault (core dumped)
#

So it must be something else. My version is (on Debian):

docker version
Client:
 Version:       18.02.0-ce
 API version:   1.36
 Go version:    go1.9.3
 Git commit:    fc4de44
 Built: Wed Feb  7 21:16:24 2018
 OS/Arch:       linux/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      18.02.0-ce
  API version:  1.36 (minimum version 1.12)
  Go version:   go1.9.3
  Git commit:   fc4de44
  Built:        Wed Feb  7 21:14:54 2018
  OS/Arch:      linux/amd64
  Experimental: false

What version did you use to try it?

@yosifkit yosifkit mentioned this issue Mar 9, 2018
Closed
@yosifkit yosifkit mentioned this issue Mar 21, 2018
Closed
@yosifkit
Copy link
Member

The 2.8 version of MongoDB was only a release candidate and was renamed to 3.0: #19. Still not sure why you would get segfaults on 3.0. I just tested 3.0 again on docker 18.02.0-ce on my AMD64 Debian Stretch host and it worked fine. 😕 😢

This was referenced Mar 27, 2018
Closed
Closed
@wglambert wglambert added the question Usability question, not directly related to an error with the image label Apr 25, 2018
@wglambert
Copy link

Since this issue doesn't seem to denote any errors with the image I'm going to close, if there is something reproducible to show an issue with the image that could be changed then I'll re-open.

@yosifkit yosifkit mentioned this issue Jul 3, 2018
Closed
@cytopia
Copy link
Author

cytopia commented Mar 27, 2022

@yosifkit @wglambert FY: I was just googling docker mongodb 3.0 segfault and found my old thread (almost 4 years leater) 😅

The issue still persists, at least on my machine. In the meanwhile I have a new notebook and latest Debian installed, both versions 2.8 and 3.0 still segfault on my machine. My Docker version:

$ docker --version
Docker version 20.10.14, build a224086

@cytopia cytopia mentioned this issue Mar 28, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Usability question, not directly related to an error with the image
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yosifkit @cytopia @wglambert