cancel
Showing results for 
Search instead for 
Did you mean: 

CCMS Agent Error!!

Former Member
0 Kudos

Hi Experts,

While stopping the CCMS Agent I am getting the following error :

ew1adm> sapccmsr -j2ee -stop pf=/usr/sap/EW1/SYS/profile/EW1_DVEBMGS02_ew1app

INFO: use SAPLOCALHOST ew1app

INFO: CCMS agent sapccmsr working directory is /usr/sap/ccms/EW1_02/sapccmsr

INFO: CCMS agent sapccmsr config file is /usr/sap/ccms/EW1_02/sapccmsr/csmconf

INFO: sapccmsr is not running. Nothing to do!

EXITING with code 0

  • It should come like this while stopping the agent :

INFO :Setting Stop Flag for sapccmsr.

INFO: Waiting for Background process to stop.

INFO : Background process was stopped

INFO : Agent was stopped. *

I am not all able to stop the agent & start it again.Please guide.

Accepted Solutions (1)

Accepted Solutions (1)

former_member227283
Active Contributor
0 Kudos

Hi,

There is no error in the log which you have pasted it just contain info.

INFO: CCMS agent sapccmsr config file is /usr/sap/ccms/EW1_02/sapccmsr/csmconf
INFO: sapccmsr is not running. Nothing to do!

The agent was not in running state , that why you get the info saying that nothing to DO.

Try to start the agent and share the log if there is any error while starting.

Thanks

Anil

Former Member
0 Kudos

Anil after starting the agent I am getting this :

sapccmsr -j2ee -DCCMS pf=/usr/sap/EW1/SYS/profile/EW1_DVEBMGS02_ew1app

INFO: use SAPLOCALHOST ew1app

INFO: CCMS agent sapccmsr working directory is /usr/sap/ccms/EW1_02/sapccmsr

INFO: CCMS agent sapccmsr config file is /usr/sap/ccms/EW1_02/sapccmsr/csmconf

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

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

INFO: Agent is running (actual pid file is detected)

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

Another CCMS Agent is already running with this profile.

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

EXITING with code 1

Former Member
0 Kudos

I've had this one before... I my case, only a restart of the entire system (host) resolved this issue.

Kind regards,

Mark

Former Member
0 Kudos

You may be right sir..But did you investigate the problem?Why it happened & how restart is resolving the issue??

former_member227283
Active Contributor
0 Kudos

Hi Das,

One more thing to ask.

sapccmsr -j2ee -DCCMS pf=/usr/sap/EW1/SYS/profile/EW1_DVEBMGS02_ew1app

SAPCCMSR --> ABAP stack

SAPCCM4X --> java stack.

What is reason you are using sapccmsr for starting java agaent.

Where as in ccms configuration SAPCCM4X is used for java agent

Thanks

Anil

Former Member
0 Kudos

Someone was registering the agent again, while it was still running.. (or something like that).

Kind regards,

Mark

Answers (3)

Answers (3)

Former Member
0 Kudos

Restarting solved the issue.

Edited by: N. Das on May 26, 2010 7:34 AM

Former Member
0 Kudos

Hey,

Can you please let me know if the issue is resolved. Please update

Regards

Naeem

Former Member
0 Kudos

Hi,

It seems to me a shared memory problem. Check and carryout the work mentioend in below note. I was able to solve similar problem earlier with this note.

Note 883361 - CCMS agent does not start

Summary

Symptom

Windows: The service "sapccmsr" or "sapccm4x" does not start or immediately stops again.

UNIX: When you start the agents sapccmsr or sapccm4x, the system issues the message "Another agent is already running with this profile".

Other terms

sapccmsr, CCMS, RZ20, sapccm4x, initshm

Reason and Prerequisites

CCMS agents manage monitoring data in a shared memory segment. You can identify this segment by an instance number for instance-specific CCMS agents, and by instance number 99 for instance-independent agents.

Only one CCMS agent may run for each instance, so the administration information of the CCMS contains information about whether an agent has been started already for an instance. The system refreshes this information when the agent is started, and deletes it when the agent is stopped.

If, due to an error, the agents could not be stopped and the administration data above could not be deleted in the shared memory, a newly started agent receives the information that another agent is running even though there is no longer a corresponding agent process. The system then issues the message described under "Symptom".

Solution

1. Check whether the agent involved is running. The process number of the agent process is noted in the agent log file "sapccmsr.log" or "sapccm4x.log" under "pid":

CCMS version 20040229, 32 bit, multithreaded, non-Unicode

compiled at Sep 22 2005

systemid 560 (PC with Windows NT)

relno 7100

patch text patch collection 2005/5, OSS note 809007 patchno 0

intno 20053800

running on P129685 Windows NT 5.1 2600 Service Pack 1 2x Intel 801586 (Mod 2 Step 9)

pid 3024

pro-file test.pfl

2. Check whether the agent process still exists.

3. If the process is no longer running, you can initialize the administrative data for the shared memory as follows:

Agent for J2EE and TREX instances:

sapccmsr pf=<instance profile> -j2ee -initshm

instance-independent agent:

sapccmsr -initshm

Agent for ABAP instances:

sapccm4x pf=<instance profile> -initshm

You can then restart the agent or agent service.

The error was eliminated with CCMS Patch Collection 2007/4.

Regards

Naeem