Graylog 3.0 interface will load after 2.5 -> 3.0 upgrade

2019-02-14T16:41:31.150Z INFO [JerseyService] Enabling CORS for HTTP endpoint

2019-02-14T16:41:46.441Z INFO [NetworkListener] Started listener bound to []

2019-02-14T16:41:46.443Z INFO [HttpServer] [HttpServer] Started.

2019-02-14T16:41:46.443Z INFO [JerseyService] Started REST API at <>

2019-02-14T16:41:46.443Z INFO [ServiceManagerListener] Services are healthy

2019-02-14T16:41:46.443Z INFO [InputSetupService] Triggering launching persisted inputs, node transitioned from Uninitialized [LB:DEAD] to Running [LB:ALIVE]

2019-02-14T16:41:46.444Z INFO [ServerBootstrap] Services started, startup times in ms: {JournalReader [RUNNING]=11, InputSetupService [RUNNING]=16, ConfigurationEtagService [RUNNING]=29, BufferSynchronizerService [RUNNING]=30, OutputSetupService [RUNNING]=40, KafkaJournal [RUNNING]=42, EtagService [RUNNING]=45, StreamCacheService [RUNNING]=81, PeriodicalsService [RUNNING]=223, LookupTableService [RUNNING]=289, JerseyService [RUNNING]=15877}

2019-02-14T16:41:46.449Z INFO [ServerBootstrap] Graylog server up and running.

Config is pointing to actual IP of instance though

Any thoughts?

http_bind_address <---- new option that got us :frowning:

the solution - read the upgrade docs

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.