SAP Knowledge Base Article - Preview

2763589 - Saposcol is not running - Got SIGSEGV

Symptom

Saposcol is not running.

In the saposcol trace dev_coll the following error can be seen:


 13:46:58 01.03.2019 LOG: Shared Memory Size: 712244.
 13:46:58 01.03.2019 LOG: Connected to existing shared memory.
 13:46:58 01.03.2019 LOG: Reused shared memory. Clearing contents.
 13:46:58 01.03.2019 LOG: ==== Collector submitted. This is the child process after fork()=====
 13:46:58 01.03.2019 LOG: Connected stderr to log_file
 13:46:58 01.03.2019 LOG: Collector daemon started
------------------------------------------------------------
 | Got SIGSEGV ... |
 ------------------------------------------------------------
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

  • Operating System Monitor Tool
  • SAP NetWeaver
  • SAP NetWeaver Application Server for SAP S/4HANA
  • ABAP PLATFORM - Application Server ABAP

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

Saposcol, ST06, SAPHOSTAGENT, shared memory, ST06N, OS07, OS07N, SMOS, RSHOST1N, Monitoring Operating System, RZ20, Display Statistics, OSMT_GDPR, , KBA , BC-CCM-MON-OS , Operating System Monitoring Tool , 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.