Closed tharasavio closed 8 years ago
joschi
commented
8 years ago @tharasavio Thanks for reporting this!
Could you please attach the configurations of your Inputs to this issue? It looks like there's a UDP input (ID: 5733375ecb09100fbabb2994) which tries to bind to an unresolvable IP address.
joschi
commented
8 years ago @tharasavio Could you solve the issue? What was the problem?
tharasavio
commented
8 years ago @joschi
Sorry , the issue is different now . I am not able to attach as the files as it is in odt format
So I am pasting it here
2016-05-17T11:51:12.537-04:00 INFO [CmdLineTool] Running with JVM arguments: -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow -Dlog4j.configurationFile=file:///etc/graylog/server/log4j2.xml -Djava.library.path=/usr/share/graylog-server/lib/sigar -Dgraylog2.installation_source=deb
2016-05-17T11:51:16.242-04:00 INFO [InputBufferImpl] Message journal is enabled.
2016-05-17T11:51:16.415-04:00 INFO [LogManager] Loading logs.
2016-05-17T11:51:16.508-04:00 INFO [LogManager] Logs loading complete.
2016-05-17T11:51:16.508-04:00 INFO [KafkaJournal] Initialized Kafka based journal at /var/lib/graylog-server/journal
2016-05-17T11:51:16.524-04:00 INFO [InputBufferImpl] Initialized InputBufferImpl with ring size <65536> and wait strategy <BlockingWaitStrategy>, running 2 parallel message handlers.
2016-05-17T11:51:16.588-04:00 INFO [cluster] Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=5000}
2016-05-17T11:51:16.679-04:00 INFO [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-05-17T11:51:16.807-04:00 INFO [connection] Opened connection [connectionId{localValue:1, serverValue:256}] to localhost:27017
2016-05-17T11:51:16.818-04:00 INFO [cluster] Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 0, 12]}, minWireVersion=0, maxWireVersion=3, maxDocumentSize=16777216, roundTripTimeNanos=3780945}
2016-05-17T11:51:16.835-04:00 INFO [connection] Opened connection [connectionId{localValue:2, serverValue:257}] to localhost:27017
2016-05-17T11:51:17.417-04:00 INFO [NodeId] Node ID: 6192e8d0-80b2-4c5d-8d4d-c328270c1938
2016-05-17T11:51:17.570-04:00 INFO [node] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] version[2.3.1], pid[32662], build[bd98092/2016-04-04T12:25:05Z]
2016-05-17T11:51:17.571-04:00 INFO [node] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] initializing ...
2016-05-17T11:51:17.577-04:00 INFO [plugins] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] modules [], plugins [graylog-monitor], sites []
2016-05-17T11:51:19.212-04:00 INFO [node] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] initialized
2016-05-17T11:51:19.375-04:00 INFO [Version] HV000001: Hibernate Validator 5.2.4.Final
2016-05-17T11:51:19.527-04:00 INFO [ProcessBuffer] Initialized ProcessBuffer with ring size <65536> and wait strategy <BlockingWaitStrategy>.
2016-05-17T11:51:23.190-04:00 INFO [RulesEngineProvider] No static rules file loaded.
2016-05-17T11:51:23.467-04:00 WARN [GeoIpResolverEngine] GeoIP database file does not exist: /tmp/GeoLite2-City.mmdb
2016-05-17T11:51:23.480-04:00 INFO [OutputBuffer] Initialized OutputBuffer with ring size <65536> and wait strategy <BlockingWaitStrategy>.
2016-05-17T11:51:24.475-04:00 INFO [ServerBootstrap] Graylog server 2.0.0 (2dc6c03) starting up
2016-05-17T11:51:24.475-04:00 INFO [ServerBootstrap] JRE: Oracle Corporation 1.8.0_91 on Linux 3.13.0-86-generic
2016-05-17T11:51:24.475-04:00 INFO [ServerBootstrap] Deployment: deb
2016-05-17T11:51:24.476-04:00 INFO [ServerBootstrap] OS: Ubuntu 14.04.4 LTS (trusty)
2016-05-17T11:51:24.476-04:00 INFO [ServerBootstrap] Arch: amd64
2016-05-17T11:51:24.481-04:00 WARN [DeadEventLoggingListener] Received unhandled event of type <org.graylog2.plugin.lifecycles.Lifecycle> from event bus <AsyncEventBus{graylog-eventbus}>
2016-05-17T11:51:24.531-04:00 INFO [PeriodicalsService] Starting 24 periodicals ...
2016-05-17T11:51:24.531-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ThroughputCalculator] periodical in [0s], polling every [1s].
2016-05-17T11:51:24.546-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.AlertScannerThread] periodical in [10s], polling every [60s].
2016-05-17T11:51:24.546-04:00 INFO [node] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] starting ...
2016-05-17T11:51:24.563-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.BatchedElasticSearchOutputFlushThread] periodical in [0s], polling every [1s].
2016-05-17T11:51:24.582-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ClusterHealthCheckThread] periodical in [0s], polling every [20s].
2016-05-17T11:51:24.595-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ContentPackLoaderPeriodical] periodical, running forever.
2016-05-17T11:51:24.603-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.GarbageCollectionWarningThread] periodical, running forever.
2016-05-17T11:51:24.611-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.IndexerClusterCheckerThread] periodical in [0s], polling every [30s].
2016-05-17T11:51:24.612-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.IndexRetentionThread] periodical in [0s], polling every [300s].
2016-05-17T11:51:24.612-04:00 INFO [IndexRetentionThread] Elasticsearch cluster not available, skipping index retention checks.
2016-05-17T11:51:24.628-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.IndexRotationThread] periodical in [0s], polling every [10s].
2016-05-17T11:51:24.633-04:00 INFO [connection] Opened connection [connectionId{localValue:3, serverValue:258}] to localhost:27017
2016-05-17T11:51:24.633-04:00 INFO [connection] Opened connection [connectionId{localValue:4, serverValue:259}] to localhost:27017
2016-05-17T11:51:24.640-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.NodePingThread] periodical in [0s], polling every [1s].
2016-05-17T11:51:24.642-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.VersionCheckThread] periodical in [300s], polling every [1800s].
2016-05-17T11:51:24.645-04:00 INFO [IndexerClusterCheckerThread] Indexer not fully initialized yet. Skipping periodic cluster check.
2016-05-17T11:51:24.658-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ThrottleStateUpdaterThread] periodical in [1s], polling every [1s].
2016-05-17T11:51:24.662-04:00 INFO [Periodicals] Starting [org.graylog2.events.ClusterEventPeriodical] periodical in [0s], polling every [1s].
2016-05-17T11:51:24.662-04:00 INFO [Periodicals] Starting [org.graylog2.events.ClusterEventCleanupPeriodical] periodical in [0s], polling every [300s].
2016-05-17T11:51:24.663-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ClusterIdGeneratorPeriodical] periodical, running forever.
2016-05-17T11:51:24.664-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.IndexRangesMigrationPeriodical] periodical, running forever.
2016-05-17T11:51:24.667-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.IndexRangesCleanupPeriodical] periodical in [15s], polling every [3600s].
2016-05-17T11:51:24.685-04:00 INFO [connection] Opened connection [connectionId{localValue:5, serverValue:260}] to localhost:27017
2016-05-17T11:51:24.691-04:00 INFO [connection] Opened connection [connectionId{localValue:6, serverValue:261}] to localhost:27017
2016-05-17T11:51:24.741-04:00 INFO [PeriodicalsService] Not starting [org.graylog2.periodical.UserPermissionMigrationPeriodical] periodical. Not configured to run on this node.
2016-05-17T11:51:24.741-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.AlarmCallbacksMigrationPeriodical] periodical, running forever.
2016-05-17T11:51:24.751-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.ConfigurationManagementPeriodical] periodical, running forever.
2016-05-17T11:51:24.760-04:00 INFO [Periodicals] Starting [org.graylog2.periodical.LdapGroupMappingMigration] periodical, running forever.
2016-05-17T11:51:24.778-04:00 INFO [Periodicals] Starting [org.graylog.plugins.usagestatistics.UsageStatsNodePeriodical] periodical in [300s], polling every [21600s].
2016-05-17T11:51:24.783-04:00 INFO [Periodicals] Starting [org.graylog.plugins.usagestatistics.UsageStatsClusterPeriodical] periodical in [300s], polling every [21600s].
2016-05-17T11:51:24.783-04:00 INFO [Periodicals] Starting [org.graylog.plugins.collector.periodical.PurgeExpiredCollectorsThread] periodical in [0s], polling every [3600s].
2016-05-17T11:51:24.938-04:00 INFO [transport] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] publish_address {127.0.0.1:9350}, bound_addresses {[::1]:9350}, {127.0.0.1:9350}
2016-05-17T11:51:24.950-04:00 INFO [discovery] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] graylog-development/h-tk8FmAQZep0wUsVQjSnQ
2016-05-17T11:51:25.239-04:00 INFO [AbstractJerseyService] Enabling CORS for HTTP endpoint
2016-05-17T11:51:27.960-04:00 WARN [discovery] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] waited for 3s and no initial state was set by the discovery
2016-05-17T11:51:27.960-04:00 INFO [node] [graylog-6192e8d0-80b2-4c5d-8d4d-c328270c1938] started
2016-05-17T11:51:28.052-04:00 INFO [NetworkListener] Started listener bound to [142.1.121.128:9000]
2016-05-17T11:51:28.053-04:00 INFO [HttpServer] [HttpServer] Started.
2016-05-17T11:51:28.055-04:00 INFO [WebInterfaceService] Started Web Interface at <http://142.1.121.128:9000/>
2016-05-17T11:51:32.966-04:00 WARN [IndexerSetupService] Could not connect to Elasticsearch
2016-05-17T11:51:32.966-04:00 INFO [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessible. Also check that the cluster name setting is correct.
2016-05-17T11:51:32.967-04:00 INFO [IndexerSetupService] See http://docs.graylog.org/en/2.0/pages/configuring_es.html for details.
2016-05-17T11:51:33.566-04:00 INFO [NetworkListener] Started listener bound to [127.0.0.1:12900]
2016-05-17T11:51:33.567-04:00 INFO [HttpServer] [HttpServer-1] Started.
2016-05-17T11:51:33.568-04:00 INFO [RestApiService] Started REST API at <http://127.0.0.1:12900/>
2016-05-17T11:51:33.569-04:00 INFO [ServiceManagerListener] Services are healthy
2016-05-17T11:51:33.571-04:00 INFO [ServerBootstrap] Services started, startup times in ms: {OutputSetupService [RUNNING]=32, MetricsReporterService [RUNNING]=33, BufferSynchronizerService [RUNNING]=45, KafkaJournal [RUNNING]=62, InputSetupService [RUNNING]=80, PeriodicalsService [RUNNING]=295, JournalReader [RUNNING]=297, WebInterfaceService [RUNNING]=3519, IndexerSetupService [RUNNING]=8438, RestApiService [RUNNING]=9051}
2016-05-17T11:51:33.576-04:00 INFO [InputSetupService] Triggering launching persisted inputs, node transitioned from Uninitialized?[LB:DEAD] to Running?[LB:ALIVE]
2016-05-17T11:51:33.580-04:00 INFO [ServerBootstrap] Graylog server up and running.
2016-05-17T11:51:33.616-04:00 INFO [InputStateListener] Input [GELF UDP/5733375ecb09100fbabb2994] is now STARTING
2016-05-17T11:51:33.645-04:00 ERROR [NettyTransport] Error in Input [GELF UDP/5733375ecb09100fbabb2994] (channel [id: 0xe91e0784])
**java.net.SocketException: Unresolved address
at sun.nio.ch.Net.translateToSocketException(Net.java:131) ~[?:1.8.0_91]
at sun.nio.ch.DatagramSocketAdaptor.bind(DatagramSocketAdaptor.java:93) ~[?:1.8.0_91]
at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.bind(NioDatagramPipelineSink.java:129) [graylog.jar:?]
at org.jboss.netty.channel.socket.nio.NioDatagramPipelineSink.eventSunk(NioDatagramPipelineSink.java:77) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.bindRequested(SimpleChannelHandler.java:299) [graylog.jar:?]
at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:265) [graylog.jar:?]
at **org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) [graylog.jar:?]
at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) [graylog.jar:?]
at org.jboss.netty.channel.Channels.bind(Channels.java:561) [graylog.jar:?]
at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:198) [graylog.jar:?]
at org.jboss.netty.bootstrap.ConnectionlessBootstrap.bind(ConnectionlessBootstrap.java:198) [graylog.jar:?]
at org.graylog2.plugin.inputs.transports.NettyTransport.launch(NettyTransport.java:136) [graylog.jar:?]
at org.graylog2.plugin.inputs.MessageInput.launch(MessageInput.java:153) [graylog.jar:?]
at org.graylog2.shared.inputs.InputLauncher$1.run(InputLauncher.java:84) [graylog.jar:?]
at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176) [graylog.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_91]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Net.java:101) ~[?:1.8.0_91]
at sun.nio.ch.DatagramChannelImpl.bind(DatagramChannelImpl.java:678) ~[?:1.8.0_91]
at sun.nio.ch.DatagramSocketAdaptor.bind(DatagramSocketAdaptor.java:91) ~[?:1.8.0_91]**
... 27 more**@tharasavio It still seems to be the same issue (at least according to the error message in the logs you've posted).
Could you please attach the configurations of your Inputs to this issue? It looks like there's a UDP input (ID: 5733375ecb09100fbabb2994) which tries to bind to an unresolvable IP address.
You can find the input configuration either by checking the web interface (System → Inputs) or in the MongoDB collection named "inputs".
Example with Mongo Shell:
$ mongo
MongoDB shell version: 3.2.6
connecting to: test
> use graylog;
switched to db graylog
> show collections;
[...]
index_ranges
inputs
ldap_settings
[...]
> db.inputs.find({ "_id": ObjectId("5733375ecb09100fbabb2994") }).pretty();
{
"_id" : ObjectId("5733375ecb09100fbabb2994"),
"creator_user_id" : "admin",
"configuration" : {
"override_source" : "",
"recv_buffer_size" : 16384,
"bind_address" : "127.0.0.1",
"port" : 5555
},
"name" : "Raw/Plaintext UDP",
"created_at" : ISODate("2015-06-30T12:54:08.682Z"),
"global" : false,
"type" : "org.graylog2.inputs.raw.udp.RawUDPInput",
"title" : "Raw UDP",
[...]
}@joschi
$ mongo MongoDB shell version: 3.0.12 connecting to: test Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see http://docs.mongodb.org/ Questions? Try the support group http://groups.google.com/group/mongodb-user Server has startup warnings:
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten]
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten] ** WARNING:
/sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten] ** We
suggest setting it to 'never'
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten]
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten] ** WARNING:
/sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten] ** We
suggest setting it to 'never'
2016-05-11T10:43:00.701-0400 I CONTROL [initandlisten]
> use graylog;
switched to db graylog
> show collections;
cluster_config
cluster_events
collectors
content_packs
grok_patterns
index_failures
index_ranges
inputs
nodes
notifications
pipeline_processor_pipelines
pipeline_processor_pipelines_streams
pipeline_processor_rules
roles
sessions
system.indexes
system_messages
users
> db.inputs.find({ "_id": ObjectId("5733375ecb09100fbabb2994") }).pretty();
{
"_id" : ObjectId("5733375ecb09100fbabb2994"),
"creator_user_id" : "admin",
"configuration" : {
"override_source" : null,
"recv_buffer_size" : 1048576,
"bind_address" : "gl2_private_IP",
"port" : 5140
},
"name" : "GELF UDP",
"created_at" : ISODate("2016-05-11T14:01:30.932Z"),
"global" : true,
"type" : "org.graylog2.inputs.gelf.udp.GELFUDPInput",
"title" : "Syslog",
"content_pack" : null
}@tharasavio Please make sure that gl2_private_IP is indeed the correct IP address and that it exists on the machine hosting Graylog (check with ip addr show or ifconfig -a).
tharasavio
commented
8 years ago @joschi . thanks i was not working on the system for the past two days. I forgot what change i made in the conf now I get the below message when i try to connect via web
We are experiencing problems connecting to the Graylog server running on http://127.0.0.1:12900//. Please verify that the server is healthy and working correctly.
tharasavio
commented
8 years ago Graylog config ### file
### ### # If you are running more than one instances of Graylog server you have to select one of these
# instances as master. The master will perform some periodical tasks that non-masters won't perform.
is_master = true
# The auto-generated node ID will be stored in this file and read after restarts. It is a good idea
# to use an absolute file path here if you are starting Graylog server from init scripts or similar.
node_id_file = /etc/graylog/server/node-id
# You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters.
# Generate one by using for example: pwgen -N 1 -s 96
password_secret =
# The default root user is named 'admin'
#root_username =
# You MUST specify a hash password for the root user (which you only need to initially set up the
# system and in case you lose connectivity to your authentication backend)
# This password cannot be changed using the API or via the web interface. If you need to change it,
# modify it in this file.
# Create one by using for example: echo -n yourpassword | shasum -a 256
# and put the resulting hash value into the following line
root_password_sha2 =
# The email address of the root user.
# Default is empty
#root_email = ""
# The time zone setting of the root user. See http://www.joda.org/joda-time/timezones.html for a list of valid time zones.
# Default is UTC
#root_timezone = UTC
# Set plugin directory here (relative or absolute)
plugin_dir = /usr/share/graylog-server/plugin
# REST API listen URI. Must be reachable by other Graylog server nodes if you run a cluster.
# When using Graylog Collectors, this URI will be used to receive heartbeat messages and must be accessible for all collectors.
#rest_listen_uri = http://142.1.121.128:12900/
# REST API transport address. Defaults to the value of rest_listen_uri. Exception: If rest_listen_uri
# is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 system address is used.
# If set, this will be promoted in the cluster discovery APIs, so other nodes may try to connect on
# this address and it is used to generate URLs addressing entities in the REST API. (see rest_listen_uri)
# You will need to define this, if your Graylog server is running behind a HTTP proxy that is rewriting
# the scheme, host name or URI.
#rest_transport_uri = http://192.168.1.1:12900/
#rest_transport_uri = http://142.1.121.128:12900/
# Enable CORS headers for REST API. This is necessary for JS-clients accessing the server directly.
# If these are disabled, modern browsers will not be able to retrieve resources from the server.
# This is enabled by default. Uncomment the next line to disable it.
#rest_enable_cors = false
# Enable GZIP support for REST API. This compresses API responses and therefore helps to reduce
# overall round trip times. This is disabled by default. Uncomment the next line to enable it.
#rest_enable_gzip = true
# Enable HTTPS support for the REST API. This secures the communication with the REST API with
# TLS to prevent request forgery and eavesdropping. This is disabled by default. Uncomment the
# next line to enable it.
#rest_enable_tls = true
"/etc/graylog/server/server.conf" 475L, 23714C 36,1 Top@tharasavio In Graylog 2.0.0 and later the way the web interface interacts with the Graylog REST API changed.
Please refer to http://docs.graylog.org/en/2.0/pages/configuring_webif.html for information about how to configure the web interface in Graylog 2.0.x.
Additionally I think it's better to move this discussion to one of our community support channels. Please post this issue to our public mailing list or join the #graylog channel on freenode IRC.
Thank you!
tharasavio
commented
8 years ago Hi,
It worked . Thanks for your help
Regards, Thara
On Thu, May 19, 2016 at 4:55 AM, Jochen Schalanda notifications@github.com wrote:
@tharasavio https://github.com/tharasavio In Graylog 2.0.0 and later the way the web interface interacts with the Graylog REST API changed.
Please refer to http://docs.graylog.org/en/2.0/pages/configuring_webif.html for information about how to configure the web interface in Graylog 2.0.x.
Additionally I think it's better to move this discussion to one of our community support channels. Please post this issue to our public mailing list https://groups.google.com/forum/#!forum/graylog2 or join the #graylog channel on freenode IRC https://webchat.freenode.net/?channels=%23graylog.
Thank you!
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/Graylog2/graylog2-server/issues/2240#issuecomment-220265880
thara
Problem description
when I restart the graylog , i get the following messages and in web interface i get Elasticsearch cluster unavailable
Steps to reproduce the problem
Environment
Version: 2.0.0 (2dc6c03), codename Rothaus JVM: PID 17995, Oracle Corporation 1.8.0_91 on Linux 3.13.0-86-generi