Mongo won't start : "Got signal: 7 (Bus error)"

Community Support
1

Hi everyone,

I use docker stack to deploy myu rocketchat instance.
Today i have this message when the mongo service try to start :

chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=fcf2f6fd6902
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] db version v3.2.21
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] git version: 1ab1010737145ba3761318508ff65ba74dfe8155
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] allocator: tcmalloc
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] modules: none
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] build environment:
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten]     distmod: debian81
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten]     distarch: x86_64
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten]     target_arch: x86_64
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.122+0000 I CONTROL  [initandlisten] options: { replication: { oplogSizeMB: 128, replSet: "rs0" }, storage: { engine: "mmapv1", mmapv1: { smallFiles: true } } }
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.150+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.152+0000 I JOURNAL  [initandlisten] recover begin
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.153+0000 I JOURNAL  [initandlisten] recover lsn: 2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.153+0000 I JOURNAL  [initandlisten] recover /data/db/journal/j._0
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:20 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:1040 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:3163 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:4988 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:5088 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:5188 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:5288 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:5388 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section seq:5488 < lsn:2194038
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.155+0000 I JOURNAL  [initandlisten] recover skipping application of section more...
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.156+0000 I JOURNAL  [initandlisten] recover final skipped journal section had sequence number 2174278
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.156+0000 I JOURNAL  [initandlisten] recover applying initial journal section with sequence number 2184108
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.167+0000 F -        [initandlisten] Invalid access at address: 0x7f644df981c0
chat_mongo.1.vhzyz45fmyrg@endeavour    | 2019-03-13T14:07:11.179+0000 F -        [initandlisten] Got signal: 7 (Bus error).

Here is my yml file :

version: '3'

services:
  rocketchat:
    image: rocketchat/rocket.chat:latest
    volumes:
      - /XXX/XXX/XXXweb/uploads:/app/uploads
    environment:
      - PORT=3000
      - ROOT_URL=https://XXX.XXX.fr
      - MONGO_URL=mongodb://mongo:27017/rocketchat
      - MONGO_OPLOG_URL=mongodb://mongo:27017/local
      - MAIL_URL=smtp://smtp.email
    depends_on:
      - mongo
    ports:
      - 3000:3000
    labels:
      - "traefik.backend=rocketchat"
      - "traefik.frontend.rule=Host: your.domain.tld"

  mongo:
    image: mongo:3.2
    volumes:
     - /XX/XX/XXXXX/XX/XX/XX:/data/db
    command: mongod --smallfiles --oplogSize 128 --replSet rs0 --storageEngine=mmapv1
    labels:
      - "traefik.enable=false"

  mongo-init-replica:
    image: mongo:4.0
    command: 'bash -c "for i in `seq 1 30`; do mongo mongo/rocketchat --eval \"rs.initiate({ _id: ''rs0'', members: [ { _id: 0, host: ''localhost:27017'' } ]})\" && s=$$? && break || s=$$?; echo \"Tried $$i times. Waiting 5 secs...\"; sleep 5; done; (exit $$s)"'
    depends_on:
      - mongo

  nginx:
    image: nginx:latest
    volumes:
      - /XXX/XXX/XXX/XX:/etc/nginx
      - /XXX/XXX/XXX/XX:/var/log/nginx
    ports:
      - 80:80
      - 443:443

Any idea?

2

Are you blowing memory? What’re you running on.

3

Hi Sing Li,

It’s actually a docker swarm cluster with 2 dedicated servers with each one : 2 x Intel® Xeon E5 2620v4 128 GB RAM 2 x 6 TB Drives

4

When i start this stack with a fresh folder, i have no issue