Graylog2-server: Graylog 2.0.0 Web Interface Problem

[onedaywillcome1]

Today, I tried to install graylog 2.0.0 in new Amazon Instance to test features of new graylog. After I installed elastic search, mongodb and graylog 2.0.0, I configured elasticsearch.yml and graylog config as below. Then, even though graylog server is up, running and elastic search added graylog node in logs, I encountered weird problem. Then I typed the graylog server ip ( <"my amazon instance public ip">:9000 ) in chrome and safari. However, when I entered my credentials ( admin/graylog password) and clicked signin, nothing was fired. Then 15-30 seconds later, graylog web interface gave an error as below:

Server currently unavailable
We are experiencing problems connecting to the Graylog server running on http://172.31.38.170:12900/. 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.
Do you need a hand? We can help you.
This is the last response we received from the server:
Error message
Bad request
Original Request
GET http://172.31.38.170:12900/system/cluster/node
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.

Here is the graylog config:

is_master = true
node_id_file = /etc/graylog/server/node-id
password_secret =  <my secret>
root_password_sha2 = <my sha 256 password>
rest_listen_uri = http://0.0.0.0:12900/
web_listen_uri = http://0.0.0.0:9000
mongodb_uri = mongodb://localhost/graylog
elasticsearch_discovery_zen_ping_unicast_hosts = 0.0.0.0:9300
elasticsearch_cluster_name = graylog

Here is the elasticsearch.yml config:

cluster.name: graylog
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["0.0.0.0:9300"]

Here is the graylog log:

2016-04-30 17:56:25,096 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugins: [Anonymous Usage Statistics 2.0.0 [org.graylog.plugins.usagestatistics.UsageStatsPlugin], Pipeline Processor Plugin 1.0.0-beta.2 [org.graylog.plugins.pipelineprocessor.ProcessorPlugin], Collector 1.0.0 [org.graylog.plugins.collector.CollectorPlugin], MapWidgetPlugin 1.0.0 [org.graylog.plugins.map.MapWidgetPlugin], Enterprise Integration Plugin 1.0.0 [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin]]
2016-04-30 17:56:25,213 INFO : org.graylog2.bootstrap.CmdLineTool - Running with JVM arguments: -Djava.library.path=bin/../lib/sigar -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow
2016-04-30 17:56:27,789 INFO : org.graylog2.shared.buffers.InputBufferImpl - Message journal is enabled.
2016-04-30 17:56:28,009 INFO : kafka.log.LogManager - Loading logs.
2016-04-30 17:56:28,106 INFO : kafka.log.LogManager - Logs loading complete.
2016-04-30 17:56:28,107 INFO : org.graylog2.shared.journal.KafkaJournal - Initialized Kafka based journal at data/journal
2016-04-30 17:56:28,125 INFO : org.graylog2.shared.buffers.InputBufferImpl - Initialized InputBufferImpl with ring size <65536> and wait strategy <BlockingWaitStrategy>, running 2 parallel message handlers.
2016-04-30 17:56:28,164 INFO : org.mongodb.driver.cluster - Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=5000}
2016-04-30 17:56:28,211 INFO : org.mongodb.driver.cluster - No server chosen by ReadPreferenceServerSelector{readPreference=primary} from cluster description ClusterDescription{type=UNKNOWN, connectionMode=SINGLE, all=[ServerDescription{address=localhost:27017, type=UNKNOWN, state=CONNECTING}]}. Waiting for 30000 ms before timing out
2016-04-30 17:56:28,246 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:1, serverValue:186}] to localhost:27017
2016-04-30 17:56:28,247 INFO : org.mongodb.driver.cluster - Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 6]}, minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216, roundTripTimeNanos=574568}
2016-04-30 17:56:28,255 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:2, serverValue:187}] to localhost:27017
2016-04-30 17:56:28,480 INFO : org.graylog2.plugin.system.NodeId - Node ID: 24997aac-8188-49fb-afc3-5bc0c414bdc5
2016-04-30 17:56:28,556 INFO : org.elasticsearch.node - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] version[2.3.1], pid[29941], build[bd98092/2016-04-04T12:25:05Z]
2016-04-30 17:56:28,556 INFO : org.elasticsearch.node - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] initializing ...
2016-04-30 17:56:28,561 INFO : org.elasticsearch.plugins - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] modules [], plugins [graylog-monitor], sites []
2016-04-30 17:56:30,485 INFO : org.elasticsearch.node - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] initialized
2016-04-30 17:56:30,571 INFO : org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.2.4.Final
2016-04-30 17:56:30,736 INFO : org.graylog2.shared.buffers.ProcessBuffer - Initialized ProcessBuffer with ring size <65536> and wait strategy <BlockingWaitStrategy>.
2016-04-30 17:56:32,764 INFO : org.graylog2.bindings.providers.RulesEngineProvider - No static rules file loaded.
2016-04-30 17:56:32,926 WARN : org.graylog.plugins.map.geoip.GeoIpResolverEngine - GeoIP database file does not exist: /tmp/GeoLite2-City.mmdb
2016-04-30 17:56:32,937 INFO : org.graylog2.buffers.OutputBuffer - Initialized OutputBuffer with ring size <65536> and wait strategy <BlockingWaitStrategy>.
2016-04-30 17:56:33,624 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server 2.0.0 (2dc6c03) starting up
2016-04-30 17:56:33,624 INFO : org.graylog2.bootstrap.ServerBootstrap - JRE: Oracle Corporation 1.8.0_66 on Linux 4.4.5-15.26.amzn1.x86_64
2016-04-30 17:56:33,625 INFO : org.graylog2.bootstrap.ServerBootstrap - Deployment: unknown
2016-04-30 17:56:33,625 INFO : org.graylog2.bootstrap.ServerBootstrap - OS: Amazon Linux AMI 2016.03 (amzn)
2016-04-30 17:56:33,625 INFO : org.graylog2.bootstrap.ServerBootstrap - Arch: amd64
2016-04-30 17:56:33,640 WARN : org.graylog2.shared.events.DeadEventLoggingListener - Received unhandled event of type <org.graylog2.plugin.lifecycles.Lifecycle> from event bus <AsyncEventBus{graylog-eventbus}>
2016-04-30 17:56:33,663 INFO : org.elasticsearch.node - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] starting ...
2016-04-30 17:56:33,668 INFO : org.graylog2.shared.initializers.PeriodicalsService - Starting 24 periodicals ...
2016-04-30 17:56:33,668 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ThroughputCalculator] periodical in [0s], polling every [1s].
2016-04-30 17:56:33,688 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.AlertScannerThread] periodical in [10s], polling every [60s].
2016-04-30 17:56:33,691 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.BatchedElasticSearchOutputFlushThread] periodical in [0s], polling every [1s].
2016-04-30 17:56:33,698 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ClusterHealthCheckThread] periodical in [0s], polling every [20s].
2016-04-30 17:56:33,704 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ContentPackLoaderPeriodical] periodical, running forever.
2016-04-30 17:56:33,704 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.GarbageCollectionWarningThread] periodical, running forever.
2016-04-30 17:56:33,705 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexerClusterCheckerThread] periodical in [0s], polling every [30s].
2016-04-30 17:56:33,708 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRetentionThread] periodical in [0s], polling every [300s].
2016-04-30 17:56:33,717 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRotationThread] periodical in [0s], polling every [10s].
2016-04-30 17:56:33,721 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.NodePingThread] periodical in [0s], polling every [1s].
2016-04-30 17:56:33,723 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.VersionCheckThread] periodical in [300s], polling every [1800s].
2016-04-30 17:56:33,732 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:3, serverValue:188}] to localhost:27017
2016-04-30 17:56:33,740 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ThrottleStateUpdaterThread] periodical in [1s], polling every [1s].
2016-04-30 17:56:33,741 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.events.ClusterEventPeriodical] periodical in [0s], polling every [1s].
2016-04-30 17:56:33,741 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.events.ClusterEventCleanupPeriodical] periodical in [0s], polling every [300s].
2016-04-30 17:56:33,743 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ClusterIdGeneratorPeriodical] periodical, running forever.
2016-04-30 17:56:33,743 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRangesMigrationPeriodical] periodical, running forever.
2016-04-30 17:56:33,744 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.IndexRangesCleanupPeriodical] periodical in [15s], polling every [3600s].
2016-04-30 17:56:33,749 INFO : org.graylog2.periodical.IndexRetentionThread - Elasticsearch cluster not available, skipping index retention checks.
2016-04-30 17:56:33,751 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:4, serverValue:189}] to localhost:27017
2016-04-30 17:56:33,752 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:5, serverValue:190}] to localhost:27017
2016-04-30 17:56:33,758 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:8, serverValue:193}] to localhost:27017
2016-04-30 17:56:33,764 INFO : org.graylog2.periodical.IndexerClusterCheckerThread - Indexer not fully initialized yet. Skipping periodic cluster check.
2016-04-30 17:56:33,774 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:7, serverValue:192}] to localhost:27017
2016-04-30 17:56:33,783 INFO : org.graylog2.shared.initializers.PeriodicalsService - Not starting [org.graylog2.periodical.UserPermissionMigrationPeriodical] periodical. Not configured to run on this node.
2016-04-30 17:56:33,783 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.AlarmCallbacksMigrationPeriodical] periodical, running forever.
2016-04-30 17:56:33,788 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.ConfigurationManagementPeriodical] periodical, running forever.
2016-04-30 17:56:33,797 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:9, serverValue:194}] to localhost:27017
2016-04-30 17:56:33,799 INFO : org.mongodb.driver.connection - Opened connection [connectionId{localValue:6, serverValue:191}] to localhost:27017
2016-04-30 17:56:33,851 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog2.periodical.LdapGroupMappingMigration] periodical, running forever.
2016-04-30 17:56:33,880 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.usagestatistics.UsageStatsNodePeriodical] periodical in [300s], polling every [21600s].
2016-04-30 17:56:33,892 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.usagestatistics.UsageStatsClusterPeriodical] periodical in [300s], polling every [21600s].
2016-04-30 17:56:33,897 INFO : org.graylog2.periodical.Periodicals - Starting [org.graylog.plugins.collector.periodical.PurgeExpiredCollectorsThread] periodical in [0s], polling every [3600s].
2016-04-30 17:56:34,070 INFO : org.elasticsearch.transport - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] publish_address {127.0.0.1:9350}, bound_addresses {[::1]:9350}, {127.0.0.1:9350}
2016-04-30 17:56:34,077 INFO : org.elasticsearch.discovery - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] graylog/4h-MsPPDSYCgDjIMJm4drg
2016-04-30 17:56:34,246 INFO : org.graylog2.shared.initializers.AbstractJerseyService - Enabling CORS for HTTP endpoint
2016-04-30 17:56:37,088 WARN : org.elasticsearch.discovery - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] waited for 3s and no initial state was set by the discovery
2016-04-30 17:56:37,088 INFO : org.elasticsearch.node - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] started
2016-04-30 17:56:37,219 INFO : org.elasticsearch.cluster.service - [graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5] detected_master {Blackheath}{UtIX4KLHRxmOsj5AcVxxww}{172.31.38.170}{172.31.38.170:9300}, added {{Blackheath}{UtIX4KLHRxmOsj5AcVxxww}{172.31.38.170}{172.31.38.170:9300},}, reason: zen-disco-receive(from master [{Blackheath}{UtIX4KLHRxmOsj5AcVxxww}{172.31.38.170}{172.31.38.170:9300}])
2016-04-30 17:56:38,148 INFO : org.glassfish.grizzly.http.server.NetworkListener - Started listener bound to [0.0.0.0:9000]
2016-04-30 17:56:38,149 INFO : org.glassfish.grizzly.http.server.HttpServer - [HttpServer] Started.
2016-04-30 17:56:38,153 INFO : org.graylog2.initializers.WebInterfaceService - Started Web Interface at <http://0.0.0.0:9000/>
2016-04-30 17:56:42,882 INFO : org.glassfish.grizzly.http.server.NetworkListener - Started listener bound to [0.0.0.0:12900]
2016-04-30 17:56:42,882 INFO : org.glassfish.grizzly.http.server.HttpServer - [HttpServer-1] Started.
2016-04-30 17:56:42,883 INFO : org.graylog2.shared.initializers.RestApiService - Started REST API at <http://0.0.0.0:12900/>
2016-04-30 17:56:42,883 INFO : org.graylog2.shared.initializers.ServiceManagerListener - Services are healthy
2016-04-30 17:56:42,885 INFO : org.graylog2.bootstrap.ServerBootstrap - Services started, startup times in ms: {OutputSetupService [RUNNING]=26, MetricsReporterService [RUNNING]=27, JournalReader [RUNNING]=27, KafkaJournal [RUNNING]=28, BufferSynchronizerService [RUNNING]=47, PeriodicalsService [RUNNING]=259, InputSetupService [RUNNING]=261, IndexerSetupService [RUNNING]=3610, WebInterfaceService [RUNNING]=4492, RestApiService [RUNNING]=9227}
2016-04-30 17:56:42,890 INFO : org.graylog2.bootstrap.ServerBootstrap - Graylog server up and running.
2016-04-30 17:56:42,890 INFO : org.graylog2.shared.initializers.InputSetupService - Triggering launching persisted inputs, node transitioned from Uninitialized?[LB:DEAD] to Running?[LB:ALIVE]

Here is the elastic search log:

[2016-04-30 17:30:24,119][INFO ][node                     ] [Blackheath] version[2.3.2], pid[28538], build[b9e4a6a/2016-04-21T16:03:47Z]
[2016-04-30 17:30:24,120][INFO ][node                     ] [Blackheath] initializing ...
[2016-04-30 17:30:24,760][INFO ][plugins                  ] [Blackheath] modules [reindex, lang-expression, lang-groovy], plugins [], sites []
[2016-04-30 17:30:24,778][INFO ][env                      ] [Blackheath] using [1] data paths, mounts [[/ (/dev/xvda1)]], net usable_space [5.4gb], net total_space [7.7gb], spins? [no], types [ext4]
[2016-04-30 17:30:24,778][INFO ][env                      ] [Blackheath] heap size [1007.3mb], compressed ordinary object pointers [true]
[2016-04-30 17:30:24,779][WARN ][env                      ] [Blackheath] max file descriptors [4096] for elasticsearch process likely too low, consider increasing to at least [65536]
[2016-04-30 17:30:27,045][INFO ][node                     ] [Blackheath] initialized
[2016-04-30 17:30:27,045][INFO ][node                     ] [Blackheath] starting ...
[2016-04-30 17:30:27,160][INFO ][transport                ] [Blackheath] publish_address {172.31.38.170:9300}, bound_addresses {[::]:9300}
[2016-04-30 17:30:27,169][INFO ][discovery                ] [Blackheath] graylog/UtIX4KLHRxmOsj5AcVxxww
[2016-04-30 17:30:30,239][INFO ][cluster.service          ] [Blackheath] new_master {Blackheath}{UtIX4KLHRxmOsj5AcVxxww}{172.31.38.170}{172.31.38.170:9300}, added {{graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5}{pcSJIa99TuefCCVlFH50cA}{127.0.0.1}{127.0.0.1:9350}{client=true, data=false, master=false},}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2016-04-30 17:30:30,367][INFO ][http                     ] [Blackheath] publish_address {172.31.38.170:9200}, bound_addresses {[::]:9200}
[2016-04-30 17:30:30,367][INFO ][node                     ] [Blackheath] started
[2016-04-30 17:30:30,399][INFO ][gateway                  ] [Blackheath] recovered [1] indices into cluster_state
[2016-04-30 17:30:30,807][INFO ][cluster.routing.allocation] [Blackheath] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[graylog_0][2], [graylog_0][0], [graylog_0][3], [graylog_0][3], [graylog_0][2], [graylog_0][0]] ...]).
[2016-04-30 17:31:19,771][INFO ][cluster.service          ] [Blackheath] added {{graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5}{RpbfjSFUQgS0QLvUeFCFsw}{127.0.0.1}{127.0.0.1:9350}{client=true, data=false, master=false},}, reason: zen-disco-join(join from node[{graylog-24997aac-8188-49fb-afc3-5bc0c414bdc5}{RpbfjSFUQgS0QLvUeFCFsw}{127.0.0.1}{127.0.0.1:9350}{client=true, data=false, master=false}])

Environment

• Graylog Version: 2.0.0
• Elasticsearch Version: 2.3
• MongoDB Version: 3.2
• Operating System: Amazon Linux AMI 2016.03.0
• Browser version: Chrome | Safari
• JAVA Version: 1.8.0_66

[xmik]

I experience this too. I didn't see the login page at all, but I see the graylog web interface error. Another difference is that, the error I see, contains 127.0.0.1 IP address:

We are experiencing problems connecting to the Graylog server running on http://127.0.0.1:12900/. 

I see no errors in logs too (the lowest log level is by default INFO).

Environment

3 docker containers in 1 vm from images:

mongo:3.2.5
elasticsearch:2.3.2
graylog2/server:2.0.0-1

[0x4D31]

I had the same problem in my AWS instance, and just fixed it.
First you need to set "rest_transport_uri" to your public/accessible IP address (https://your-public-ip:12900). Then, make sure that you have access to port 12900. So you need to configure your security groups to allow access from your client to the graylog instance on ports 9000 and 12900.

[joschi]

@onedaywillcome1

elasticsearch_discovery_zen_ping_unicast_hosts = 0.0.0.0:9300

That won't work. You have a provide the specific address to at least one Elasticsearch node (same for discovery.zen.ping.unicast.hosts in the Elasticsearch configuration).

In general, I'd recommend using the public IP address of your EC2 instance in rest_listen_uri and web_listen_uri. Additionally make sure that the Elasticsearch nodes can communicate and use elasticsearch_network_host (Graylog) and network.host (Elasticsearch) to specify the network interfaces it they should be using.

[xmik]

Setting rest_transport_uri = http://my_vm_public_ip:12900 solved this! Thank you very much for suggesting this. I was actually setting this in two places and forgot about the second one.

To confirm that rest_transport_uri is set correctly: curl http://localhost:12900/system/cluster/node return string should contain "transport_address":"http://my_vm_public_ip:12900/"

Another helpful thing for me was to know that it takes ~5 minutes for Elasticsearch cluster to become green (curl -XGET 'http://localhost:9200/_cluster/health?pretty=true' shows that; 9200 is the Elasticsearch http port).

[joschi]

@xmik Thanks for the update! I'm closing this issue. Feel free to add a comment or open a new issue if anything else comes up.

[onedaywillcome1]

@0x4D31

Yes. web interface signin button fired and I logged in to homepage when I set public ip in rest_transport_uri. Thank you.

@joschi

I didnt understand why we need to set public ips in graylog config. In previous graylog 1.3.4, I was login to web interface by setting loopback ip in web_listen_uri of web interface plugin. However, it changed in this version.

By the way, I set below configs to able to access graylog web home page. In other case ( setting "loopback ip(127.0.0.1)" in rest_listen_uri and web_listen_uri), I am not able to reach web interface login page or reach web interface home page.

graylog conf:

rest_listen_uri = http://0.0.0.0:12900
rest_transport_uri = http://public-amazon-ip:12900
web_listen_uri = http://0.0.0.0:9000
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300

elasticsearch conf:
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]

[joschi]

@onedaywillcome1

In previous graylog 1.3.4, I was login to web interface by setting loopback ip in web_listen_uri of web interface plugin. However, it changed in this version.

Yes, and that has been documented in the Graylog documentation at http://docs.graylog.org/en/2.0/pages/configuring_webif.html

Regarding your Elasticsearch configuration, please read https://github.com/Graylog2/graylog2-server/issues/2165#issuecomment-216127231 again.

[SnazzyBootMan]

I have also come across this problem and have tried build some test servers in AWS on Centos 7.

I am using Java 1.8.0_102, Elasticsearch 2.4.0, GrayLog Server 2.0.3.

/etc/graylog/server/server.conf

rest_listen_uri = http://0.0.0.0:9000
rest_transport_uri = http://my_amazon_public_ip:12900
web_listen_uri = http://0.0.0.0:9000
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300

/etc/elasticsearch/elasticsearch.yml

cluster.name: graylog
path.data: /elasticsearch/data
path.logs: /var/log/elasticsearch
script.inline: false
script.indexed: false
script.file: false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]
transport.tcp.port: 9300

[joschi]

@SnazzyBootMan Graylog 2.0.x is incompatible with Elasticsearch 2.4.0. Either downgrade to ES 2.3.5 or upgrade to Graylog 2.1.1.

We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our public mailing list or join the #graylog channel on freenode IRC.

Thank you!

[SnazzyBootMan]

Thanks @joschi , I have upgraded Graylog and I am still unable to get a login prompt with the server start up log giving no clues to a potential issue.

[onedaywillcome1]

@SnazzyBootMan Can you change config as below and test it? And is there any error in graylog log file : /var/log/graylog-server/server.log ?

rest_listen_uri = http://0.0.0.0:12900/

[joschi]

@onedaywillcome1 @SnazzyBootMan As I already wrote before, please post this issue to our public mailing list or join the #graylog channel on freenode IRC.