IntroscopeSapAgent.profile could not be read

[Former Member]

Good afternoon,

I've been able to get my servers to show up in the console.  We found that there were some firewall settings that were blocking communication between the montoring server and bobj servers. 

Today I did a landscape check and I am getting SMDAgent not reachable on my stand alone tomcat servers.  I checked the logs and found this on all tomcat servers.  I looked in that directory and it is completely blank.  Also, I've started/restarted all of the smd agents on these servers.  From what I can see they're starting ok.

#1.5 #00505699003000010000003200000D1C0004D5C416B18098#1360938077879#SMDloggerAgentApp##SMDloggerAgentApp#######Thread[Connector,5,main]##0#0#Warning##Java###com.sap.smd.wily.hostagent.SapAgent - isConfigured(): IntroscopeSapAgent.profile could not be read!

[EXCEPTION]

{0}#1#java.io.FileNotFoundException: D:\\usr\\sap\\DAA\\SMDA98\\SMDAgent\\applications.config\\com.sap.smd.agent.application.wilyhost\\IntroscopeSapAgent.profile (The system cannot find the file specified)

    at java.io.FileInputStream.open(Native Method)

    at java.io.FileInputStream.<init>(FileInputStream.java:106)

    at com.sap.smd.wily.hostagent.SapAgent.isConfigured(SapAgent.java:68)

    at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:116)

    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:234)

    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:468)

    at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)

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

    at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:116)

    at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:159)

    at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:709)

    at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:500)

    at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:359)

    at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:316)

    at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:2162)

    at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:2086)

    at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.internalAttemptConnection(SMDConnector.java:566)

    at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.attemptConnection(SMDConnector.java:95)

    at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:1039)

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

[Toby_Johnston]

Hey Rob,

If you go into RSC configuration, then run the config wizard, under monitoring infrastructure do you see SMD Agent nodes defined for each of the Tomcat hosts?  If not, add those Tomcat hosts (with port 59804 or whatever port you SMD Agent listens on) and it will create the IntroscopeSapAgent.profile on each of those Tomcat nodes.

Thanks

Toby

[Former Member]

Yes the Tomcat hosts are listed.  I've removed and added them as well. 

[Toby_Johnston]

1.  Can you telnet from the managing host to each tomcat host on the SMD Agent listen port 5<##>04.  If the agents are using instance number 98 then it would be port 59804

2.  Run a netstat on each managed tomcat node

netstat -ano | findstr "59804"

3.  Zip and attach the logs (/usr/sap/DAA/SMDA98/SMDAgent/log) from the managing host and also from one of the managed hosts

Thanks

Toby

[Former Member]

I can telnet to will no problem.  I ran netstat on one of the tomcat servers and returned the following

>netstat -ano | findstr "59804"

  TCP    0.0.0.0:59804          0.0.0.0:0              LISTENING       2196

  TCP    [::]:59804             [::]:0                 LISTENING       2196

[Former Member]

In zip format

Managing Host.txt.zip

Managed host.txt.zip

[Toby_Johnston]

Hi Rob,

Could you please try the following solution?

1585018 - How to reset a failed lock on a managed host to resolve
communication issues

I think the IntroscopeSapAgent.profile not found error is a bi-product of the underlying communication problem. (since RSC is currently trying to connect in order to send this configuration to the managed host)

Let me know how it goes.

Thanks

Toby

[Former Member]

That was one of the first things I did.  I redid it a few moments ago and I get the same result.  I worked with our network folks and we're not finding anything that could be blocking this.  We can telnet and ping back and forth without any problems.

[Toby_Johnston]

Hey Rob,

Ok thanks for confirming.  If you could create a message and email me I'll schedule a meeting for us to look at this over Netviewer.

Regards

Toby

[Former Member]

Thanks Toby.  Just sent you an email with the ticket number.

[Toby_Johnston]

We discovered the problem was Network Address Translation between managing host and Tomcat server (where SMD Agent was running). 

Instead we installed SMD Agent 7.3 SP3 in stand-alone mode and configured it to report metrics directly to Introscope Enterprise Manager instead of registering with RSC managed agent.

Thanks

Toby