Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

put jvm crash logs in logs/ #13982

Closed
rmuir opened this issue Oct 6, 2015 · 10 comments · Fixed by #29028
Closed

put jvm crash logs in logs/ #13982

rmuir opened this issue Oct 6, 2015 · 10 comments · Fixed by #29028
Labels
:Core/Infra/Logging Log management and logging utilities :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts >enhancement Team:Delivery Meta label for Delivery team

Comments

@rmuir
Copy link
Contributor

rmuir commented Oct 6, 2015

This would be a great improvement over what probably happens today. See issues like #13600 where the jvm crashes and people are unaware of the log file (most likely in many cases its going to /tmp which is unexpected).

It would be better if we set -XX:ErrorFile explicitly...

@rjernst
Copy link
Member

rjernst commented Oct 7, 2015

+1

1 similar comment
@jpountz
Copy link
Contributor

jpountz commented Oct 7, 2015

+1

@nik9000 nik9000 self-assigned this Oct 7, 2015
@nik9000
Copy link
Member

nik9000 commented Oct 7, 2015

I'll have a look.

@clintongormley clintongormley added >enhancement :Core/Infra/Logging Log management and logging utilities labels Oct 7, 2015
@nik9000 nik9000 added the :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts label Oct 7, 2015
nik9000 added a commit to nik9000/elasticsearch that referenced this issue Oct 7, 2015
@clintongormley
Copy link

Closed by #14006

@rjernst
Copy link
Member

rjernst commented Jan 28, 2016

I don't think this issue was fixed? The linked PR was closed without merging. The problem, IIRC, is the location must be set when starting the jvm, but we have too many ways to set the log dir location, so determining that from the elasticsearch shell script is problematic.

@rjernst rjernst reopened this Jan 28, 2016
@jasontedor
Copy link
Member

@clintongormley I don't think #14006 was integrated, and I still think that this is something that we should do.

@clintongormley
Copy link

ah thanks - missed that

@nik9000 nik9000 removed their assignment Apr 22, 2016
@rjernst rjernst added :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts and removed :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts labels Mar 13, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@rjernst
Copy link
Member

rjernst commented Mar 13, 2018

I wonder if we could set the ErrorFile in the same way we set HeapDumpPath? In rpm/deb, we put it under /var/lib/elasticsearch, and for zip/tar, we have a commented out line in jvm.options.

@jasontedor
Copy link
Member

I opened #29028.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Logging Log management and logging utilities :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts >enhancement Team:Delivery Meta label for Delivery team
Projects
None yet
8 participants