Graylog2 / Graylog2/graylog2-server

Converting standalone Graylog server to cluster setup causes global inputs to fail

Open
#5,036 9 comments 0 reactions 1 assignee Claimed by @jalogisch View on GitHub
to-verify
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

I have total three nodes A, B and C.
Initially I was running graylog only on node A. Now, I am trying to have a graylog cluster with all three nodes A, B and C.
This also works fine I can see the nodes belognign to graylog cluster as shown below:
![image](https://user-images.githubusercontent.com/38486100/44895667-fbc7ec00-ad12-11e8-8cda-0763bf38825c.png)

## Expected Behavior
If global inputs were working in standalone mode it should also work in cluster setup.

## Current Behavior
But the global inputs fails to start on the new nodes B and C and complains that the address is already in use as shown below:
![image](https://user-images.githubusercontent.com/38486100/44841620-6d476200-ac61-11e8-849d-dc4ec1c85c59.png)

## Your Environment

* Graylog Version: 2.4.3
* Elasticsearch Version: 5.6.8
* MongoDB Version: 3.6.2
* Operating System: Red Hat Enterprise Linux Server 7.3
* Browser version: Chrome

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.