# Curator problem!

**URL:** https://discuss.elastic.co/t/curator-problem/131870
**Category:** Elasticsearch
**Created:** [May 15, 2018, 7:35am UTC](https://discuss.elastic.co/t/curator-problem/131870 "2018-05-15T07:35:19Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)
#### Post date: [May 15, 2018, 7:35am UTC](https://discuss.elastic.co/t/curator-problem/131870/1 "2018-05-15T07:35:19Z")

</div>

Hi,

I have a problem, I was sending logs from a server using Filebeat to my server. Once I set up the curator and I made the command : curator --config ..... ,The other server stopped sending the logs. Can someone explain to me why?

---

<div class="post-metadata">

### Author: ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 15, 2018, 12:01pm UTC](https://discuss.elastic.co/t/curator-problem/131870/2 "2018-05-15T12:01:07Z")

</div>

Curator only reads files, and interacts with Elasticsearch via an API. Do you have a limited number of sockets on the endpoint, and both Curator and Filebeat were trying to use them and they got exhausted?

---

<div class="post-metadata">

### Author: ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)
#### Post date: [May 15, 2018, 12:10pm UTC](https://discuss.elastic.co/t/curator-problem/131870/3 "2018-05-15T12:10:26Z")

</div>

The problem is, it change my logstash, I can't start it as a service anymore !! I don't know why, everything changes.

Everythnig was working before I just install curator and rename my conf file in logstash and everythnig goes wrong ...

---

<div class="post-metadata">

### Author: ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 15, 2018, 12:23pm UTC](https://discuss.elastic.co/t/curator-problem/131870/4 "2018-05-15T12:23:30Z")

</div>

Curator cannot do what you're describing. The only file it can write to is the log file you have set. It only ever reads from a configuration file you define, and interacts with Elasticsearch via the REST API, over the network.

Part of it may be:

> [@asalma](#):
>
> Everythnig was working before I just install curator and rename my conf file in logstash and everythnig goes wrong ...

With emphasis on, **"rename my conf file in logstash and everything goes wrong..."** Curator _cannot_ change your Logstash configuration, nor affect your systemd setup.

---

<div class="post-metadata">

### Author: ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)
#### Post date: [May 15, 2018, 12:26pm UTC](https://discuss.elastic.co/t/curator-problem/131870/5 "2018-05-15T12:26:20Z")

</div>

It is me who renamed my logstash conf, I gave an other name, and it's ruin mt logstash.

---

<div class="post-metadata">

### Author: ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 15, 2018, 12:27pm UTC](https://discuss.elastic.co/t/curator-problem/131870/6 "2018-05-15T12:27:23Z")

</div>

That's another topic. Clearly it is not a Curator problem.

---

<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: [June 12, 2018, 12:27pm UTC](https://discuss.elastic.co/t/curator-problem/131870/7 "2018-06-12T12:27:25Z")

</div>

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