# Duplicate message in nginx logs

**URL:** <https://discuss.elastic.co/t/duplicate-message-in-nginx-logs/90757>\
**Category:** Logstash\
**Created:** [June 25, 2017, 2:32pm UTC](https://discuss.elastic.co/t/duplicate-message-in-nginx-logs/90757 "2017-06-25T14:32:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pietia](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@Pietia](https://discuss.elastic.co/u/Pietia)\
**Post date:** [June 25, 2017, 2:32pm UTC](https://discuss.elastic.co/t/duplicate-message-in-nginx-logs/90757/1 "2017-06-25T14:32:37Z")

</div>

problem is solved it was beats sending messages over to elastic directly .

---

<div class="post-metadata">

**Author:** ![Pietia](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@Pietia](https://discuss.elastic.co/u/Pietia)\
**Post date:** [June 25, 2017, 3:12pm UTC](https://discuss.elastic.co/t/duplicate-message-in-nginx-logs/90757/2 "2017-06-25T15:12:05Z")

</div>

Ok seems like I found the issue and it's a problem with filebeats on master elk stack server.  
When I installed filebeats on another host the messages went ok.

---

<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:** [July 23, 2017, 3:12pm UTC](https://discuss.elastic.co/t/duplicate-message-in-nginx-logs/90757/3 "2017-07-23T15:12:08Z")

</div>

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