SMD Agent Information REquired

[Former Member]

Hi,

We upgraded our portal from 6,40 to 7.0 EHP1 Stack 6. During this upgrade the SMD agent on the central instance of portal did not get upgraded. It's version is still 7.0 patch 105. After which we installed app server which brought a different SMD agent version 7.01 patch 11.

Issues;

From Solution Manager (which is of 7.0 stack 22 (EHP1)) , solman_workcenter->Agent Administration it was showing central Instance agent as running but it is not showing as running from diagnostics setup screen,

Whereas the one from app server was not showing as running even in agent administration even though it was running at OS level

Did smdsetup.sh with managedconfig parameter in the app server and the agent did get connected with solution manager now and also it was showing in agent administration as well as from diagnostics setup screen.

Did the same smdsetup from Central instance also to see whether it will show in diagnostics setup as running but still it is showing as not running.

Question; Is there anything in particular to be done in Central Instance ?

Does the version 7.0 of agent is ok or do we need to get it like app server which has got 7.01, if so where to get that, i could not find one with the same in SMP.

Also some guides say if solman is of stack 22, then we need to have diagnostics agent 7.11 in all managed system,-- is this same as SMD agent or something different ? Because in SMP download section there is one says diagnostics agent and also there is a link for SMD agent....

Thanks,

Murali.

[raguraman_c · Accepted solution]

Hi,

Please post SMDAgent.log here.

This should help us in finding the actual error.

Feel free to revert back.

-=-Ragu

[Former Member · Accepted solution]

Hi Raghu,

Thanks for the reply. The following are the extract from SMDAgent.log of central instance where the agent is running as per OS check and also agent administration from solman_workcenter but not running as per diagnostics setup:

Jul 11, 2010 3:10:52 AM [Thread[Thread-660,5,main]] Error com.sap.smd.wily.

hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed

[EXCEPTION]

com.sap.smd.wily.hostagent.PermanentException: Error: cannot connect to destina

tion SapHostControl_Default. Probably saphostctrl is not installed. This error c

an be ignored if saposcol is available.

at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.o

pen(SapHostControlDestination.java:98)

at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(A

gentConfigVO.java:85)

at com.sap.smd.wily.hostagent.config.AgentConfigXmlHandler.endElement(Ag

entConfigXmlHandler.java:135)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDo

cHandler.java(Compiled Code))

at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java(Com

piled Code))

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Co

mpiled Code))

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Co

mpiled Code))

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Co

mpiled Code))

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2

845)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchExceptio

n(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLPars

er.java:165)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLPars

er.java:245)

at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:

260)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(Unknown Source)

at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentCon

figParser.java:59)

at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:4

38)

at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:95)

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(Servic

eEntityHandle.java:114)

at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntity

Handle.load(AbstractEntityHandle.java:233)

at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityH

andle.load(PseudoEntityHandle.java:154)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyIm

pl.java:308)

at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectRef

erence.java:305)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyIm

pl.java:272)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:

146)

at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(Applicat

ionManager.java:504)

at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializatio

nStates(ApplicationManager.java:381)

at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)

at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:249

)

at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:16

2)

at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.ja

va:300)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl

.java(Compiled Code))

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java(In

lined Compiled Code))

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java(Com

piled Code))

at java.lang.Thread.run(Thread.java:570)

Caused by: java.rmi.RemoteException: Service call exception; nested exception is

:

java.net.ConnectException: A remote host refused an attempted connect op

eration.

at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(S

APOscolStub.java:143)

at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(S

APOscolStub.java:151)

at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.o

pen(SapHostControlDestination.java:94)

... 38 more

Caused by: java.net.ConnectException: A remote host refused an attempted connect

operation.

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188)

at java.net.Socket.connect(Socket.java:482)

at java.net.Socket.connect(Socket.java:432)

at java.net.Socket.<init>(Socket.java:339)

at java.net.Socket.<init>(Socket.java:150)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsF

romSocket(HTTPSocket.java:682)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeSt

reams(HTTPSocket.java:504)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStr

eam(HTTPSocket.java:461)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTP

Transport.getRequestStream(HTTPTransport.java:408)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.Mime

HttpBinding.outputMessage(MimeHttpBinding.java:557)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.Mime

HttpBinding.call(MimeHttpBinding.java:1444)

at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(S

APOscolStub.java:136)

... 40 more

Jul 11, 2010 3:10:52 AM [Thread[Thread-660,5,main]] Warning com.sap.smd.wily.

hostagent.SapAgent - startActions(): Action SAPOsColWs

[EXCEPTION]

com.sap.smd.wily.hostagent.TransientException: Destination not available:SapHos

tControl_Default

at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlAction.init(S

apHostControlAction.java:74)

at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:404)

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(Servic

eEntityHandle.java:114)

at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntity

Handle.load(AbstractEntityHandle.java:233)

at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityH

andle.load(PseudoEntityHandle.java:154)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyIm

pl.java:308)

at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectRef

erence.java:305)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyIm

pl.java:272)

at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:

146)

at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(Applicat

ionManager.java:504)

at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializatio

nStates(ApplicationManager.java:381)

at com.sap.smd.core.runtime.Runtime.run(Runtime.java:56)

at com.sap.smd.agent.AgentContext.runStarterPlugin(AgentContext.java:249

)

at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:16

2)

at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.ja

va:300)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl

.java(Compiled Code))

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java(In

lined Compiled Code))

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java(Com

piled Code))

at java.lang.Thread.run(Thread.java:570)

Jul 11, 2010 3:10:54 AM [Thread[Thread-660,5,main]] Warning com.sap.smd.wily.

hostagent.action.SapOsColAction - launchDaemon(): saposcol exited with 255******

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

• This is Saposcol Version COLL 20.94 700 - AIX v10.35 5L-64 bit 070123

• Usage: saposcol -l: Start OS Collector

• saposcol -k: Stop OS Collector

• saposcol -d: OS Collector Dialog Mode

• saposcol -s: OS Collector Status

• The OS Collector (PID 1626366) is already running .....

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

Jul 11, 2010 3:10:56 AM [Thread[Thread-660,5,main]] Warning com.sap.smd.eem.a

gelet.ext.ExtManager - init: no executor libs found

Thanks,

Murali.

[guilherme_balbinot · Accepted solution]

Hello all,

It seems that the SAP Host Agent is either not installed or not running.

Please perform this steps:

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

Check its version

saphostexec -version

Please check if the job is staring correctly.

If SAP Host Agent is not installed, please install it according to Diagnostics Setup Guide 7.11.pdf, which defines SAP Host Agent as obligatory. Follow note 1031096: Installing Package SAPHOSTAGENT . There's a PDF included in this note.

Best regards,

Guilherme Balbinot

[raguraman_c · Accepted solution]

Hi,

Check this

this may help you.

Feel free to revert back.

-=-Ragu

[Former Member · Accepted solution]

All,

Issue is with SMSY not configured properly and the app servers were not showing as active. After fixing it by recreating everything went ok.

Thanks