Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 7. Contacting Red Hat Support Service
If the information in this guide did not help you to solve the problem, this chapter explains how you contact the Red Hat Support Service.
7.1. Providing Information to Red Hat Support Engineers
If you are unable to fix problems related to Red Hat Ceph Storage by yourself, contact the Red Hat Support Service and provide sufficient amount of information that helps the support engineers to faster troubleshoot the problem you encounter.
Procedure: Providing Information to Red Hat Support Engineers
- Open a support ticket on the Red Hat Customer Portal.
-
Ideally, attach an
sosreportto the ticket. See the What is a sosreport and how to create one in Red Hat Enterprise Linux 4.6 and later? solution for details. - If the Ceph daemons failed with a segmentation fault, consider generating a human-readable core dump file. See Section 7.2, “Generating Readable Core Dump Files” for details.
7.2. Generating Readable Core Dump Files
When a Ceph daemon terminates unexpectedly with a segmentation fault, gather the information about its failure and provide it to the Red Hat Support Engineers.
Such information speeds up the initial investigation. Also, the Support Engineers can compare the information from the core dump files with Red Hat Ceph Storage known issues.
Before You Start
Install the
ceph-debuginfopackage if it is not installed already.Enable the repository containing the
ceph-debuginfopackage:subscription-manager repos --enable=rhel-7-server-rhceph-2-<daemon>-debug-rpms
subscription-manager repos --enable=rhel-7-server-rhceph-2-<daemon>-debug-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace
<daemon>withosdormondepending on the type of the node.Install the
ceph-debuginfopackage:yum install ceph-debuginfo
# yum install ceph-debuginfoCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Ensure that the
gdbpackage is installed and if it is not, install it:yum install gdb
# yum install gdbCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure: Generating Readable Core Dump Files
Enable generating core dump files for Ceph.
Set the proper
ulimitsfor the core dump files by adding the following parameter to the/etc/systemd/system.conffile:DefaultLimitCORE=infinity
DefaultLimitCORE=infinityCopy to Clipboard Copied! Toggle word wrap Toggle overflow Comment out the
PrivateTmp=trueparameter in the Ceph daemon service file, by default located at/lib/systemd/system/<cluster-name>-<daemon>@.service:PrivateTmp=true
# PrivateTmp=trueCopy to Clipboard Copied! Toggle word wrap Toggle overflow Set the
suid_dumpableflag to2to allow the Ceph daemons to generate dump core files:sysctl fs.suid_dumpable=2
# sysctl fs.suid_dumpable=2Copy to Clipboard Copied! Toggle word wrap Toggle overflow Adjust the core dump files location:
sysctl kernel.core_pattern=/tmp/core
# sysctl kernel.core_pattern=/tmp/coreCopy to Clipboard Copied! Toggle word wrap Toggle overflow Reload the
systemdservice for the changes to take effect:systemctl daemon-reload
# systemctl daemon-reloadCopy to Clipboard Copied! Toggle word wrap Toggle overflow Restart the Ceph daemon for the changes to take effect:
systemctl restart ceph-<daemon>@<ID>
systemctl restart ceph-<daemon>@<ID>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Specify the daemon type (
osdormon) and its ID (numbers for OSDs, or short host names for Monitors) for example:systemctl restart ceph-osd@1
# systemctl restart ceph-osd@1Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- Reproduce the failure, for example try to start the daemon again.
Use the GNU Debugger (GDB) to generate a readable backtrace from an application core dump file:
gdb /usr/bin/ceph-<daemon> /tmp/core.<PID>
gdb /usr/bin/ceph-<daemon> /tmp/core.<PID>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Specify the daemon type and the PID of the failed process, for example:
gdb /usr/bin/ceph-osd /tmp/core.123456
$ gdb /usr/bin/ceph-osd /tmp/core.123456Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the GDB command prompt apply the
backtracecommand to all threads of the process by enteringthr a a bt:(gdb) thr a a bt
(gdb) thr a a btCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Copy and paste the output from the previous command into a support ticket.
See Also
- The How to use gdb to generate a readable backtrace from an application core solution on the Red Hat Customer Portal
- The How to enable core file dumps when an application crashes or segmentation faults solution on the Red Hat Customer Portal
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}