DX Application Performance Management

Expand all | Collapse all

EnterpriseManager is not starting 10.5.1.8

Jump to Best Answer
  • 1.  EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 11:27 AM

    Tried to follow the steps on The Introscope EM fails to start - org.rocksdb.RocksDBException: Corruption: checksum mismatch 

    But, it didn't work.

     

    Nearly same issue on Wily collector was resolved.

     

    10/20/17 02:57:19.078 PM UTC [ERROR] [main] [Manager] The EM failed to start. Invalid value for 'isengard.server.port.channel1' property:
    10/20/17 02:57:19.079 PM UTC [VERBOSE] [main] [Manager]

    com.wily.isengard.IsengardException: Invalid value for 'isengard.server.port.channel1' property:
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketPort(ServerPropertiesParser.java:416)
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketProperties(ServerPropertiesParser.java:286)
    at com.wily.isengard.api.server.ServerPropertiesParser.<init>(ServerPropertiesParser.java:164)
    at com.wily.isengard.api.samplemain.SampleMain.setProperties(SampleMain.java:105)
    at com.wily.introscope.server.enterprise.EnterpriseServer$IntroscopeIsengardServer.<init>(EnterpriseServer.java:2118)
    at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:506)
    at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:381)
    at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:324)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)
    at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1595)
    at com.wily.introscope.em.internal.Activator.startEM(Activator.java:119)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.zerog.lax.LAX.launch(Unknown Source)
    at com.zerog.lax.LAX.main(Unknown Source)
    Caused by: java.lang.NumberFormatException: For input string: ""
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
    at java.lang.Integer.parseInt(Integer.java:592)
    at java.lang.Integer.parseInt(Integer.java:615)
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketPort(ServerPropertiesParser.java:412)
    ... 32 more
    10/20/17 02:57:19.080 PM UTC [DEBUG] [main] [Manager] Shudown requested.
    java.lang.Exception: Stack trace
    at java.lang.Thread.dumpStack(Thread.java:1333)
    at com.wily.introscope.server.enterprise.EnterpriseServer.cleanUp(EnterpriseServer.java:1812)
    at com.wily.introscope.server.enterprise.EnterpriseServer.cleanUpSafe(EnterpriseServer.java:1724)
    at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:417)
    at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:324)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)
    at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1595)
    at com.wily.introscope.em.internal.Activator.startEM(Activator.java:119)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.zerog.lax.LAX.launch(Unknown Source)
    at com.zerog.lax.LAX.main(Unknown Source)
    Oct 20, 2017 2:57:19 PM org.springframework.osgi.extender.support.DefaultOsgiApplicationContextCreator createApplicationContext
    INFO: Discovered configurations {osgibundle:/META-INF/spring/*.xml} in bundle [Dependency (com.wily.apm.em.monitor.entity.dependency;singleton:=true)]
    Oct 20, 2017 2:57:19 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
    INFO: Refreshing OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.entity.dependency, config=osgibundle:/META-INF/spring/*.xml): startup date [Fri Oct 20 14:57:19 UTC 2017]; root of context hierarchy
    10/20/17 02:57:19.107 PM UTC [INFO] [main] [Manager] Orderly shutdown complete.
    10/20/17 02:57:19.108 PM UTC [DEBUG] [main] [Manager] Error starting up EM
    com.wily.introscope.server.enterprise.EnterpriseManagerCannotStartException: An error occurred while trying to start Isengard.
    at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:418)
    at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:324)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)
    at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1595)
    at com.wily.introscope.em.internal.Activator.startEM(Activator.java:119)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.zerog.lax.LAX.launch(Unknown Source)
    at com.zerog.lax.LAX.main(Unknown Source)
    Caused by: com.wily.isengard.IsengardException: Invalid value for 'isengard.server.port.channel1' property:
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketPort(ServerPropertiesParser.java:416)
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketProperties(ServerPropertiesParser.java:286)
    at com.wily.isengard.api.server.ServerPropertiesParser.<init>(ServerPropertiesParser.java:164)
    at com.wily.isengard.api.samplemain.SampleMain.setProperties(SampleMain.java:105)
    at com.wily.introscope.server.enterprise.EnterpriseServer$IntroscopeIsengardServer.<init>(EnterpriseServer.java:2118)
    at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:506)
    at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:381)
    ... 26 more
    Caused by: java.lang.NumberFormatException: For input string: ""
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
    at java.lang.Integer.parseInt(Integer.java:592)
    at java.lang.Integer.parseInt(Integer.java:615)
    at com.wily.isengard.api.server.ServerPropertiesParser.initializeServerSocketPort(ServerPropertiesParser.java:412)
    ... 32 more


    ************************************
    ************************************
    Introscope Enterprise Manager failed to start because:
    An error occurred while trying to start Isengard.
    Invalid value for 'isengard.server.port.channel1' property:
    For input string: ""



  • 2.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 11:32 AM

    I tried to edit IntroscopeEnterpriseManager.properties and make the properties for channel look like below and it still breaks.

     

    #######################
    # Port Settings
    #
    # ================

    # The EM is configured with several communication channels.
    # To enable a communication channel, add the channel id to the
    # comma separated list of enabled channels. Likewise, a communication
    # channel may be disabled by removing it from that same list.
    #
    # All communication to the EM is obfuscated, and passwords are always encrypted.

    # The enabled communication channels.
    introscope.enterprisemanager.enabled.channels=channel1

    # Use this to enable both the default channel and secure channel.
    #introscope.enterprisemanager.enabled.channels=channel1,channel2

    # The default communication channel.
    introscope.enterprisemanager.serversocketfactory.channel1=com.wily.isengard.postofficehub.link.net.server.DefaultServerSocketFactory
    introscope.enterprisemanager.port.channel1=

    # The secure (SSL) communication channel.
    introscope.enterprisemanager.serversocketfactory.channel2=com.wily.isengard.postofficehub.link.net.server.SSLServerSocketFactory
    introscope.enterprisemanager.port.channel2=5443
    # Location of a keystore containing certificates for authenticating the EM to clients.
    # Either an absolute path or a path relative to the config directory.
    # On Windows, backslashes must be escaped. For example:
    # introscope.enterprisemanager.keystore.channel2=C:\\Introscope\\config\\internal\\server\\keystore
    introscope.enterprisemanager.keystore.channel2=internal/server/keystore

    # Set this property to true to enable encryption of introscope.enterprisemanager.keypassword.channel2
    # Once introscope.enterprisemanager.keypassword.channel2 is encrypted,
    # this property is automatically set to false.
    #
    # To change the existing password, enter the new password and set this property to true.
    # Note: If this property is set to true and the password is not changed, the existing encrypted password will be encrypted again.
    # If password field for a new channel is configured, add the corresponding
    # plaintextpassword field and set it to true to enable encryption.
    introscope.enterprisemanager.keypassword.channel2.plaintextpassword=true

    # The password for the keystore.
    introscope.enterprisemanager.keypassword.channel2=password
    # Location of a truststore containing trusted client certificates.
    # Either an absolute path or a path relative to the config directory.
    # On Windows, backslashes must be escaped. For example:
    # introscope.enterprisemanager.truststore.channel2=C:\\Introscope\\config\\internal\\server\\keystore
    # The truststore is optional. It is needed only if client authentication is required.
    # If no truststore is specified, the EM trusts all client certificates.
    #introscope.enterprisemanager.truststore.channel2=internal/server/keystore

    # Set this property to true to enable encryption of introscope.enterprisemanager.trustpassword.channel2
    # Once introscope.enterprisemanager.trustpassword.channel2 is encrypted,
    # this property is automatically set to false.
    #
    # To change the existing password, enter the new password and set this property to true.
    # Note: If this property is set to true and the password is not changed, the existing encrypted password will be encrypted again.
    # If password field for a new channel is configured, add the corresponding
    # plaintextpassword field and set it to true to enable encryption.
    # introscope.enterprisemanager.trustpassword.channel2.plaintextpassword=false

    # The password for the truststore
    #introscope.enterprisemanager.trustpassword.channel2=password
    # Set to true to require clients to authenticate.
    # If true, clients must be configured with a keystore containing a certificate trusted by the EM.
    # Default is false
    introscope.enterprisemanager.needclientauth.channel2=false
    # Set the enabled cipher suites.
    # A comma-separated list of cipher suites.
    # If not specified, use the default enabled cipher suites.
    #introscope.enterprisemanager.ciphersuites.channel2=

    # Set the enabled protocols.
    # A comma-separated list of protocols.
    # Comment it to use the default enabled protocols.
    # For SUN/Oracle JVM the user can add SSLv2Hello protocol.
    # IBM JVM accepts SSL_TLSv2, SSL_TLS, TLS protocols as well
    introscope.enterprisemanager.protocols.channel2=TLSv1.2,TLSv1.1,TLSv1



  • 3.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 11:38 AM

    You're missing the port

     

    introscope.enterprisemanager.serversocketfactory.channel1=com.wily.isengard.postofficehub.link.net.server.DefaultServerSocketFactory
    introscope.enterprisemanager.port.channel1=

     

    It should be

    introscope.enterprisemanager.port.channel1=5001

     

    or whatever you want to set the port value to



  • 4.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 11:58 AM

    Now I am getting below error.

    THere is no smartsore dir on the webview server.

    I tried to follow instructions on Enterprise Manager failed to start due to “Failed to map segment from shared object”  but it didn't help.

     

     

    10/20/17 03:50:51.444 PM UTC [DEBUG] [main] [Manager] Shudown requested.
    java.lang.Exception: Stack trace
    at java.lang.Thread.dumpStack(Thread.java:1333)
    at com.wily.introscope.server.enterprise.EnterpriseServer.cleanUp(EnterpriseServer.java:1812)
    at com.wily.introscope.server.enterprise.EnterpriseServer.cleanUpSafe(EnterpriseServer.java:1724)
    at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:402)
    at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:324)
    at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)
    at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1595)
    at com.wily.introscope.em.internal.Activator.startEM(Activator.java:119)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    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(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.zerog.lax.LAX.launch(Unknown Source)
    at com.zerog.lax.LAX.main(Unknown Source)



  • 5.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 12:15 PM

    I think you will really need a support case for this, not just saying that because I work in support but it sounds like a full review of the configuration is required.

     

    You keep referring to the issue of the RocksDB, that would only be an issue for Enterprise Manager.

    What did you actually implement to get around that issue, did you remount the /tmp as executable, or did you add a value to the Introscope_Enterprise_Manager.lax file ?

     

    If it was the lax file, perhaps you could share a before and after for what you did to make sure the setting is in the right place.

     

    You are then mentioning there is no Smartstor on the WebView server, well that's good to run the WebView on a dedicated server, but I just don't actually see how that relates to the problem you have mentioned.

     

    For any Enterprise Manager that is still not starting I would do the following:

     

    1) Go to /product/enterprisemanager/configuration and delete everything EXCEPT for the config.ini file, please do not touch that file or things will be worse.

    2) Go to /work and delete everything, it is just the cache of the embedded Jetty web server

    3) Now try to restart the Enterprise Manager

     

    If you were getting an issue starting WebView, you could go to /product/webview/configuration and delete everything there except for config.ini, and again clear the /work folder in that install.



  • 6.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 12:38 PM

    RockDB issue was on collectors and I just had to clean the .log file under /data/LOG That I just mentioned but this issue here in this thread is very different. I had not to make any change in Introscope_Enterprise_Manager.lax

     

     

    This issue here is only about  the WebView.

    Do I need to have  IntroscopeWebView.properties and IntroscopeEnterpriseManager.properties on a WebView server ?

    I may be asking wrong question here.

    The suggested steps didn't work as well.



  • 7.  Re: EnterpriseManager is not starting 10.5.1.8
    Best Answer

    Posted 10-20-2017 12:47 PM

    Was this a clean install? 

    Which installer did you use?

    Which options did you choose?

     

    Can you describe your APM servers?  (MOM, WebView host, Collectors, AXA server, TIM, etc)

     

    From the sounds of it your configuration files are not set, namely your IntroscopeEnterpriseManager.properties and the tess.db.cfg.xml.

     

    What type of EM (Enterprise Manager) is this?

    Manager of Manager (MOM)

    Collector

    WebView host (if not hosted on the MOM)

     

    From the looks of it, this is a WebView only install in which case you shouldn't be using the EMCtrl.sh script, you should use the WVCtrl.sh script to start WebView.  The channel port, and the smart store information would have been set with the install of the enterprise manager.

     

    So look in your <em_home>/config/IntroscopeWebView.properties to see if the following settings have values:

    introscope.webview.enterprisemanager.tcp.host=<MOM Host>
    introscope.webview.enterprisemanager.tcp.port=5001
    introscope.webview.enterprisemanager.webserver.tcp.port=8080

     

    If those are set, but the settings for the EM are not set then I'm guessing that only WebView was installed and not an enterprise manager.

     

    Best of luck,

     

    Billy



  • 8.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 01:02 PM

    Thank you guys. Great community answers and team work.

    I should know about the design before I ask questions.

    I used WVCtrl.sh and WebView is up.



  • 9.  Re: EnterpriseManager is not starting 10.5.1.8

    Posted 10-20-2017 01:05 PM

    Thanks Billy for giving such a helpful response for Vijay! I hope that others will follow this example and contribute as well. Also helps to follow others. I am now following Vijay and Billy!