# Graylog on docker not start **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [March 12, 2019, 2:23pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393 "2019-03-12T14:23:59Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 12, 2019, 2:23pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/1 "2019-03-12T14:23:59Z")
config folder look lik: drwxrwxrwx 2 755 1100 4096 Mar 12 15:12 config and gralog start with this error: chown: changing ownership of ‘/usr/share/graylog/data/config’: Operation not permitted Warning can not change owner to graylog:graylog [http://servername:9000/api](http://servername:9000/api) says unable to connect and curl [http://servername:9000](http://servername:9000) says: Failed to connect to datalog port 9000: Connection refused The firewall is disabled netstat -tupln | grep 9000 tcp6 0 0 :::9000 :::\* LISTEN - ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 12, 2019, 2:48pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/2 "2019-03-12T14:48:11Z")
i change the config file to 1100:1100 and now [http://servername:9000](http://servername:9000) We are experiencing problems connecting to the Graylog server running on [http://172.18.0.4:9000/api/](http://172.18.0.4:9000/api/). Please verify that the server is healthy and working correctly. You will be automatically redirected to the previous page once we can connect to the server. and detail: Error message Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc. Original Request GET [http://172.18.0.4:9000/api/](http://172.18.0.4:9000/api/) Status code undefined Full error message Error: Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc. i have following error in graylog log ERROR: org.graylog2.indexer.cluster.Cluster - Couldn’t read cluster health for indices [graylog\_\*] (Could not connect to [http://127.0.0.1:9200](http://127.0.0.1:9200)) ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 12, 2019, 2:50pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/3 "2019-03-12T14:50:05Z")
what is your configuration look like? what graylog version did you start? ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 12, 2019, 2:55pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/4 "2019-03-12T14:55:15Z")
i used the compose file from the [graylog.com](http://graylog.com) graylog is version 3.0 and elastic is 6.6.1 here is compose file ```auto version: '2' services: mongodb: image: mongo:3 volumes: - /graylog/data/db:/data/db elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.6.1 volumes: - /graylog/elasticsearch:/usr/share/elasticsearch/data environment: - http.host=0.0.0.0 - transport.host=localhost - network.host=0.0.0.0 - "ES_JAVA_OPTS=-Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 mem_limit: 1g graylog: image: graylog/graylog:3.0 #graylog/graylog:3.0 volumes: - /graylog/data/journal:/usr/share/graylog/data/journal - /graylog/config:/usr/share/graylog/data/config environment: # CHANGE ME (must be at least 16 characters)! - GRAYLOG_PASSWORD_SECRET=somepasswordpepper # Password: admin - GRAYLOG_ROOT_PASSWORD_SHA2=415160ff57f6bb5a592ba347d4c992a1a489437180fe4b228d31d72091f76fb3 # - GRAYLOG_ELASTICSEARCH_HOSTS=http://elasticsearch:9200 - GRAYLOG_WEB_ENDPOINT_URI=http://"servername:9000/api # - GRAYLOG_HTTP_EXTERNAL_URI=http://servername:9000/api # - GRAYLOG_HTTP_PUBLISH_URI=http://servername:9000/api links: - mongodb:mongo - elasticsearch depends_on: - mongodb - elasticsearch ports: # Graylog web interface and REST API - 9000:9000 # Syslog TCP - 514:514 # Syslog UDP # GELF TCP - 12201:12201 # GELF UDP - 12201:12201/udp volumes: mongo_data: driver: local es_data: driver: local graylog_journal: driver: local ``` ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 12, 2019, 3:05pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/5 "2019-03-12T15:05:33Z")
please make your posting readable with markup like mentioned in the FAQ ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 12, 2019, 3:15pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/6 "2019-03-12T15:15:02Z")
ok sorry: it’s graylog version 3.0 and elasticsearch version 6.6.1 mongo version 3 ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 13, 2019, 11:21am UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/7 "2019-03-13T11:21:32Z")
it’s work now. problem was group id and permission. graylog has 1100 as group and mango 999 and elastic just unix user permission. ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 13, 2019, 12:21pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/8 "2019-03-13T12:21:21Z")
i mount mongo volumes like: - /graylog/data/db:/data/db and /graylog/data/db has: drwxr-xr-x 2 999 root 4096 Mar 13 09:33 db i can’t see any file in db directories. it’s look like the mount, is not correct. From docker logs for mango i found the following error: I NETWORK [initandlisten] waiting for connections on port 27017 2019-03-13T09:52:37.067+0000 I NETWORK [listener] connection accepted from 172.21.0.4:49582 #1 (1 connection now open) 2019-03-13T09:52:37.076+0000 I NETWORK [conn1] received client metadata from 172.21.0.4:49582 conn1: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture 2019-03-13T09:52:37.106+0000 I NETWORK [listener] connection accepted from 172.21.0.4:49584 #2 (2 connections now open). What is wrong? ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 13, 2019, 2:33pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/9 "2019-03-13T14:33:08Z")
what is the software mango you are talking about? ---
**Author:** ![Sharzad](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Sharzad](https://community.graylog.org/u/Sharzad)\ **Post date:** [March 13, 2019, 3:30pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/10 "2019-03-13T15:30:43Z")
I mean mongo. this is just typo. 🙂 ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [March 13, 2019, 3:50pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/11 "2019-03-13T15:50:47Z")
Guy I fixed your formatting - please do this your own in the future. You did not read well the documentation, you mixed in settings from Graylog prior to Version 3.0 what will make it fail to run. Please re-read the docs and correct your docker compose file ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [March 27, 2019, 3:50pm UTC](https://community.graylog.org/t/graylog-on-docker-not-start/9393/12 "2019-03-27T15:50:49Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.