In rook, if you enable the `logCollector`, the core dump should be collected under `ls -lhsa /var/lib/systemd/coredump`. could you double check if logCollector is enabled, and also how the process is terminated?. Please check this upstream comment https://github.com/rook/rook/issues/10788#issuecomment-1280809186 where we have confirmed that core dump is collected once the process is terminated. Also, you can read https://rook.github.io/docs/rook/latest/CRDs/Cluster/ceph-cluster-crd/#cluster-settings under `logCollector` ``` logCollector: The settings for log collector daemon. enabled: if set to true, the log collector will run as a side-car next to each Ceph daemon. The Ceph configuration option log_to_file will be turned on, meaning Ceph daemons will log on files in addition to still logging to container's stdout. These logs will be rotated. In case a daemon terminates with a segfault, the coredump files will be commonly be generated in /var/lib/systemd/coredump directory on the host, depending on the underlying OS location. ```
Given the sort time (the 2nd of May is DF), this requires some good work IMO and testing too. We can try to get this in 4.13.z. @tnielsen Thoughts on this?
What changes are needed in Rook? If I follow the links from the conversation above, this mentions changes to systemd: https://bugzilla.redhat.com/show_bug.cgi?id=2098118#c63 That may work for RHCS, but not in an OCP environment, or at least Rook doesn't have the ability to modify systemd.
I was not aware that Rook doesn't have the ability to modify systems. So, I think we can move this other component since these only require changes on systems. cc @muagarwa
Subham, Travis, and Mudit, what do you think?
(In reply to Bipin Kunal from comment #8) > Subham, Travis, and Mudit, what do you think? Make sense to open Jira on ocp team and meantime have the documentation ready.
We should keep it open and mark it as a tracker for OCP BZ
@muagarwa could you help by opening the OCP BZ? I'm not sure what the right process here is since they are using Jira now.
I converted the Jira raised by Subham to OCP bug, please check if the component is correct or not. https://issues.redhat.com/browse/OCPBUGS-16786
Closing this bz since the Jira mentioned above is closed. cc @muagarwa