# Problems creating a single node cluster

**URL:** <https://discuss.elastic.co/t/problems-creating-a-single-node-cluster/219984>\
**Category:** Elasticsearch\
**Created:** [February 19, 2020, 2:23pm UTC](https://discuss.elastic.co/t/problems-creating-a-single-node-cluster/219984 "2020-02-19T14:23:06Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 19, 2020, 7:09pm UTC](https://discuss.elastic.co/t/problems-creating-a-single-node-cluster/219984/8 "2020-02-19T19:09:01Z")

</div>

> [@waynesmallman](#):
>
> What else would I need to do?

As with [your previous thread](https://discuss.elastic.co/t/elastic-failing-on-ubuntu-18-on-aws/219531), it's hard to give any concrete suggestions without seeing the Elasticsearch logs. I don't really understand why you cannot see them, sorry, but without them we're kinda stuck. I tried again to reproduce this (see my post in your earlier thread, a clean installation on a brand-new Ubuntu 18.04 instance) and `sudo tail -f /var/log/elasticsearch/elasticsearch.log` shows the logs we need.

Have you adjusted the logging config from the default? If so, can you put it back to how it was? There's certainly been some customisation because `this node must discover master-eligible nodes [52.2.0.8] to bootstrap a cluster` is not how an empty installation behaves.

---

_[View the full topic](https://discuss.elastic.co/t/problems-creating-a-single-node-cluster/219984)._