Graylog2 / Graylog2/graylog2-server

no node-id file created at startup for slace nodes

Open
#4,978 0 comments 0 reactions 0 assignees 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 configured a 3 nodes clusters, 2 of the new nodes are clones of the first one. I have followed all the step in order to have mongodb and elasticsearch in cluster mode and set node1 as the graylog master. When I started all the nodes, I can only see 1 node listed even if the 2 other nodes (let's say node2 and mode3) are started successfully. I see that the node-id file was not created at started like it is supposed to. After creating the file and put a string in it (like the one from node1 + 1), and restarted the graylog server on node2 and node3, they now appear in the webgui

## Expected Behavior

node-id should be recreated and populated if it has been deleted by hand

An error message in the log should indicate the issue

## Current Behavior

No node-id created

## Possible Solution

Maybe but that in the documentation has a manual fix?

## Steps to Reproduce (for bugs)

* Install a single node using official doc
* clone the vm to create 2 other nodes
* remove the node-id file on node2 and node3
* configure mongodb and elastic on node1-2-3 has cluster

1.
2.
3.
4.

## Context

## Your Environment

* Graylog Version: 2.4.6+ceaa7e4
* Elasticsearch Version: elasticsearch-5.6.10-1.noarch
* MongoDB Version: MongoDB server version: 3.6.6
* Operating System: CentOS Linux release 7.5.1804 (Core)
* Browser version:

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.