# Graylog 2.3 cluster issue

**URL:** <https://community.graylog.org/t/graylog-2-3-cluster-issue/3469>\
**Category:** Graylog Central (peer support)\
**Created:** [December 12, 2017, 3:57pm UTC](https://community.graylog.org/t/graylog-2-3-cluster-issue/3469 "2017-12-12T15:57:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [December 12, 2017, 6:43pm UTC](https://community.graylog.org/t/graylog-2-3-cluster-issue/3469/4 "2017-12-12T18:43:39Z")

</div>

did you checked the solution in the linked thread?

> [@Graylog 2.2 Cluster Issue](https://community.graylog.org/t/graylog-2-2-cluster-issue/697/6):
>
> After the Weekend I had the same messages on my node2. But i found the solution. If you get messages like: [NodePingThread] Did not find meta info of this node. Re-registering. Check your server clock! The time on all systems should be in sync! Maybe this helps some other, too.

---

_[View the full topic](https://community.graylog.org/t/graylog-2-3-cluster-issue/3469)._