# Recovering xpack log4j configuration from not standart path

**URL:** <https://discuss.elastic.co/t/recovering-xpack-log4j-configuration-from-not-standart-path/77786>\
**Category:** Elasticsearch\
**Created:** [March 8, 2017, 9:17am UTC](https://discuss.elastic.co/t/recovering-xpack-log4j-configuration-from-not-standart-path/77786 "2017-03-08T09:17:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![olorasde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olorasde/32/40103_2.png) [@olorasde](https://discuss.elastic.co/u/olorasde)\
**Post date:** [March 8, 2017, 9:17am UTC](https://discuss.elastic.co/t/recovering-xpack-log4j-configuration-from-not-standart-path/77786/1 "2017-03-08T09:17:55Z")

</div>

Hi,

I'm trying to configure the xpack audit logs in an EL installation that has the configuration outside the usual elasticsearch directory (path\_base/config/).

I have xpack settings on two sites right now.

- /base\_path/config/x-pack
- /other\_conf\_path/conf/elasticsearch/x-pack

When I start the service of elasticsearch that is configured, I do it this way:

...  
ExecStart =/data/lmelk/tools/elasticsearch/bin/elasticsearch   
-p $ {PID\_DIR} /elasticsearch.pid   
--quiet   
-Edefault.path.logs = $ {LOG\_DIR}   
-Edefault.path.data = $ {DATA\_DIR}   
-Edefault.path.conf = $ {CONF\_DIR}  
...

Where $ {CONF\_DIR} is informed with the value /other\_conf\_path/conf/elasticsearch

The system works fine, and I retrieve the configuration of the elasticsearch.yml and log4j.properties from the directory I want. But it's not the same with x-pack.

For some reason, I do not read the log4j x-pack configuration I have stored in /other\_conf\_path/conf/elasticsearch /x-pack but the default one in /base\_path/config/x-pack

Writing the audit log to the root of the installation, in /base\_path/

I may be missing some additional configuration at startup? Or something else?

Any ideas?

Regards,

---

<div class="post-metadata">

**Author:** ![olorasde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/olorasde/32/40103_2.png) [@olorasde](https://discuss.elastic.co/u/olorasde)\
**Post date:** [March 8, 2017, 2:06pm UTC](https://discuss.elastic.co/t/recovering-xpack-log4j-configuration-from-not-standart-path/77786/2 "2017-03-08T14:06:50Z")

</div>

False alarm, do not configure the path of the x-pack log4j.properties file well.

After proper updating, the log is spelled correctly.

---

<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:** [April 5, 2017, 2:06pm UTC](https://discuss.elastic.co/t/recovering-xpack-log4j-configuration-from-not-standart-path/77786/3 "2017-04-05T14:06:50Z")

</div>

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