# Request Assistance – Graylog Data Node Not Connecting

**URL:** <https://community.graylog.org/t/request-assistance-graylog-data-node-not-connecting/35158>\
**Category:** Graylog Central (peer support)\
**Created:** [March 8, 2025, 4:55am UTC](https://community.graylog.org/t/request-assistance-graylog-data-node-not-connecting/35158 "2025-03-08T04:55:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nidhim](https://avatars.discourse-cdn.com/v4/letter/n/3bc359/32.png) [@nidhim](https://community.graylog.org/u/nidhim)\
**Post date:** [March 8, 2025, 4:55am UTC](https://community.graylog.org/t/request-assistance-graylog-data-node-not-connecting/35158/1 "2025-03-08T04:55:51Z")

</div>

![graylog_error_post](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/9/8/98ebf5a9c1b5abbb3855dc44504399f0003b3a3c.png)

Hello Graylog Community,

I am setting up Graylog 6.1 in a Docker environment, but I am facing an issue where the **Data Node is not available** , and Graylog keeps retrying to connect.

I have been troubleshooting for a while but haven’t been able to resolve the issue. I would really appreciate any guidance on what might be causing this problem and how I can fix it.

My Setup:\*\*

- **Graylog Version:** `6.1`
- **Installation Type:** Docker
- **Graylog Data Node:** Yes
- **OpenSearch Installed:** ❌ No
- **Operating System:** Ubuntu 22.04 (running Docker)
- **Docker & Docker-Compose Installed:** ✅ Yes

Issue Description:\*\*

- When I check the **Graylog logs** , I repeatedly see the following error:

org.graylog2.configuration.IndexerDiscoveryProvider - Datanode is not available. Retry #XX

- The **Graylog UI shows “No Data Nodes Found”**
- Running `docker ps` shows that the **Graylog container is running**
- The **Data Node appears to be running** but is not recognized by Graylog

Steps I Have Taken to Troubleshoot:\*\*

1. **Checked running containers** with `docker ps`

- Graylog is running ✅
- Data Node is running ✅

1. **Restarted Graylog Data Node** (`docker restart <container-id>`)

- ❌ No effect

1. **Checked Graylog Logs** (`docker logs -f <graylog-container-id>`)

- The error **keeps repeating**

1. **Checked Open Ports in the Container** with:

netstat -tulnp

- The **Data Node port is listening** , but Graylog is not connecting

1. **Restarted the entire Graylog stack** :  
docker-compose down && docker-compose up -d

- ❌ Still no data node detected

1. **Checked the Graylog UI for Data Nodes**

- **It shows “No Data Nodes Found”**

Request for Help – My Questions:\*\*

1. **Why is Graylog not detecting the Data Node?**
2. **Do I need OpenSearch, or can I run Graylog with just the built-in Data Node?**
3. \*\*Is there a specific configuration I need to check in `docker-compose.yml`?
4. **Are there additional logs I should check to find the root cause?**

I would really appreciate any suggestions or guidance from the community.

Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![Joel\_Duffield](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Joel\_Duffield](https://community.graylog.org/u/Joel_Duffield)\
**Post date:** [March 8, 2025, 1:09pm UTC](https://community.graylog.org/t/request-assistance-graylog-data-node-not-connecting/35158/2 "2025-03-08T13:09:45Z")

</div>

So a couple really important things need to be able to happen. Can datanode talk to mongodb database over network, and is datanode configured to talk to mongo.

What bind and publish uri is set in datanode and is the graylog able to talk to that address.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [March 22, 2025, 1:10pm UTC](https://community.graylog.org/t/request-assistance-graylog-data-node-not-connecting/35158/3 "2025-03-22T13:10:41Z")

</div>

Closed on March 22, 2025, 1:10pm UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.