SAP Knowledge Base Article - Preview

3200092 - How to find why SAP was terminated? Introduction to stap

Symptom

SAP application process was terminated without detailed information in SAP logs. Nor did Linux syslog /var/log/messages captured any related info

For example:

  1. in a Netweaver ABAP installation in dev_* files, there is "caught signal 2" but no other errors, no stack either.
  2. in a HANA DB server, index server crashed with similar message to "TrexDaemon.cpp(03780) : process hdbindexserver with pid 43311 exited because it caught signal 9"

In case there isn't any sender information logged in OS syslog (/var/log/messages) nor application itself, and the problem happens frequently, it is necessary to use additional tool to capture the external process info. 


Read more...

Environment

SAP applications on Linux

Product

SAP NetWeaver all versions ; SAP S/4HANA all versions

Keywords

SIGKILL, SIGINT, Signal 9, Signal 2, systemtap , KBA , BC-OP-LNX , Linux , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.