no log4j2.properties in es_conf_dir

[Gurpartap]

Deployment of this Ansible role on new servers will get the default log4j2.properties provided by Elasticsearch without any override.

On a fresh install, with es_conf_dir=/opt/elasticsearch/config, there was no log4j2.properties inside the es_conf_dir.

RUNNING HANDLER [elastic.elasticsearch : restart elasticsearch] ***********************************************
fatal: [elasticidx-node1]: FAILED! => {
  "changed": false,
  "msg": "Unable to start service elasticsearch: Job for elasticsearch.service failed because a timeout was exceeded.\nSee \"systemctl status elasticsearch.service\" and \"journalctl -xe\" for details.\n"
}

I had to cp /etc/elasticsearch/log4j2.properties /opt/elasticsearch/config/ to get it moving.

7.10

[jmlrt]

Hi @Gurpartap,

Thanks for opening this issue.

Indeed, this role doesn't copy the log4j2.properties file from deb/rpm default directory (/etc/elasticsearch/log4j2.properties) when es_config_dir is overrided.

That's something we could add if you're interrested to submit a PR.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic[bot]]

This issue has been automatically closed because it has not had recent activity since being marked as stale.

[Gurpartap]

Issue reported has not been fixed, afaik.

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic[bot]]

This issue has been automatically closed because it has not had recent activity since being marked as stale.