Problem at the step of Interscope Host Adaptor while configuring Managed System in solman_setup

[Former Member]

Hi All,

We are facing problem at the step of Interscope Host Adaptor while configuring Managed System in solman_setup.

We are at the following versions

Solution Manager - 7.1 SP08

Wily Introscope - 9.1.5

We have configured Wily Introscope - Basic Configuration (pic 1)

When we try to configure managed system - at step 7 - Configure Automaticlly - step of Interscope Host Adaptor. (pic 2)

It gives us error saying all EMs are offline. (pic 3)

EM is up running at os level and able to login and see through webview of Introscope.

But when we go back to Wily Introscope - in Basic Configuration - status turns red (pic 4)

Once we reload the configuration of Wily - status turns green in Basic Configuration.

1.We have tried giving full access to the Introscope directories to diagnostic agent user.( Wily was installed by Solman <sid>adm)

2.Tried new installation of Wily Introscope with diagnostic agent user but the error remains the same.

3.Checked https://service.sap.com/sap/support/notes/1771826

4. Made changes as per note 1565954 - http://scn.sap.com/thread/3185523

5 Made entries - http://scn.sap.com/thread/1413337

in table/view : ssm_var

name: WILY_PORT

field:   8081

name: WILY_HOST

field:   solman

6. Tried different ports for Wily Introscope

7. We are using Admin  user as a connect user in Wily Itroscope.

Any suggestions are highly appreciated.

Regards,

Sam.

[divyanshu_srivastava3 · Accepted solution]

Hi Sam,

Did you check all logs. What does they say before reloading the configuration.

Regards,

Divyanshu

[Former Member · Accepted solution]

Hi Divyanshu,

We have checked IntroscopeEnterpriseManager.log

It has one error -

"8/05/13 08:36:02.429 AM AST [ERROR] [main] [Manager.Acceptor] Failed to bind to server socket"

Log in the step configure

CA Wily Introscope Enterprise Managers

Offline - The EM Connection cannot be established (caused by :java.sql.SQLException: Failed to establish connection to Isengard Server. Caught Exception java.io.EOFException_)

We have checked -- Wily is accessable from webview. http://FQDN:8081/webview

Diagnostic agent is running when we check from http://<hostname>:59613

No other error we could find.

Regards,

Sam

[divyanshu_srivastava3 · Accepted solution]

Hi,

Did you check these notes:

1773617 - SAP Remote Support Component log files report exception "Failed to establish connection to Isengard Server"

1845926 - CA Wily Introscope Enterprise Manager does not start "Failed to bind to server socket"

Regards,

Divyanshu

[Former Member · Accepted solution]

Hi Divyanshu,

We have checked

1.Note 1773617 - SAP Remote Support Component log files report exception "Failed to establish connection to Isengard Server

As mentioned in the notes we are not able to access . It gives page cannot be displayed.

http://managinghost:59813/rsc.jnlp

we have tried managing host with the solution manager host. we hope 98 is the port of the diagnostic agent. we have tried with 98 and 96 ( no for diagnostic agent SMDA96).

Is there any configuration need to be done for accessing rsc.jnlp?

2.Note 1845926 - CA Wily Introscope Enterprise Manager does not start "Failed to bind to server socket"

6001 and 8081 ports are used only by Wily Introscope. Even then we have tried changing the port nos to 6005 and 8085. Even then the same error.

Regards,

Sam

[jon_friesen2 · Accepted solution]

Hi Sam,

That's an interesting error message.  Is it possible you have another application listening on port 6001?  To test this, try shutting down wily and then see if anything else is still listening on port 6001.  You can do this by running "netstat -a" (works on both Unix and Windows) and see if there is a line that looks like:

tcp        0      0  *.6001                 *.*                    LISTEN

The important parts are "*.6001" and "LISTEN".  An example of another program that listens on port 6001 is VNC, commonly found in Unix systems as a cheap alternative to using Exceed.

[divyanshu_srivastava3 · Accepted solution]

Hi Sam,

If everything is fine the you should clear the cache and re-cache the info. Stop SMD agent on your Wily host and clean the SHM.

Also, Check the below page to make changes to disable and enable user specific cache.

Regards,

Divyanshu

[Former Member]

Hi Sam

I am facing the same issue, for collectors.Out of 3 collectors only 1 collector is currently active and other 2 were having same

"[ERROR] [main] [Manager.Acceptor] Failed to bind to server socket" error

What steps did u take to fix this

Regards

Arun

[former_member185048]

Hi Sam,

As mentioned, It seems that another service running on your host with the default port(6001),

Change the Wily EM server port in IntroscopeEnterpriseManager.properties (EMHome/config) file and the parameter

introscope.enterprisemanager.port.channel1=6001

to any other port as (Ex:6051).

Thanks,

Karthik.

[bxiv]

Tx solman_setup_admin > Generic Storare Admin UI > EM_CONFIG_ID-EM_CONFIG_ID drop down > the first EM_CONFIG_ID line item

In the configuration details, is the information there correct for your Wily installation?

Also did you manually create a \\hostname\sapmnt\CCMS\wily folder?

[Former Member]

Hi Billy,

Thanks for the update!

1. Also did you manually create a \\hostname\sapmnt\CCMS\wily folder?

We did not create wily folder manually. It was created during installation. Installation was done by solman <sid>adm, after installation wily folder (/usr/sap/ccms/apmintroscope) was granted access to diagnostic agent<sid>adm.

2.Tx solman_setup_admin > Generic Storare Admin UI > EM_CONFIG_ID-EM_CONFIG_ID drop down > the first EM_CONFIG_ID line item

In the configuration details, is the information there correct for your Wily installation?

Agent Id, Hostname, port no, Connection user are all OK.

Regards,

Sam

[bxiv]

Your LSID is WLY00001?  Do you also have a WLY in your LMDB?

This may not be the exact problem, but I can confirm that mine is just WLY.  It is possible to edit the entry on that screen, but I would verify which one is being used first.

[Former Member]

Hi Billy,

There is only one entry WLY00001 in LMDB for standalone Wily.

We have updated to WLY and restarted Wily introscope also.

We are still getting the error.

Regards,

Sam

[former_member185048]

hi Sam,

As the error says "Failed to bind to server socket  java.net.BindException: Address already in use" There is some other service running on the port 6001. Change the Wily EM server port in IntroscopeEnterpriseManager.properties (EMHome/config) file and the parameter

introscope.enterprisemanager.port.channel1=6001

to any other port as (Ex:6051).

Restart the EM. It should work.

Thanks,

Karthikeyan.

[former_member93896]

Thanks, Karthikeyan.

I had the same "Failed to bind to server socket" issue and changing the port to 6051 fixed the issue.

In case SolMan is already configured for another port, you have to go to SolMan Basic Configuration > Step 3.2 "Configure CA Wily Introscope" and reload the configuration (the new port should show up). You might have to reconfigure other managed systems if they were already assigned to agent.

Regards,
Marc

SAP Customer Solution Adoption (CSA)

[Former Member]

Hi Sam,

Have you installed SAP Management Modules after Wily Enterprise Manager installation ?

Also have you updated SAP Host agent to latest available ?

Please paste detailed logs here for Wily EM and Managed system errors.

Regards,

Nisha

[Former Member]

Hi Nisha,

We have installed SAP Management modules immediately after Wily installation.

SAP Host agent is on the latest version 159.

IntroscopeEnterpriseManager.log

INFO: Application context successfully refreshed (OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.isengard, config=osgibundle:/META-INF/spring/*.xml))

8/06/13 06:36:39.162 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: CA Styles r 2.1

8/06/13 06:36:39.259 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: CA Styles R5.1.2

8/06/13 06:36:39.511 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: Wily APM Axis and Muse Web services

8/06/13 06:36:39.732 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: CEM URL Adapter

8/06/13 06:36:39.867 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: Workstation WebStart

8/06/13 06:36:39.903 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: Isengard HTTP Tunneling Server

8/06/13 06:36:40.027 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: Introscope Online Documentation

8/06/13 06:36:40.434 PM AST [INFO] [main] [Manager.EMWebServer] Deployed web application: Introscope WebView

8/06/13 06:36:50.742 PM AST [INFO] [main] [Manager.ManagementModule] Loading Management Module "Triage Map Configurations"

8/06/13 06:36:50.762 PM AST [INFO] [main] [Manager.ManagementModule] Loading Management Module "SOA Performance Management"

8/06/13 06:36:50.821 PM AST [INFO] [main] [Manager.ManagementModule] Loading Management Module "ChangeDetector"

8/06/13 06:36:50.947 PM AST [INFO] [main] [Manager.Bootstrap] Load all Management Modules complete.

8/06/13 06:36:51.001 PM AST [INFO] [main] [Manager.HighConcurrencyTransportServer] Starting High Concurrency Transport Server

8/06/13 06:36:51.024 PM AST [INFO] [main] [Manager.Dispatcher] Started Dispatcher 1

8/06/13 06:36:51.038 PM AST [ERROR] [main] [Manager.Acceptor] Failed to bind to server socket

java.net.BindException: Address already in use

        at sun.nio.ch.Net.bind(Native Method)

        at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)

        at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)

        at com.wily.isengard.postofficehub.link.server.Acceptor.<init>(Acceptor.java:72)

        at com.wily.isengard.postofficehub.link.server.ConnectionListenerFactory.create(ConnectionListenerFactory.java:31)

        at com.wily.isengard.postoffice.server.PostOfficeHubServer.startIncomingConnectionListener(PostOfficeHubServer.java:261)

        at com.wily.isengard.postoffice.server.PostOfficeHubServer.startAllIncomingConnectionListeners(PostOfficeHubServer.java:235)

        at com.wily.isengard.postoffice.server.PostOfficeHubServer.acceptIncomingHubConnections(PostOfficeHubServer.java:103)

        at com.wily.isengard.api.server.IsengardControllerServer.acceptIncomingConnections(IsengardControllerServer.java:207)

        at com.wily.isengard.api.samplemain.SampleMain.acceptIncomingConnections(SampleMain.java:117)

        at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:703)

        at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:360)

        at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)

        at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)

        at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:282)

        at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1491)

        at com.wily.introscope.em.internal.Activator.startEM(Activator.java:116)

        at com.wily.introscope.em.internal.Application.start(Application.java:27)

        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

        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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)

        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)

        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

        at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

        at org.eclipse.core.launcher.Main.main(Main.java:30)

        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.zerog.lax.LAX.launch(DashoA10*..)

        at com.zerog.lax.LAX.main(DashoA10*..)

8/06/13 06:36:51.042 PM AST [INFO] [main] [Manager.PostOfficeHub] Server listening for incoming default socket connections on port 6001

8/06/13 06:36:51.045 PM AST [INFO] [main] [Manager] Connection Initiator listening...

8/06/13 06:36:51.047 PM AST [INFO] [main] [Manager.MMHotDeployEntity] Will monitor /usr/sap/ccms/apmintroscope/deploy for new files every 60 seconds

8/06/13 06:36:51.048 PM AST [INFO] [main] [Manager] Introscope Enterprise Manager started.

log4j:WARN No appenders could be found for logger (com.wily.apm.em.monitor.support.util.TimingThreadPool).

log4j:WARN No appenders could be found for logger (com.wily.apm.em.monitor.support.util.TimingThreadPool).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN No appenders could be found for logger (com.wily.apm.em.monitor.support.util.TimingThreadPool).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN Please initialize the log4j system properly.

Regards,

Sam

[former_member185048]

Hi Sam,

If you have uninstalled any Wily EM servers, and if you try to reload the configuration the unistalled EM configuration details will also appear in the list. Please remove that entry in the list and save it. Let me know if this works.

Thanks,

Karthikeyan.

[Former Member]

Hi Karthikeyan,

We have done the same.

Uninstalled Wily and Diagnostic Agent.

removed the entries.

Installed them and configured.

But still the error appears mentioning "Failed to establish connection to Isengard Server"

Regards,

Sam