Control-M for SAP log error

Everything about Control-M Control Modules
Post Reply
User avatar
wer230518
Nouveau
Nouveau
Posts: 11
Joined: 19 Apr 2013 12:00

Control-M for SAP log error

Post by wer230518 » 16 May 2013 1:26

Hi All

I hope you can help

CM(SAP) ver 7.0.00.105
Control-M/Agent ver 7.0.00.300
Control-M/Server ver 7.0.00.300
Control-M EM ver 7.0.00.400

I get an error in the cmsap_date.log log. Added error at the bottom of the topic.

I have 1 Node Group with 2 Agents, both Agents have the SAP Module installed

I thought it might be something to do with the Agent and SAP Module

What I have tried to do is:
1. Remove one agent from the Node Group
2. When all jobs running on the removed agent completed I stopped the SAP Module and restart it with the sapcmbe.cmd command
3. Add the agent back in the node group
4. Done steps 1 to 3 with both agents

What I found was that whichever agent is running the log gets created in that agents PROCLOG directory, but not in both when both Agents are running. So always just one log.


Whats strange is is that all jobs are running successfully on both agents and I can test the SAP Module's account successfully. No jobs failing, but this error gets created in the log 2 to 3 times a minute.

Sometimes it is just the bold part in the log
16 09:34:02:923 E 18 TreeMonitor.getTargetServer[412] Could not calculate Target server for account 'ACCOUNT NAME', target server is set to empty: java.lang.NullPointerException
at com.bmc.ctm.cmsap.domain.command.cm_actuators.load_balancing.tree_monitor.TreeMonitor.buildServerAndResourceList(TreeMonitor.java:287)
at com.bmc.ctm.cmsap.domain.command.cm_actuators.load_balancing.tree_monitor.TreeMonitor.getTargetServer(TreeMonitor.java:379)
at com.bmc.ctm.cmsap.domain.command.cm_actuators.load_balancing.tree_monitor.TreeMonitorService.getTargetServer(TreeMonitorService.java:62)
at com.bmc.ctm.cmsap.domain.command.cm_actuators.GetTargetServerCommand.call(GetTargetServerCommand.java:24)
at com.bmc.ctm.cmsap.domain.command.cm_actuators.GetTargetServerCommand.call(GetTargetServerCommand.java:15)
at com.bmc.ctm.cmsap.domain.command.CommandManagerImpl.execute(CommandManagerImpl.java:133)
at com.bmc.ctm.cmsap.invoker.InvokerImpl.invoke(InvokerImpl.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy23.invoke(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:180)
at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:109)
at org.springframework.remoting.caucho.Hessian2SkeletonInvoker.invoke(Hessian2SkeletonInvoker.java:93)
at org.springframework.remoting.caucho.HessianExporter.invoke(HessianExporter.java:142)
at org.springframework.remoting.caucho.HessianServiceExporter.handleRequest(HessianServiceExporter.java:70)
at org.springframework.web.context.support.HttpRequestHandlerServlet.service(HttpRequestHandlerServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:843)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

User avatar
Manii
Nouveau
Nouveau
Posts: 46
Joined: 28 Jul 2011 12:00

Post by Manii » 16 May 2013 5:34

This error indicate that load balancing is set to XAL in BMC control-M for SAP configuration

---
You need to change the load balancing algorithm from XAL to SAP default

using CCM

Go CCM right click on CM (SAP) for the problematic agent/host and select configuration management to change the load balancing setting

Hope this will help

Cheers ,
Chandramani
:)

User avatar
wer230518
Nouveau
Nouveau
Posts: 11
Joined: 19 Apr 2013 12:00

Post by wer230518 » 17 May 2013 8:37

Thanks for the reply.

I checked and the SAP Modules are definately set to XAL, as you suggested.

Now another question whick I am not sure of.
I made the change on our DEV environment and now the agent needs to be restarted.

What is the correct procedure for agent restarts?

1. I stopped the Control-M/Agent Windows service.

2. In CCM the agent still shows available.

3. ag_diag_comm output:
System ping to Server Platform : Succeeded
Agent ping to Control-M/Server : Succeeded

Agent processes status:
======================
Agent Router : Not Running
Agent Listener : Not Running
Agent Tracker : Not Running
Agent FileWatcher : Not Running
4. ctms_diag_comm output:
MS-Windows ping to Agent or Remote host : Succeeded
CTMS ping to Agent or Remote host : Failed
Agent IP Address : IP

CTMS Ping jdgcntrlmdev00 as Regular Agent
=========================================
Agent [NAME] responded with "Agent not available."
Can I now start the service and this completes the agent restart?

Is there any other Windows services that must be stopped with the Agent service?

What is recycle for? Is it like restart?

Thanks for the help :D

User avatar
Manii
Nouveau
Nouveau
Posts: 46
Joined: 28 Jul 2011 12:00

Post by Manii » 17 May 2013 2:38

yes

for windows agent you need to stop and start the services from service panel in windows

Sometime on CCM it takes time to reflect the status of agent status

however it does not affect anything , as its showing in your output of commands

ag_diag_comm and ctm_diag_comm

---

Recycling agent form CCM is the same stopping and starting services , however i prefer to do it from agent

Hope its resolved ur issue

Regards,
Chandramani

:)

User avatar
wer230518
Nouveau
Nouveau
Posts: 11
Joined: 19 Apr 2013 12:00

Post by wer230518 » 14 Jun 2013 2:57

Sorry for taking so long to reply

We only now upgraded to all the latest fix packs and I made the change from XAL to SAP ONLY.

The error stopped and I could delete the log file


Thank for your help :D :D

Post Reply