Feedback on epas 15 - "Enabling core dumps"

[tureba]

Summary

There are multiple issues with this page, causing customers to follow incorrect instructions.

To name a few:

• The page covers EL 7, EL 8, but not EL 9, where the instructions are meant to be different, with the presence of systemd-coredump. Additionally, some steps of the instructions seem outdated and are not aligned with Red Hat's usual directions on the matter. We should align our instructions with the OS vendors'.
• The page covers Debian 10 and Ubuntu 18.04 and 20.04. But we now support Debian 11 and Ubuntu 22.04, and we have dropped support of Ubuntu 18.04. So the instructions should be reviewed for the new ones, to check for any changes.
• We support SLES, but there are no instructions for the supported versions of it.
• The page instructs on editing files of /usr/lib/systemd/system and /lib/systemd/system. This is a mistake. Files in those locations should never be edited, especially ones that are provided by our packages. Instead, the instructions should explain how to use systemd edit or to create override files in /etc/systemd/system. More details on how to edit systemd service files can be found in man systemd.unit.
• The page instructs that to change the core dump limit, the reader has to change both the database service file as well as /etc/systemd/system.conf. That is also incorrect. Any one of those changes is enough, and providing both wastes time during troubleshooting, and may enable core dump files to all processes of the reader's system, which is not necessary (and might exhaust disk space in case of third party softwares crashing, as was observed in the past). The page should only explain how to change the database service, not the global setting.

Unfortunately I don't have the cycles to fix these things myself right now, so I'm only reporting for the moment.

Where did you see the problem?

https://github.com/EnterpriseDB/docs/blob/main/product_docs/docs/epas/15/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx

Expected behavior

No response

Screenshots

No response

Browser / Platform

No response

Additional notes

No response

[josh-heyer]

Thanks @tureba - we'll take a look and see if we can't get these addressed soon.

[josh-heyer]

Waiting on developer input - may be a bit