Docker graylog server is up but accesing port 9000 just gives me a white screen

[i4admin (Casper Jensen)]

Hi all,

So when i access my graylog server at 172.16.99.9:9000 my firefox browser just shows me a white screen. No error.
I have tried to add the logs from the graylog container to my host but there are no log files. Nothing in /var/log or /var/log/graylog-server/
This i have confirmed on the host as well as inside the container???

I belive i have seen the error before but i can’t remember where…
and what more wierd is that this was working but i had to recraete the docker compose file from the documentation since i deleted it by mistake

any help would be greatly apriciated! and happy new years!

[i4admin (Casper Jensen)]

Here is my docker-compose file:

Blockquote
version: ‘3.3’
services:
MongoDB: https ://hub.docker .com/_/mongo/
mongodb:
image: mongo:3
volumes:
- mongo_data:/data/db
Elasticsearch:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:5.6.12
volumes:
- es_data:/usr/share/elasticsearch/data
environment:
- http.host=0.0.0.0
- transport.host=localhost
- network.host=0.0.0.0
# Disable X-Pack security:
- xpack.security.enabled=false
- xpack.watcher.enabled=false
- xpack.monitoring.enabled=false
- xpack.security.audit.enabled=false
- xpack.ml.enabled=false
- xpack.graph.enabled=false
- “ES_JAVA_OPTS=-Xms512m -Xmx512m”
ulimits:
memlock:
soft: -1
hard: -1
#mem_limit: 1g
deploy:
resources:
limits:
memory: ‘0.50’
Graylog:
graylog:
user: root
image: graylog/graylog:3.1
volumes:
# Mount local configuration directory into Docker container
- ./graylog/config:/usr/share/graylog/data/config
# Mount local log files
- ./graylog/logs:/var/log/graylog-server
Mount local plugin file into Docker container
- ./graylog/plugin/graylog-plugin-auth-sso-2.4.0.jar:/usr/share/graylog/plugin/graylog-plugin-auth-sso-2.4.0.jar
environment:
# CHANGE ME!
- GRAYLOG_PASSWORD_SECRET=XXXXXXXXXXXXXXX
# Password: XXXXXX
- GRAYLOG_ROOT_PASSWORD_SHA2=8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
- GRAYLOG_WEB_ENDPOINT_URI=http :// 172.16.99.9 :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
- 514:514/udp
# GELF TCP
- 12201:12201
# GELF UDP
- 12201:12201/udp
Volumes for persisting data, see
volumes:
mongo_data:
driver: local
es_data:
driver: local
graylog_journal:
driver: local

[i4admin (Casper Jensen)]

Here is log when starting my docker compose file:

Blockquote
root@docker01:/docker/graylog-docker# docker-compose up
WARNING: Some services (elasticsearch) use the ‘deploy’ key, which will be ignored. Compose does not support ‘deploy’ configuration - use docker stack deploy to deploy to a swarm.
Starting graylogdocker_elasticsearch_1 …
Starting graylogdocker_elasticsearch_1
Starting graylogdocker_mongodb_1 …
Starting graylogdocker_mongodb_1 … done
Recreating graylogdocker_graylog_1 …
Recreating graylogdocker_graylog_1 … done
Attaching to graylogdocker_elasticsearch_1, graylogdocker_mongodb_1, graylogdocker_graylog_1
elasticsearch_1 | [2019-12-28T10:45:58,368][INFO ][o.e.n.Node ] initializing …
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=eb123f915831
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] db version v3.6.16
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] git version: 204ab367a130a4fd2db1c54b02cd6a86e4e07f56
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
elasticsearch_1 | [2019-12-28T10:45:58,478][INFO ][o.e.e.NodeEnvironment ] [0FKd6Qo] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/sda2)]], net usable_space [167.6gb], net total_space [186gb], spins? [possibly], types [ext4]
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] allocator: tcmalloc
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] modules: none
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] build environment:
elasticsearch_1 | [2019-12-28T10:45:58,479][INFO ][o.e.e.NodeEnvironment ] [0FKd6Qo] heap size [494.9mb], compressed ordinary object pointers [true]
elasticsearch_1 | [2019-12-28T10:45:58,512][INFO ][o.e.n.Node ] node name [0FKd6Qo] derived from node ID [0FKd6QorQ02eRJqrwaEKHg]; set [node.name] to override
elasticsearch_1 | [2019-12-28T10:45:58,512][INFO ][o.e.n.Node ] version[5.6.12], pid[1], build[cfe3d9f/2018-09-10T20:12:43.732Z], OS[Linux/4.15.0-72-generic/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_181/25.181-b13]
elasticsearch_1 | [2019-12-28T10:45:58,512][INFO ][o.e.n.Node ] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -Des.path.home=/usr/share/elasticsearch]
elasticsearch_1 | [2019-12-28T10:45:59,910][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [aggs-matrix-stats]
elasticsearch_1 | [2019-12-28T10:45:59,910][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [ingest-common]
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [lang-expression]
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [lang-groovy]
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] distmod: ubuntu1604
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [lang-mustache]
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [lang-painless]
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [parent-join]
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] distarch: x86_64
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] target_arch: x86_64
mongodb_1 | 2019-12-28T10:45:58.417+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true } }
mongodb_1 | 2019-12-28T10:45:58.417+0000 I - [initandlisten] Detected data files in /data/db created by the ‘wiredTiger’ storage engine, so setting the active storage engine to ‘wiredTiger’.
mongodb_1 | 2019-12-28T10:45:58.417+0000 I STORAGE [initandlisten]
mongodb_1 | 2019-12-28T10:45:58.417+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongodb_1 | 2019-12-28T10:45:58.417+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [percolator]
mongodb_1 | 2019-12-28T10:45:58.417+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=1460M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),compatibility=(release=“3.0”,require_max=“3.0”),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [reindex]
mongodb_1 | 2019-12-28T10:45:59.111+0000 I STORAGE [initandlisten] WiredTiger message [1577529959:111072][1:0x7f8afbab5a40], txn-recover: Main recovery loop: starting at 4/69760
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [transport-netty3]
mongodb_1 | 2019-12-28T10:45:59.217+0000 I STORAGE [initandlisten] WiredTiger message [1577529959:217267][1:0x7f8afbab5a40], txn-recover: Recovering log 4 through 5
elasticsearch_1 | [2019-12-28T10:45:59,911][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded module [transport-netty4]
mongodb_1 | 2019-12-28T10:45:59.292+0000 I STORAGE [initandlisten] WiredTiger message [1577529959:292740][1:0x7f8afbab5a40], txn-recover: Recovering log 5 through 5
elasticsearch_1 | [2019-12-28T10:45:59,912][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded plugin [ingest-geoip]
elasticsearch_1 | [2019-12-28T10:45:59,912][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded plugin [ingest-user-agent]
elasticsearch_1 | [2019-12-28T10:45:59,912][INFO ][o.e.p.PluginsService ] [0FKd6Qo] loaded plugin [x-pack]
mongodb_1 | 2019-12-28T10:45:59.354+0000 I STORAGE [initandlisten] WiredTiger message [1577529959:354727][1:0x7f8afbab5a40], txn-recover: Set global recovery timestamp: 0
mongodb_1 | 2019-12-28T10:45:59.479+0000 I CONTROL [initandlisten]
mongodb_1 | 2019-12-28T10:45:59.479+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1 | 2019-12-28T10:45:59.479+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
mongodb_1 | 2019-12-28T10:45:59.479+0000 I CONTROL [initandlisten]
mongodb_1 | 2019-12-28T10:45:59.487+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory ‘/data/db/diagnostic.data’
mongodb_1 | 2019-12-28T10:45:59.488+0000 I NETWORK [initandlisten] listening via socket bound to 0.0.0.0
mongodb_1 | 2019-12-28T10:45:59.488+0000 I NETWORK [initandlisten] listening via socket bound to /tmp/mongodb-27017.sock
mongodb_1 | 2019-12-28T10:45:59.488+0000 I NETWORK [initandlisten] waiting for connections on port 27017
elasticsearch_1 | [2019-12-28T10:46:01,647][INFO ][o.e.d.DiscoveryModule ] [0FKd6Qo] using discovery type [zen]
elasticsearch_1 | [2019-12-28T10:46:02,100][INFO ][o.e.n.Node ] initialized
elasticsearch_1 | [2019-12-28T10:46:02,100][INFO ][o.e.n.Node ] [0FKd6Qo] starting …
elasticsearch_1 | [2019-12-28T10:46:02,205][INFO ][o.e.t.TransportService ] [0FKd6Qo] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
elasticsearch_1 | [2019-12-28T10:46:02,217][WARN ][o.e.b.BootstrapChecks ] [0FKd6Qo] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
graylog_1 | 2019-12-28 10:46:02,871 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: AWS plugins 3.1.3 [org.graylog.aws.AWSPlugin]
graylog_1 | 2019-12-28 10:46:02,874 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Collector 3.1.3 [org.graylog.plugins.collector.CollectorPlugin]
graylog_1 | 2019-12-28 10:46:02,874 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Threat Intelligence Plugin 3.1.3 [org.graylog.plugins.threatintel.ThreatIntelPlugin]
graylog_1 | 2019-12-28 10:46:03,095 INFO : org.graylog2.bootstrap.CmdLineTool - Running with JVM arguments: -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:NewRatio=1 -XX:MaxMetaspaceSize=256m -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow -Dlog4j.configurationFile=/usr/share/graylog/data/config/log4j2.xml -Djava.library.path=/usr/share/graylog/lib/sigar/ -Dgraylog2.installation_source=docker
graylog_1 | 2019-12-28 10:46:03,235 INFO : org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.1.3.Final
graylog_1 | 2019-12-28 10:46:04,804 INFO : org.graylog2.shared.buffers.InputBufferImpl - Message journal is enabled.
graylog_1 | 2019-12-28 10:46:04,819 INFO : org.graylog2.plugin.system.NodeId - Node ID: 5ae916a6-9db4-411e-adba-733521de18cc
graylog_1 | 2019-12-28 10:46:04,966 INFO : kafka.log.LogManager - Loading logs.
graylog_1 | 2019-12-28 10:46:04,982 WARN : kafka.log.Log - Found a corrupted index file, /usr/share/graylog/data/journal/messagejournal-0/00000000000000000000.index, deleting and rebuilding index…
graylog_1 | 2019-12-28 10:46:05,006 INFO : kafka.log.LogManager - Logs loading complete.
graylog_1 | 2019-12-28 10:46:05,009 INFO : org.graylog2.shared.journal.KafkaJournal - Initialized Kafka based journal at /usr/share/graylog/data/journal
graylog_1 | 2019-12-28 10:46:05,027 INFO : org.mongodb.driver.cluster - Cluster created with settings {hosts=[mongo:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout=‘30000 ms’, maxWaitQueueSize=500}
graylog_1 | 2019-12-28 10:46:05,056 INFO : org.mongodb.driver.cluster - Cluster description not yet available. Waiting for 30000 ms before timing out
mongodb_1 | 2019-12-28T10:46:05.062+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42494 #1 (1 connection now open)
mongodb_1 | 2019-12-28T10:46:05.069+0000 I NETWORK [conn1] received client metadata from 172.19.0.4:42494 conn1: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
graylog_1 | 2019-12-28 10:46:05,086 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:1, serverValue:1}] to mongo:27017
graylog_1 | 2019-12-28 10:46:05,089 INFO : org.mongodb.driver.cluster - Monitor thread successfully connected to server with description ServerDescription{address=mongo:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 6, 16]}, minWireVersion=0, maxWireVersion=6, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=2040005}
mongodb_1 | 2019-12-28T10:46:05.099+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42496 #2 (2 connections now open)
mongodb_1 | 2019-12-28T10:46:05.099+0000 I NETWORK [conn2] received client metadata from 172.19.0.4:42496 conn2: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
graylog_1 | 2019-12-28 10:46:05,111 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:2, serverValue:2}] to mongo:27017
graylog_1 | 2019-12-28 10:46:05,311 INFO : org.graylog2.shared.buffers.InputBufferImpl - Initialized InputBufferImpl with ring size <65536> and wait strategy , running 2 parallel message handlers.
elasticsearch_1 | [2019-12-28T10:46:05,317][INFO ][o.e.c.s.ClusterService ] [0FKd6Qo] new_master {0FKd6Qo}{0FKd6QorQ02eRJqrwaEKHg}{SN-RcEpgStCPzwg9d9PjaQ}{localhost}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)[, ]
elasticsearch_1 | [2019-12-28T10:46:05,353][INFO ][o.e.h.n.Netty4HttpServerTransport] [0FKd6Qo] publish_address {172.19.0.3:9200}, bound_addresses {0.0.0.0:9200}
elasticsearch_1 | [2019-12-28T10:46:05,353][INFO ][o.e.n.Node ] [0FKd6Qo] started
graylog_1 | 2019-12-28 10:46:05,612 INFO : io.searchbox.client.AbstractJestClient - Setting server pool to a list of 1 servers: [http://elasticsearch:9200]
graylog_1 | 2019-12-28 10:46:05,617 INFO : io.searchbox.client.JestClientFactory - Using multi thread/connection supporting pooling connection manager
graylog_1 | 2019-12-28 10:46:05,673 INFO : io.searchbox.client.JestClientFactory - Using custom ObjectMapper instance
graylog_1 | 2019-12-28 10:46:05,674 INFO : io.searchbox.client.JestClientFactory - Node Discovery disabled…
graylog_1 | 2019-12-28 10:46:05,674 INFO : io.searchbox.client.JestClientFactory - Idle connection reaping disabled…
elasticsearch_1 | [2019-12-28T10:46:05,769][INFO ][o.e.l.LicenseService ] [0FKd6Qo] license [131f0e05-605c-4aae-adc5-044b0a6010d0] mode [trial] - valid
elasticsearch_1 | [2019-12-28T10:46:05,770][INFO ][o.e.g.GatewayService ] [0FKd6Qo] recovered [3] indices into cluster_state
graylog_1 | 2019-12-28 10:46:05,876 INFO : org.graylog2.shared.buffers.ProcessBuffer - Initialized ProcessBuffer with ring size <65536> and wait strategy .
graylog_1 | 2019-12-28 10:46:06,073 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /etc/graylog/server/GeoLite2-City.mmdb
graylog_1 | 2019-12-28 10:46:06,084 INFO : org.graylog2.buffers.OutputBuffer - Initialized OutputBuffer with ring size <65536> and wait strategy .
graylog_1 | 2019-12-28 10:46:06,108 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /etc/graylog/server/GeoLite2-City.mmdb
mongodb_1 | 2019-12-28T10:46:06.121+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42498 #3 (3 connections now open)
mongodb_1 | 2019-12-28T10:46:06.122+0000 I NETWORK [conn3] received client metadata from 172.19.0.4:42498 conn3: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
graylog_1 | 2019-12-28 10:46:06,124 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:3, serverValue:3}] to mongo:27017
graylog_1 | 2019-12-28 10:46:06,162 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /etc/graylog/server/GeoLite2-City.mmdb
graylog_1 | 2019-12-28 10:46:06,189 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /etc/graylog/server/GeoLite2-City.mmdb
graylog_1 | 2019-12-28 10:46:06,210 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /etc/graylog/server/GeoLite2-City.mmdb
elasticsearch_1 | [2019-12-28T10:46:06,480][INFO ][o.e.c.r.a.AllocationService] [0FKd6Qo] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[graylog_0][0]] …]).
graylog_1 | 2019-12-28 10:46:06,773 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server 3.1.3+cda805f starting up
graylog_1 | 2019-12-28 10:46:06,774 INFO : org.graylog2.bootstrap.ServerBootstrap - JRE: Oracle Corporation 1.8.0_232 on Linux 4.15.0-72-generic
graylog_1 | 2019-12-28 10:46:06,774 INFO : org.graylog2.bootstrap.ServerBootstrap - Deployment: docker
graylog_1 | 2019-12-28 10:46:06,774 INFO : org.graylog2.bootstrap.ServerBootstrap - OS: Debian GNU/Linux 10 (buster) (debian)
graylog_1 | 2019-12-28 10:46:06,775 INFO : org.graylog2.bootstrap.ServerBootstrap - Arch: amd64
graylog_1 | 2019-12-28 10:46:06,795 INFO : org.graylog2.shared.initializers.PeriodicalsService - Starting 29 periodicals …
graylog_1 | 2019-12-28 10:46:06,795 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ThroughputCalculator] periodical in [0s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,800 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.pipelineprocessor.periodical.LegacyDefaultStreamMigration] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,815 INFO : org.graylog2.shared.initializers.PeriodicalsService - Not starting [org.graylog2.periodical.AlertScannerThread] periodical. Not configured to run on this node.
graylog_1 | 2019-12-28 10:46:06,824 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.BatchedElasticSearchOutputFlushThread] periodical in [0s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,827 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ClusterHealthCheckThread] periodical in [120s], polling every [20s].
graylog_1 | 2019-12-28 10:46:06,829 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.GarbageCollectionWarningThread] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,834 INFO : org.graylog.plugins.pipelineprocessor.periodical.LegacyDefaultStreamMigration - Legacy default stream has no connections, no migration needed.
graylog_1 | 2019-12-28 10:46:06,838 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexerClusterCheckerThread] periodical in [0s], polling every [30s].
graylog_1 | 2019-12-28 10:46:06,843 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRetentionThread] periodical in [0s], polling every [300s].
graylog_1 | 2019-12-28 10:46:06,848 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRotationThread] periodical in [0s], polling every [10s].
graylog_1 | 2019-12-28 10:46:06,849 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.NodePingThread] periodical in [0s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,849 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.VersionCheckThread] periodical in [300s], polling every [1800s].
graylog_1 | 2019-12-28 10:46:06,850 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ThrottleStateUpdaterThread] periodical in [1s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,851 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.events.ClusterEventPeriodical] periodical in [0s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,855 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.events.ClusterEventCleanupPeriodical] periodical in [0s], polling every [86400s].
graylog_1 | 2019-12-28 10:46:06,855 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ClusterIdGeneratorPeriodical] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,855 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRangesMigrationPeriodical] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,856 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRangesCleanupPeriodical] periodical in [15s], polling every [3600s].
mongodb_1 | 2019-12-28T10:46:06.858+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42500 #4 (4 connections now open)
mongodb_1 | 2019-12-28T10:46:06.858+0000 I NETWORK [conn4] received client metadata from 172.19.0.4:42500 conn4: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
mongodb_1 | 2019-12-28T10:46:06.863+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42502 #5 (5 connections now open)
mongodb_1 | 2019-12-28T10:46:06.863+0000 I NETWORK [conn5] received client metadata from 172.19.0.4:42502 conn5: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
graylog_1 | 2019-12-28 10:46:06,864 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:4, serverValue:4}] to mongo:27017
mongodb_1 | 2019-12-28T10:46:06.877+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42504 #6 (6 connections now open)
mongodb_1 | 2019-12-28T10:46:06.877+0000 I NETWORK [listener] connection accepted from 172.19.0.4:42506 #7 (7 connections now open)
mongodb_1 | 2019-12-28T10:46:06.877+0000 I NETWORK [conn6] received client metadata from 172.19.0.4:42504 conn6: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
mongodb_1 | 2019-12-28T10:46:06.878+0000 I NETWORK [conn7] received client metadata from 172.19.0.4:42506 conn7: { driver: { name: “mongo-java-driver”, version: “unknown” }, os: { type: “Linux”, name: “Linux”, architecture: “amd64”, version: “4.15.0-72-generic” }, platform: “Java/Oracle Corporation/1.8.0_232-b09” }
graylog_1 | 2019-12-28 10:46:06,879 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:5, serverValue:5}] to mongo:27017
graylog_1 | 2019-12-28 10:46:06,883 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:7, serverValue:7}] to mongo:27017
graylog_1 | 2019-12-28 10:46:06,886 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:6, serverValue:6}] to mongo:27017
graylog_1 | 2019-12-28 10:46:06,895 INFO : org.graylog2.shared.initializers.PeriodicalsService - Not starting [org.graylog2.periodical.UserPermissionMigrationPeriodical] periodical. Not configured to run on this node.
graylog_1 | 2019-12-28 10:46:06,898 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ConfigurationManagementPeriodical] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,926 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.LdapGroupMappingMigration] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,942 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexFailuresPeriodical] periodical, running forever.
graylog_1 | 2019-12-28 10:46:06,943 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.TrafficCounterCalculator] periodical in [0s], polling every [1s].
graylog_1 | 2019-12-28 10:46:06,982 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.indexer.fieldtypes.IndexFieldTypePollerPeriodical] periodical in [0s], polling every [3600s].
graylog_1 | 2019-12-28 10:46:07,002 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.scheduler.periodicals.ScheduleTriggerCleanUp] periodical in [120s], polling every [86400s].
graylog_1 | 2019-12-28 10:46:07,012 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.sidecar.periodical.PurgeExpiredSidecarsThread] periodical in [0s], polling every [600s].
graylog_1 | 2019-12-28 10:46:07,012 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.sidecar.periodical.PurgeExpiredConfigurationUploads] periodical in [0s], polling every [600s].
graylog_1 | 2019-12-28 10:46:07,020 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.views.search.db.SearchesCleanUpJob] periodical in [0s], polling every [28800s].
graylog_1 | 2019-12-28 10:46:07,033 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.events.periodicals.EventNotificationStatusCleanUp] periodical in [120s], polling every [86400s].
graylog_1 | 2019-12-28 10:46:07,065 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.collector.periodical.PurgeExpiredCollectorsThread] periodical in [0s], polling every [3600s].
graylog_1 | 2019-12-28 10:46:07,442 INFO : org.graylog2.shared.initializers.JerseyService - Enabling CORS for HTTP endpoint
graylog_1 | 2019-12-28 10:46:26,563 INFO : org.glassfish.grizzly.http.server.NetworkListener - Started listener bound to [0.0.0.0:9000]
graylog_1 | 2019-12-28 10:46:26,564 INFO : org.glassfish.grizzly.http.server.HttpServer - [HttpServer] Started.
graylog_1 | 2019-12-28 10:46:26,564 INFO : org.graylog2.shared.initializers.JerseyService - Started REST API at <0.0.0.0:9000>
graylog_1 | 2019-12-28 10:46:26,565 INFO : org.graylog2.shared.initializers.ServiceManagerListener - Services are healthy
graylog_1 | 2019-12-28 10:46:26,565 INFO : org.graylog2.shared.initializers.InputSetupService - Triggering launching persisted inputs, node transitioned from Uninitialized [LB:DEAD] to Running [LB:ALIVE]
graylog_1 | 2019-12-28 10:46:26,567 INFO : org.graylog2.bootstrap.ServerBootstrap - Services started, startup times in ms: {InputSetupService [RUNNING]=2, OutputSetupService [RUNNING]=18, GracefulShutdownService [RUNNING]=19, BufferSynchronizerService [RUNNING]=21, JournalReader [RUNNING]=24, JobSchedulerService [RUNNING]=28, KafkaJournal [RUNNING]=35, MongoDBProcessingStatusRecorderService [RUNNING]=39, EtagService [RUNNING]=76, ConfigurationEtagService [RUNNING]=81, LookupTableService [RUNNING]=83, StreamCacheService [RUNNING]=173, PeriodicalsService [RUNNING]=287, JerseyService [RUNNING]=19770}
graylog_1 | 2019-12-28 10:46:26,573 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server up and running.

[i4admin (Casper Jensen)]

Found the solution:

had to add
GRAYLOG_HTTP_EXTERNAL_URI: http://33.33.33.33:9000/
as per this post

Graylog 3.1 with docker - running and healthy but blank page when accessing it

Hi! I installed graylog 3.1 in a container with docker images. I followed the documentation on the officiel docker page for graylog, the container are starting and flagged as healthy but when I access the web page it just turns and turns and gives me a blank page. Any help would be appreciated!!! Here is my docker-compose.yml file I used and customized: version: ‘2’ services: graylog3_mongodb: image: mongo:3 volumes: - graylog3_mongo_data:/graylog3_space/db elasticsearch: image: docke…

[jan (Jan Doberstein)]

he @i4admin

glad that you found this information yourself. Some additional notes on your Docker Compose.

Did you run for a reason old MongoDB and Elasticsearch Versions? I would choose MongoDB V4 and Elasticsearch 6.8-oss

But that is just my personal way of using.

[i4admin (Casper Jensen)]

Hi @jan
Actually i just copied the docker-compose from the documentation and started from there. Didn’t think of checking the versions but thanks for pointing it out i will update my docker compose file

[jan (Jan Doberstein)]

Did you remember from what version you copy that from? Means from what page direct?

Because we try to keep the docs up to date - but only for the latest version, but not older versions. The wrong setting indicate that you started from some older version …

[i4admin (Casper Jensen)]

I don’t remember excatly but im pretty sure it was a docs.graylog site because i do remember the left menu pretty clearly. but when i do a search my self, trying to retrace my steps i would be tempted to say it was this site:
https://docs.graylog.org/en/3.1/pages/installation/docker.html
but that version of elastic search does not correlate to mine and i know that i haven’t touched the elastic search and mongodb setup in the docker compose.

I also just googled part of my docker compose that i knew i hadn’t touch but that got me no where.
so im sorry to say im not really sure. unless you updated the docs like 2 to 4 days ago or something like that?

it may very well be my memory playing tricks on me…

[jan (Jan Doberstein)]

all fine @i4admin

I just want to make sure that we do not have actual docs that are not in good shape. The latest Version should be fine - but people sometimes use different versions (you can select the Graylog version bottom left) so they actually use the latest version but browse the docs for earlier versions.

I know for sure that the docs in that region had not updated for a month … or similar.

[i4admin (Casper Jensen)]

Sorry @jan I don’t remember where i got it from. But from the looks of it you doc looks right happy new years