# DNS lookup failure "X.X.X": lookup X.X.X on \[::1\]:53: dial udp \[::1\]:53: socket: too many open files

**URL:** <https://discuss.elastic.co/t/dns-lookup-failure-x-x-x-lookup-x-x-x-on-1-dial-udp-1-socket-too-many-open-files/168667>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 16, 2019, 4:48am UTC](https://discuss.elastic.co/t/dns-lookup-failure-x-x-x-lookup-x-x-x-on-1-dial-udp-1-socket-too-many-open-files/168667 "2019-02-16T04:48:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 16, 2019, 4:48am UTC](https://discuss.elastic.co/t/dns-lookup-failure-x-x-x-lookup-x-x-x-on-1-dial-udp-1-socket-too-many-open-files/168667/1 "2019-02-16T04:48:45Z")

</div>

Hello World!

I'm using Elastic stack 6.6.1 and my metricbeat worked fine for a while, then it stopped on it's own and I'm seeing following error in `/var/log/metricbeat/metricbeat`:

```
2019-02-16T04:36:05.176Z	WARN	transport/tcp.go:53	DNS lookup failure "X.X.X": lookup X.X.X on [::1]:53: dial udp [::1]:53: socket: too many open files
2019-02-16T04:36:05.178Z	ERROR	[centralmgmt]	management/manager.go:193	error retrieving new configurations, will use cached ones: fail to execute the HTTP GET request: Get https://X.X.X:443/api/beats/agent/62e347c7-09e5-4fbf-b131-23f158f8d8a3/configuration?validSetting=true: lookup X.X.X on [::1]:53: dial udp [::1]:53: socket: too many open files
2019-02-16T04:36:25.575Z	ERROR	instance/metrics.go:91	Error while getting memory usage: error retrieving process stats: cannot find matching process for pid=7959
2019-02-16T04:36:25.584Z	ERROR	instance/metrics.go:135	Error retrieving CPU percentages: error retrieving process stats: cannot find matching process for pid=7959
2019-02-16T04:36:25.584Z	ERROR	instance/metrics_file_descriptors.go:39	Error while retrieving FD information: error retrieving process stats: cannot find matching process for pid=7959

```

I've used: `systemctl restart metricbeat` to resolve issue, however this isn't the first time it happens...

I'm using Google's DNS, pretty sure they're up)

```
# ulimit 
unlimited
# 

```

Please advise.

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [February 25, 2019, 7:47pm UTC](https://discuss.elastic.co/t/dns-lookup-failure-x-x-x-lookup-x-x-x-on-1-dial-udp-1-socket-too-many-open-files/168667/2 "2019-02-25T19:47:43Z")

</div>

Hi @alexus,

There is a bug causing a file descriptor leak with central management, find it here: [https://github.com/elastic/beats/issues/10491](https://github.com/elastic/beats/issues/10491) This could be causing your problems.

There is a PR in progress that could fix this issue: [https://github.com/elastic/beats/pull/10599](https://github.com/elastic/beats/pull/10599)

Take into account that central management is currently beta.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 25, 2019, 7:47pm UTC](https://discuss.elastic.co/t/dns-lookup-failure-x-x-x-lookup-x-x-x-on-1-dial-udp-1-socket-too-many-open-files/168667/3 "2019-03-25T19:47:49Z")

</div>

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