OpenSearch/docs/reference/setup/important-settings/error-file.asciidoc

[[error-file-path]]
=== JVM fatal error logs

By default, Elasticsearch configures the JVM to write fatal error logs
to the default logging directory (this is `/var/log/elasticsearch` for
the <<rpm,RPM>> and <<deb,Debian>> package distributions, and the `logs`
directory under the root of the Elasticsearch installation for the
<<targz,tar>> and <<zip-windows,zip>> archive distributions). These are logs
produced by the JVM when it encounters a fatal error (e.g., a
segmentation fault). If this path is not suitable for receiving logs,
you should modify the entry `-XX:ErrorFile=...` in
<<jvm-options,`jvm.options`>> to an alternate path.
Add docs for error file configuration (#29032) This commit adds docs for configuring the error file setting for where the JVM writes fatal error logs. 2018-03-13 18:18:01 -04:00			`[[error-file-path]]`
			`=== JVM fatal error logs`

Configure error file for archive packages (#29129) This is a follow up to a previous change which set the error file path for the package distributions. The observation here is that we always set the working directory of Elasticsearch to the root of the installation (i.e., Elasticsearch home). Therefore, we can specify the error file path relative to this directory and default it to the logs directory, similar to the package distributions. 2018-03-18 15:33:17 -04:00			`By default, Elasticsearch configures the JVM to write fatal error logs`
			to the default logging directory (this is `/var/log/elasticsearch` for
			the <<rpm,RPM>> and <<deb,Debian>> package distributions, and the `logs`
			`directory under the root of the Elasticsearch installation for the`
Add docs for bundled jdk (#40487) This commit changes the note in docs about required java version to note the existence of the bundled jdk and how to bring your own java. It also reorganizes the zip/targz docs as zip is no longer suitable on Linux/MacOS. 2019-03-29 09:04:46 -04:00			`<<targz,tar>> and <<zip-windows,zip>> archive distributions). These are logs`
Configure error file for archive packages (#29129) This is a follow up to a previous change which set the error file path for the package distributions. The observation here is that we always set the working directory of Elasticsearch to the root of the installation (i.e., Elasticsearch home). Therefore, we can specify the error file path relative to this directory and default it to the logs directory, similar to the package distributions. 2018-03-18 15:33:17 -04:00			`produced by the JVM when it encounters a fatal error (e.g., a`
			`segmentation fault). If this path is not suitable for receiving logs,`
			you should modify the entry `-XX:ErrorFile=...` in
Add docs for error file configuration (#29032) This commit adds docs for configuring the error file setting for where the JVM writes fatal error logs. 2018-03-13 18:18:01 -04:00			<<jvm-options,`jvm.options`>> to an alternate path.