Coresnap

coresnap consists of two primary components. The archive tool and coresnapd. archive is responsible for writing out core files to disk and communicating with the coresnapd journaling mechanism. archive is only relevant to Linux targets and is used to handle writes and invocations from the core_pattern mechanism.

coresnap invokes the Backtrace snapshot tool on core files automatically and then sends the resulting snapshot to the object store using the object store client. Configuration of coresnap consists of installing the package, supplying a coroner configuration for coresnapto pass to the object store client and then enabling the service.

Please note that some of the command snippets require administrator privileges.

Installation

These steps require a license number from Backtrace to install the necessary packages. Please contact us to receive a license number before proceeding.

RHEL

Debian

Ubuntu

Configuration

Please refer to the coroner documentation for coroner-specific configuration options. Your site administrator or team lead probably already have one for your environment. All you have to do is place your coroner configuration file in /usr/local/etc/coroner.cf. This path may be changed by modifyingcoresnap.conf.

If you wish to modify the Coresnap configuration file, copy /opt/backtrace/etc/coresnap/coresnap.confto /usr/local/etc/coresnap/coresnap.conf or /etc/coresnap/coresnap.conf and then modify your new configuration file. Refer to the configuration file for configuration options.

Remove Conflicts

Ubuntu

In order to disable the apport crash reporting service, the following commands can be used.

It is also possible simply uninstall the apport service with the following commands.

RHEL

Enable

The final step is to enable coresnap. You want to disable any crash-reporting solution that is currently enabled on your platform.

init.d

The status of coresnapd should report that it is up:

On Ubuntu systems that are using Upstart, the following line enables Coresnap on boot.

On RHEL systems that are still using init.d then the following sequence of commands can be used to enable Coresnap on boot.

systemd

The status of coresnapd should report that it is up:

At this point, enable coresnapd with the following command.

FreeBSD

Consult the dedicated page for FreeBSD.

Advanced Configuration

Configure coresnap to submit to your projects

Coresnap comes configured to submit all snapshots to the blackhole project by default. In the likely event that you have configured Coroner for other project names, you can modify your coresnap configuration to use these instead.

First, copy out the example coresnap.conf:

Find the line format.1 = blackhole. This specifies that blackhole is the default destination project. We will add a line above this to route crashes to a particular project:

The effect of this is that coresnap will submit a crash to the project named testapp using the token name testapp from coroner.cf, if the executable name ends in testapp.

This simple pattern should cover most cases. The default coresnap.conf has inline documentation explaining the various options for the format lines, if you need to pass values to ptrace and coroner in different ways.

Frequently Asked Questions

How do I see what coresnapd is doing?

Coresnap logs error messages in syslog. Refer to syslog to diagnose any potential issues. If there are problems in executing sub-processes, you may run coresnapd by hand with /opt/backtrace/sbin/coresnapd -f. This specifies foreground mode and forces command output mode to inherit. Command output is displayed on your terminal output in this case.

Which project are snapshots submitted to?

By default, all dumps are submitted to a "blackhole" project using the "blackhole" authentication token. Please ensure that these exist in coronerd and your coroner configuration file if this default is used. Otherwise, format rules are typically used for dynamic selection of projects.