Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

error::pass5(7stap) [centos man page]

ERROR::PASS5(7stap)													       ERROR::PASS5(7stap)

NAME
error::pass5 - systemtap pass-5 errors DESCRIPTION
Errors that occur during pass 5 (execution) can have a variety of causes. exceptional events during script execution The systemtap translator and runtime include numerous error checks that aim to protect the systems and the users from mistakes or transient conditions. The script may deliberately call the error() tapset function to signal a problem. Some memory needed for accessing $context variables may be temporarily unavailable. Consider using the try/catch construct to wrap script fragments in exception-handling code. Consider using the stap --suppress-handler-errors or stap --skip-badvars option. resource exhaustion One of several types of space or time resource limits may be exceeded by the script, including system overload, too many tuples to be stored in an array, etc. Some of the error messages identify the constraint by macro name, which may be individually raised. Consider using the stap --suppress-handler-errors option. Extend or disable resource limits using the stap -DLIMIT=NNNN option. remote execution server problems If you use the stap --remote option to direct a systemtap script to be executed somewhere else, ensure that an SSH connection may be made to the remote host, and that it has the current systemtap runtime installed & available. installation/permission problems It is possible that your installation of systemtap was not correctly installed. For example, the /usr/bin/staprun program may lack the necessary setuid permissions, or your invoking userid might not have sufficient privileges (root, or stapusr and related group memberships). Environment variables may interfere with locating /usr/libexec/.../stapio. errors from target program The program invoked by the stap -c CMD option may exit with a non-zero code. uncaught exceptions in the target program When using --runtime=dyninst you may encounter an issue where the target program aborts with a message like "terminate called after throwing an instance of 'foo_exception'". This is unfortunately a limitation of Dyninst, which sometimes prevents exceptions from properly unwinding through instrumented code. GATHERING MORE INFORMATION
Increasing the verbosity of pass-5 with an option such as --vp 00001 can help pinpoint the problem. SEE ALSO
stap(1), http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors, error::fault(7stap), error::reporting(7stap) ERROR::PASS5(7stap)

Check Out this Related Man Page

PMDASYSTEMTAP(1)					       Performance Co-Pilot						  PMDASYSTEMTAP(1)

NAME
pmdasystemtap - Systemtap performance metrics domain agent (PMDA) DESCRIPTION
pmdasystemtap is a Performance Metrics Domain Agent (PMDA) which exports metric values from the Linux Systemtap dynamic tracing toolkit. This implementation uses the stap(1) tool, which is a front-end to the Systemtap toolkit. INSTALLATION
In order to access performance data exported by Systemtap from with PCP, it is necessary to perform two configuration steps: 1. Configure Systemtap probes, and verify them with stap(1). These should be produced in a format that is easily parsed, and then stored in the $PCP_PMDAS_DIR/systemtap/probes.stp file. 2. Configure pmdasystemtap to extract the values from the text produced by stap. Two example probes are implemented in the default systemtap PMDA script - readdir and sync traces (see $PCP_PMDAS_DIR/systemtap/pmdasystemtap.pl for details). # cd $PCP_PMDAS_DIR/systemtap # [ edit probes.stp, test /usr/bin/stap probes.stp ] # [ edit pmdasystemtap.pl ] Once this is setup, you can access the names and values for the systemtap performance metrics by doing the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Install If you want to undo the installation, do the following as root: # cd $PCP_PMDAS_DIR/systemtap # ./Remove pmdasystemtap is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is installed or removed. FILES
$PCP_PMDAS_DIR/systemtap/probes.stp probe configuration file for stap(1), run by pmdasystemtap $PCP_PMDAS_DIR/systemtap/Install installation script for the pmdasystemtap agent $PCP_PMDAS_DIR/systemtap/Remove undo installation script for the pmdasystemtap agent $PCP_LOG_DIR/pmcd/systemtap.log default log file for error messages from pmdasystemtap SEE ALSO
pmcd(1) and stap(1). 3.8.10 Performance Co-Pilot PMDASYSTEMTAP(1)
Man Page