Closed lennartkoopmann closed 9 years ago
How did you stop the server?
Cannot reproduce this on 1.0 :/
Tried to stop it with CTRL+C.
It happened to me during the old game of starting the cluster in office network, put macbook to sleep, open it again in hotel/home network and having the funny state of stale IPs in non-existant subnets. Probably nothing that happens to production servers but some change caused this to happen in the current master it seems and I don't know what other ES cluster connection states can cause this.
Probably close the ticket until somebody else complains or it happens to one of us.
Closing for now, couldn't reproduce. Please reopen if this comes up again.
0.92.3 running here. Same message (Couldn't point deflector to a new index
), same solution: kill -9
.
ES cluster: GREEN Graylog2 (before the kill): completely unresponsive: no response from API.
Restart of Graylog2 very quickly (within a minute) starts reporting it cannot contact ES (though ES still GREEN).
Reaction to that: kill all Graylog, stop ES cluster, wipe ES index completely, restart ES, restart Graylog2 (server + web).
this is the second time it happens, same "solution" both times. Problems appear to start occurring as soon as Graylog2 index reaches more than about 120 directories in ES (each configured to hold 2M documents).
Had to
kill -9
. This happened in the most recentmaster
and never happened before so it might have been introduced recently.