# Log files not forwarded to Elasticsearch

**URL:** <https://discuss.elastic.co/t/log-files-not-forwarded-to-elasticsearch/75495>\
**Category:** Logstash\
**Created:** [February 17, 2017, 1:04pm UTC](https://discuss.elastic.co/t/log-files-not-forwarded-to-elasticsearch/75495 "2017-02-17T13:04:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![renevdm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/renevdm/32/5730_2.png) [@renevdm](https://discuss.elastic.co/u/renevdm)\
**Post date:** [February 17, 2017, 8:57pm UTC](https://discuss.elastic.co/t/log-files-not-forwarded-to-elasticsearch/75495/2 "2017-02-17T20:57:11Z")

</div>

Seems to be the same issue as this:

> [@Fresh logstash 5.2 install gives log4j warnings and no logging from plugins](https://discuss.elastic.co/t/fresh-logstash-5-2-install-gives-log4j-warnings-and-no-logging-from-plugins/75530):
>
> I just downloaded the new logstash version (5.2.1), and after starting it I noticed a warning message saying that log4j needs to be initialized properly. I also noticed that plugins like kafka, beats, etc, were not emitting any output log... I used this very simple command to reproduce the problem on a Windows machine: $ bin\logstash -e "input{beats{port=\>5044}} output{stdout{}}" Could not find log4j2 configuration at path /Downloads/logstash-5.2.1/config/log4j2.properties. Using default con…

---

_[View the full topic](https://discuss.elastic.co/t/log-files-not-forwarded-to-elasticsearch/75495)._