pranavbhole commented on issue #17429:
URL: https://github.com/apache/druid/issues/17429#issuecomment-2445901341
I received a response from Azul regarding the Zulu JDK crash. I informed
them that the issue is consistently reproducible (still occurring with the
latest master commit). Azul has requested a core dump as well as list of shared
libraries to analyze the crash.
```
There is
# Core dump will be written. Default location: Core dumps may be processed
with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or
dumping to /home/runner/work/druid/druid/processing/core.3533)
and
rlimit (soft/hard): STACK 16384k/infinity , CORE 0k/infinity , NPROC
63899/63899 , NOFILE 65536/65536 , AS infinity/infinity , CPU infinity/infinity
, DATA infinity/infinity , FSIZE infinity/infinity , MEMLOCK 8192k/8192k
in hs_err file, that tells there might be a core dump in the system
generated after crash happened.
In case you manage to locate core file please collect the shared libs as
well.
You can use this command
grep '/.*\.so' hs_err_pid1913.log | awk '{ print $NF }' | uniq > libs.txt
Then run the following command on the resulting libs.txt file from above
tar -czf libs.tgz -T libs.txt
Upload core and libs.tgz to the file sharing resource and your convenience
and share the link to download.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
