How to Use getappcore for SUSE Support

This document (7018642) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 11

Situation

An application is crashing and support is asking for a getappcore for further analysis.

Resolution

If the application is not generating a core file already when crashing review the following applicable TID to get the core file needed by getappcore:

"How to obtain application core dumps"
"How to obtain systemd service core dumps"

The crash should generate a file called 'core' or 'core.<pid>'.
If the core file is compressed please decompress it before using getappcore.

Then run the following:

# getappcore -ur <SR/Case number> -b <path to application executable> <path to core file>

For example, it might look something like this if perl were crashing and the core file was named core in the /tmp directory:

# getappcore -ur 00123456 -b /usr/bin/perl /tmp/core

This command will create the tarball file that the support team needs.

Additional Information

# getappcore -h
Usage: /sbin/getappcore [OPTION] COREFILE
 
getappcore creates an archive containing an application core, and all files
required to analyze the application core - including the binary which
created the core, and all required shared libraries. Included in the
archive is a logfile containing RPM version information for further
investigation by SUSE.
 
Required parameter:
 
  COREFILE        The application core file, typically found in the working
                             directory of the application, or /
 
Optional parameters:
 
  -h                         This screen
  -b [BINARY]       Binary which generated [COREFILE]
  -r [SR Number]  SUSE Service Request number associated with this issue
  -u                         Automatically upload archive to the SUSE FTP server using HTTPS
  -f                          Automatically upload archive to the SUSE FTP server using FTPES
  -v                          Enable verbose messages
 
For example:
 
   getappcore -ur 00123456 -b /bin/rpm -j 2344
   getappcore -ur 00123456 -b /bin/rpm /core.15832


Please note in older versions of getappcore the parameters still show the URL of the old ftp server:
-u              Automatically upload archive to ftp.novell.com:/incoming
Update the supportutils package to the latest available version. After the update the option will show:
-u              Automatically upload archive to the SUSE FTP server using HTTPS

In case of SLES11 SP4 LTSS don't use the -u parameter and instead upload the archive manually.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7018642
  • Creation Date: 17-Feb-2017
  • Modified Date:23-Feb-2021
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center