Skip to Content
Author's profile photo Tamas Istenes

instance rebooted

I find an unusual question , that can not be solved on PS level:

Let me say it can be don but do not recommended…
If the PID file of SAPCCM4X Agent is empty ( -> 0 Bytes) and you do a sapccm4x -stop …. command, the agent takes “-1” as PID and kills all shared memory segments of his user, causing the whole sap system to shut down…

Steps to simulate:

1. Install a SLES or AIX machine

2. Install SAP system which is runnable with a 7.20 kernel

3. Install Kernel 720 EXT PL 618

4. Start the SAP system

5. Stop the CCM4X Agent

6. Execute command:  touch /usr/sap//DVEBMGS00/log/sapccm4x/ as sidadm-user

7. Stop the CCM4X Agent again (yes, its not running, but do it)

8. System is down.

„NOT_ACTIVE (10), monitoring segment type NOT_RUNNING (-1). Info read from up-to-date pid file. INFO: Created monitoring segment type APPLSERVER (1), running in process local memory.”

“If the agent reports NOT_ACTIVE (10) and NOT_RUNNING (-1), then it is Ok, because the agent reports state of another possibly attached CCMS agent. “

About pid file:

It is used to stop with option –stop in dialog an CCMS agent sapccm4x  that is running as a daemon on Unix while its abap instance is down. It means that there is not existing a CCMS monitoring segment in shared memory to communicate via flags in SHM to stop the daemon process.

If the customer deleted the pid file and he cannot stop the agent running on background, he should list the process and call ‘kill [pid]’

On Windows the agent usually run as services not stoppable by using task kill command.

We have the solution.The correction in Note:
2031328 – Stopping CCMS agent can kill all processes of the user  

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.