SAP Knowledge Base Article - Preview

2763589 - Saposcol is not running - Got SIGSEGV

Symptom

Saposcol is not running.

In the saposcol trace dev_coll you can see the following error:


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 ... |
------------------------------------------------------------

Read more...

Environment

SAP NetWeaver release independent.

Product

SAP NetWeaver all versions

Keywords

Saposcol, ST06, SAPHOSTAGENT, shared memory , 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 ONE Support launchpad (Login required).

Search for additional results

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