Cannot stop and start CCMS agent

[Former Member]

Hi experts,

I'm new to SAP and here we have problem on sapccmsr agent not running. Previously the sapccmsr was running fine until one day it is not. When i tried to start the application, it says that theres another CCMS agent running with the profile:

bcuser> code/libs/sapccmsr -DCCMS pf=saploc/oscol.pfl

INFO: CCMS agent sapccmsr working directory is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr

INFO: CCMS agent sapccmsr config file is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr/csmconf

INFO: Central Monitoring System is [M04]. (found in config file)

INFO: Checking shared memory status of sapccmsr

**********************************************************

Another CCMS Agent is already running with this profile.

**********************************************************

EXITING with code 0

bcuser> ps -ef | grep sapccmsr | grep -v grep

bcuser>

And when i tried to stop the sapccmsr manually, it failed:

bcuser> code/libs/sapccmsr -stop pf=saploc/oscol.pfl

INFO: CCMS agent sapccmsr working directory is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr

INFO: CCMS agent sapccmsr config file is /sbdc/sapbc47/Server/packages/SAPMonitoring/saploc/PRFCLOG/sapccmsr/csmconf

INFO: Setting Stop Flag for sapccmsr

INFO: Waiting for background process to stop...

INFO: Background process has not stopped after 10 seconds.

INFO: Process might be busy..

INFO: Please try again.

EXITING with code -1

bcuser>

Yeah i think it is because there is no sapccmsr processes running!

My question is; how to force the sapccmsr to start? I already delete the sapccmsr.pid but no success.

The last resort would be to restart the box but unfortunately, thats not the feasible option... for the time being...

Please help....

Thanks in advance

[Former Member]

Hello

This is a shared memory issue you may have to clear the shared memory which will be occpying that.

ipcs -a |grep sidadm command should show you the processes which have occupied the processes you may need to identify the exact process ID corelating to ccms agent and kill that.

Then you start the process that should fix the issue.

Regards

Vivek

[Former Member]

Hello Ahmad,

I hope this link below helps you solve your problem :-

http://help.sap.com/saphelp_nw04s/helpdata/en/b1/7d27d2b2b5f9488d4e72ad3b6aa93d/frameset.htm

Must be SAPCCMSR.00 service is not running. start the service manually.

Also SAPCCMSR.INI is a configuration file that is stored in the working directory of the CCMS agent.

Please do let me know in case of some more concerns.

Thank you.

Regards,

Manomeet

[Former Member]

Also,

try deregistering the agent and the register afresh

[Former Member]

I recently had the same problem with sapccm4x when I was updating the CCMS agent's patchlevel, with these error messages:

INFO: Agent is running (no actual pid, but actual shared memory!)

Another CCMS Agent is already running with this profile.

The answer was to clear the shared memory:

sapccm4x -initshm pf=<instance profile>

This is documented in sapnote 883361 ; as seen in another thread .

[Former Member]

You can also try to start it with the -nosema option.

sapccm4x -DCCMS -nosema pf=<instance_profile>

Edited by: J. Hellemons on Jan 15, 2010 2:32 PM

[Former Member]

try to execute execute ./sapccmsr pf=/usr/sapSID/SYS/profile/PROFILE -j2ee -initshm

filter on

INFO: Attached to Shared Memory Key 73 (size 60000000), no pool used

so you see the size of the shared memory is 60000000

then execute on solaris

ipcs -ma |grep 60000000

this will result in keys with size 60000000

m 108039 0x4761 rw-r--- eppadm sapsys eppadm sapsys 1 60000000 4955 20441 11:40:28 11:40:28 8:30:38

m 5744 0x3d9d rw-r--- yppadm sapsys yppadm sapsys 1 60000000 29224 29224 15:22:23 15:22:24 15:22:23

m 30323 0x3f91 rw-r--- yppadm sapsys yppadm sapsys 1 60000000 29480 29480 15:22:33 15:22:35 15:22:33

m 150522485 0x46fd rw-r--- eppadm sapsys eppadm sapsys 4 60000000 21181 5909 12:05:31 12:05:31 17:03:39

in this case there are 4 with size 60000000 our instance EPP both ccms agents had a problem so we cleaned those 2 entries

ipcrm -m 108039 -m 150522485

afterwards the agents were able to start