# Log entries on stdout and not in the log file

**URL:** <https://discuss.elastic.co/t/log-entries-on-stdout-and-not-in-the-log-file/11918>\
**Category:** Elasticsearch\
**Created:** [May 11, 2013, 1:44am UTC](https://discuss.elastic.co/t/log-entries-on-stdout-and-not-in-the-log-file/11918 "2013-05-11T01:44:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![the\_nozzle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/the_nozzle/32/1935_2.png) [@the\_nozzle](https://discuss.elastic.co/u/the_nozzle)\
**Post date:** [May 11, 2013, 1:44am UTC](https://discuss.elastic.co/t/log-entries-on-stdout-and-not-in-the-log-file/11918/1 "2013-05-11T01:44:00Z")

</div>

for some odd reason I am not getting any logs written out with 0.9 (if I  
start ES with the init.d script it dumps all of the entries to stdout) ..  
The final ES command is as follows :

java -Xms12g -Xmx12g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC  
-XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75  
-XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError  
-Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid  
-Des.path.home=/usr/share/elasticsearch -cp  
:/usr/share/elasticsearch/lib/elasticsearch-0.90.0.jar:/usr/share/elasticsearch/lib/_:/usr/share/elasticsearch/lib/sigar/_  
-Des.config=/usr/share/elasticsearch/config/elasticsearch.yml  
-Des.path.conf=/usr/share/elasticsearch/config  
-Des.path.home=/usr/share/elasticsearch  
-Des.path.logs=/var/log/elasticsearch -Des.path.data=/var/lib/elasticsearch  
-Des.path.work=/tmp/elasticsearch  
-Des.path.plugins=/usr/share/elasticsearch/plugins  
org.elasticsearch.bootstrap.ElasticSearch

/usr/share/elasticsearch/config/logging.yml (I tried it both using the  
variables and hardcoding the path -  
the uncommented line should be result when those var are evaluated..):

rootLogger: INFO,file  
logger:

# log action execution errors for easier debugging

action: DEBUG

# reduce the logging for aws, too much is logged under the default INFO

com.amazonaws: WARN

# gateway

#gateway: DEBUG  
#index.gateway: DEBUG

# peer shard recovery

#index.shard.recovery: DEBUG

# discovery

#discovery: TRACE

appender:  
file:  
type: file  
#file: ${path.logs}/${cluster.name}.log  
file: /var/log/elasticsearch/cmdb-test.log  
layout:  
type: pattern  
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"

... the log directory is owned by ES process user so def. not a perms  
issue .. What am I doing wrong ? Thanks for any help in advance.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:37am UTC](https://discuss.elastic.co/t/log-entries-on-stdout-and-not-in-the-log-file/11918/2 "2017-07-06T02:37:06Z")

</div>