Chapter 10. 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.
10.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 10.2, “Generating Readable Core Dump Files” for details.
10.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
ceph-debuginfopackage if it is not installed already.
Enable the repository containing the
subscription-manager repos --enable=rhel-7-server-rhceph-3-<daemon>-debug-rpms
mondepending on the type of the node.
# yum install ceph-debuginfo
Ensure that the
gdbpackage is installed and if it is not, install it:
# yum install gdb
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
Comment out the
PrivateTmp=trueparameter in the Ceph daemon service file, by default located at
2to allow the Ceph daemons to generate dump core files:
# sysctl fs.suid_dumpable=2
Adjust the core dump files location:
# sysctl kernel.core_pattern=/tmp/core
systemdservice for the changes to take effect:
# systemctl daemon-reload
Restart the Ceph daemon for the changes to take effect:
systemctl restart ceph-<daemon>@<ID>
Specify the daemon type (
mon) and its ID (numbers for OSDs, or short host names for Monitors) for example:
# systemctl restart ceph-osd@1
- 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>
Specify the daemon type and the PID of the failed process, for example:
$ gdb /usr/bin/ceph-osd /tmp/core.123456
In the GDB command prompt disable paging and enable logging to a file by entering the commands
set pag offand
set log on:
(gdb) set pag off (gdb) set log on
backtracecommand to all threads of the process by entering
thr a a bt full:
(gdb) thr a a bt full
After the backtrace is generated turn off logging by entering
set log off:
(gdb) set log off
Transfer the log file
gdb.txtto the system you access the Red Hat Customer Portal from and attach it to a support ticket.
- 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