on 09-03-2011 4:48 PM
Hi Experts,
Please need your expertise in solving SMD AGENT Diagnosctics Configuration for managed systems.
Solution Manager 7.01 SP27 with LM SERVICE 7.01 SP10 - all components are with correct patch levels as per Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP27
Installed SMD Agent 7.20 on our managed systems (PI 7.11 and few others) - some of the managed systems this Diagnostics Configuration worked properly.
But for PI 7.11 system - SMD agent Diagnostics Configuration is failing in WilyHost Agent step with following error message.
Connection to SMDAgent tx3s003a could not be established! Reason: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.
Connection to SMDAgent tx3s003a could not be established! Reason: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.
Exceptions
com.sap.smd.ServiceNotAvailableException: Smd agent Service 'Implementation as null of object entities:com.sap.smd.agent.application.wilyhost.WilyHostService is not available' not available.
at com.sap.smd.core.runtime.Runtime.getService(Runtime.java:167)
at com.sap.smd.agent.AgentContext.getService(AgentContext.java:555)
at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:183)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
-
Looked at SMDAgentApplication.0.log -->
Sep 3, 2011 3:27:46 PM [Thread[Thread-6,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - commandExists: file /usr/sap/SMD/SMDA97/exe/saposcol does
not exist, destination Process_Saposcol not available
Sep 3, 2011 3:27:46 PM [Thread[Thread-6,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - open(): file saposcol does not exist, destination not avai
lable
Sep 3, 2011 3:27:51 PM [Thread[Thread-6,5,main]] Fatal com.sap.smd.wily.hostagent.WilyHostService - startAgent(): WilyHostAgent start failed!
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP
-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:455)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:96)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:233)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:504)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:381)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)
at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:255)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:168)
at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:97)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: metho
d name or namespace not recognized
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:155)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
... 21 more
Caused by: javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1454)
at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:142)
Errors from SMDSystem.0.log are -->
Sep 3, 2011 3:27:42 PM [Thread[Connector,5,main]] Info [ms://tsgd002a.eu.unilever.com:8102/P4] Registration done.
Sep 3, 2011 3:27:42 PM [Thread[Connector,5,main]] Info [ms://tsgd002a.eu.unilever.com:8102/P4] Agent ready.
Sep 3, 2011 3:27:42 PM [Thread[Thread-6,5,main]] Info SMD Patch Installer: Nothing to do ... already patched at: /usr/sap/SMD/SMDA97/SMDAgent/lib/patch_7.01.10.0.2011060110
2614
Sep 3, 2011 3:27:43 PM [Thread[Thread-6,5,main]] Info [WHS] Initializing Wily Handler Service
Sep 3, 2011 3:27:51 PM [Thread[Thread-6,5,main]] Error service com.sap.smd.agent.application.wilyhost.WilyHostService is going ouf of service: com.sap.smd.plugin.service.Ser
viceException: WilyHostAgent start failed; nested exception is:
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Metho
d SOAP-ENV:Envelope not implemented: method name or namespace not recognized
[EXCEPTION]
com.sap.smd.plugin.service.ServiceException: WilyHostAgent start failed; nested exception is:
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Metho
d 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:71)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:233)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:504)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:381)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)
at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:255)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:168)
at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:97)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Caused by: java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Metho
d 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
... 17 more
Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Me
thod 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:455)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:96)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
... 18 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Generic Exception: -> javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: metho
d name or namespace not recognized
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:155)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
Appreciate your help here
BR
Davinder
Edited by: Davinderpal Singh on Sep 3, 2011 5:48 PM
Hi,
The error message is : WilyHostService is not available' not available
Is the Wily Enterprise Manager installed and is the server running on the default port 6001 or any other corresponding port?
Regards,
Srikishan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your quick response.
Wily Enterprise Manager is installed and running on 6001. Other Managed systems in our landscape are connected to this Wily Enterprise Manager. Even for this managed system - hostagent entry is visible and reporting data in Wily as visible in WIly Workstation.
Please give more inputs on resolve this issue.
Hello Davinder,
The problem is with the SAP Host Agent. When it is not available it might lead to the Wily Host Agent to crash.
-
The SAPHOSTAGENT is located at /usr/sap/hostctrl/exe on unix
On Windows it is usually installed to "C:\Progam Files\SAP\hostctrl\exe"
It will require the root user to execute any of the SAPHOSTAGENT commands. On Windows it is usually installed as a service meaning it can be started or stopped via Windows Services
Check its status
saphostexec -status
If your SAP Host Agent is not running please check if the job is staring correctly.
If SAP Host Agent is not installed, please install it according to note 1031096.
If everything is OK, you might be missing the webservice entry in the configuration. Check note 1400891.
-
Best regards,
Guilherme Balbinot
Hello,
Thanks very much - after following SAP Note 1400891 - WilyHost Agent service is coming up properly.
But still there are some error messages related to SAPOSCOL
Sep 4, 2011 6:09:36 PM [Thread[Thread-5,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - commandExists: file /usr/sap/SMD/SMDA97/exe/saposcol does
not exist, destination Process_Saposcol not available
Sep 4, 2011 6:09:36 PM [Thread[Thread-5,5,main]] Warning com.sap.smd.wily.hostagent.destination.ProcessDestination - open(): file saposcol does not exist, destination not avai
lable
I tried copying the saposcol from /usr/sap/hostctrl/exe to /usr/sap/SMD/SMDA97/exe/saposcol - but still the error is being reported.....
Please help to get rig of these messages..
Best Regards
Davinder
Dello Davinder,
There are several actions executed by the agent. These actions are called by the software INSIDE the SMD Agent, which is deployed from the Solution Manager to the Diagnostics Agent. Hence the agent is a mere "agent"/"slave" on the whole scenario. It's a man in the middle.
The agents 7.01 have a kernel that uses SAPOSCOL to get the host data (such as memory, cpu, etc).
The agents with 7.11 (+ all newer releases) a kernel that can use SAP Host Agent or the SAPOSCOL directly.
Starting with LM-SERVICE SP05 the software deployed to the SMD Agents started to take advantage of this resource and therefore this SAP Host Agent action is used in a first place..
Having this said, one can conclude that the actions must be backwards compatible BY DESIGN for COMPATIBILITY PURPOSES:
it must call the SAPOSCOL action and the SAPhostagent action all together.
All agents look for SAP Host agent and SAPOSCOL, regardless of the release (7.01, 7.11, 7.2), and you will find these kind of "warnings" in all of them. As stated above, the actions are executed in all agents the same way until one action is found.
You can ignore these errors if you have the SAP Host Agent action running*
You can find the SAPHostWS entry in the logs and look if the SAP Host Agent Webservice is being called properly.
Best regards,
Guilherme Balbinot
Edited by: Guilherme Balbinot on Sep 5, 2011 2:40 PM
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.