cancel
Showing results for 
Search instead for 
Did you mean: 

willy introscope error

former_member1334776
Participant
0 Kudos

Dear Experts,

We are facing a problem in starting willy intoroscope.

I started manually as ./EMCtrl.sh start.

It is started and after some time it has stopped.

Please find the logs for your reference..

I set dispaly variable also but i am not able to set in ...

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

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

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

5/17/13 09:32:14.258 AM IST [ERROR] [main] [Manager] The EM failed to start. Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.

5/17/13 09:32:14.830 AM IST [INFO] [main] [Manager] Shutting down data persistence subsystem

5/17/13 09:32:14.832 AM IST [INFO] [main] [Manager] Shutting down the Isengard server

5/17/13 09:32:14.836 AM IST [INFO] [main] [Manager.IscopeAlertsExtension] Isengard Alert Extension Bean has been passivated

5/17/13 09:32:14.839 AM IST [INFO] [main] [Manager.DependencyMapServerBean] DependencyMapServerBean passivate

5/17/13 09:32:14.894 AM IST [INFO] [main] [Manager] Orderly shutdown complete.

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

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

Introscope Enterprise Manager failed to start because:

An error occurred while trying to start Isengard.

Press 'Enter' to acknowledge....

Thanks,

Thamodaran.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Thamodaran,

Please refer to sap note 1776332 - CA Wily Introscope Enterprise Manager start fails after error "Unable to open the Perst backing store"

Resolution

Stop Enterprise Manager

Rename file "/usr/sap/ccms/apmintroscope/traces/traces_YYYYMMDD.db" to "/usr/sap/ccms/apmintroscope/traces/traces_YYYYMMDD.db.backup"

Start Enterprise Manager

Kind Regards,

Johan


Former Member
0 Kudos

Can you attach full log file?

former_member1334776
Participant
0 Kudos

Dear vivek,

Thanks for your reply..

I checked the space/usr/sap has more space...

# The default communication channel.

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

introscope.enterprisemanager.port.channel1=6001.

Please find the full logs for your reference..

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

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

Introscope Enterprise Manager failed to start because:

An error occurred while trying to start Isengard.

Press 'Enter' to acknowledge....

Debug options:

    file:/tmp/.options not found

May 18, 2013 9:52:45 AM org.springframework.osgi.extender.internal.activator.ContextLoaderListener start

INFO: Starting [org.springframework.osgi.extender] bundle v.[1.2.1]

May 18, 2013 9:52:45 AM org.springframework.osgi.extender.internal.support.ExtenderConfiguration <init>

INFO: No custom extender configuration detected; using defaults...

May 18, 2013 9:52:45 AM org.springframework.scheduling.timer.TimerTaskExecutor afterPropertiesSet

INFO: Initializing Timer

5/18/13 09:52:47 AM IST [INFO] [Manager] Introscope Enterprise Manager Release 9.1.0.2 (Build 581100)

5/18/13 09:52:47 AM IST [INFO] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.

5/18/13 09:52:47 AM IST [INFO] [Manager] Using Introscope installation at: /usr/sap/ccms/apmintroscope/willyintroscope/.

5/18/13 09:52:47 AM IST [INFO] [Manager] CA Introscope(R) Version 9.1

5/18/13 09:52:47 AM IST [INFO] [Manager] Copyright (c) 2012 CA. All Rights Reserved.

5/18/13 09:52:47 AM IST [INFO] [Manager] Introscope(R) is a registered trademark of CA.

5/18/13 09:52:47 AM IST [INFO] [Manager] Starting Introscope Enterprise Manager...

5/18/13 09:52:47 AM IST [INFO] [Manager] Found valid license file: /usr/sap/ccms/apmintroscope/willyintroscope/./license/SAP.em.lic

5/18/13 09:52:47 AM IST [INFO] [Manager]

****** CA Wily Introscope License ******

        type = em-sap

        rev = 30

        cid = sap-ags

        organization = SAP Active Global Support

        reg-id = sap-end-user

        email = none

        sum = 27618b562bc2239e3cf71d9542c76df4

5/18/13 09:52:48 AM IST [INFO] [Manager.HotFailover] Hot Failover not enabled

5/18/13 09:52:50.542 AM IST [INFO] [main] [Manager] Introscope Enterprise Manager Release 9.1.0.2 (Build 581100)

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] Using Introscope installation at: /usr/sap/ccms/apmintroscope/willyintroscope/.

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] CA Introscope(R) Version 9.1

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] Copyright (c) 2012 CA. All Rights Reserved.

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] Introscope(R) is a registered trademark of CA.

5/18/13 09:52:50.543 AM IST [INFO] [main] [Manager] Starting Introscope Enterprise Manager...

5/18/13 09:52:50.544 AM IST [INFO] [main] [Manager]

****** CA Wily Introscope License ******

        type = em-sap

        rev = 30

        cid = sap-ags

        organization = SAP Active Global Support

        reg-id = sap-end-user

        email = none

        sum = 27618b562bc2239e3cf71d9542c76df4

5/18/13 09:52:50.545 AM IST [INFO] [main] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.

5/18/13 09:52:50.565 AM IST [INFO] [main] [Manager] Starting server...

May 18, 2013 9:52:50 AM 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)]

May 18, 2013 9:52:50 AM org.springframework.osgi.extender.support.DefaultOsgiApplicationContextCreator createApplicationContext

INFO: Discovered configurations {osgibundle:/META-INF/spring/*.xml} in bundle [Config (com.wily.apm.em.monitor.config)]

May 18, 2013 9:52:50 AM 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 [Sat May 18 09:52:50 IST 2013]; root of context hierarchy

May 18, 2013 9:52:50 AM org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext unpublishContextAsOsgiService

INFO: Application Context service already unpublished

May 18, 2013 9:52:50 AM org.springframework.context.support.AbstractApplicationContext prepareRefresh

INFO: Refreshing OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.config, config=osgibundle:/META-INF/spring/*.xml): startup date [Sat May 18 09:52:50 IST 2013]; root of context hierarchy

May 18, 2013 9:52:50 AM org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext unpublishContextAsOsgiService

INFO: Application Context service already unpublished

May 18, 2013 9:52:51 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from URL [bundleentry://91/META-INF/spring/apm-monitor-config-context.xml]

May 18, 2013 9:52:51 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from URL [bundleentry://95/META-INF/spring/apm-em-monitor-dependency-context.xml]

May 18, 2013 9:52:51 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from URL [bundleentry://95/META-INF/spring/apm-em-monitor-dependency-osgi.xml]

May 18, 2013 9:52:51 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from URL [bundleentry://91/META-INF/spring/apm-monitor-config-osgi.xml]

May 18, 2013 9:52:51 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from URL [bundleentry://91/META-INF/spring/apm-monitor-config-poller-context.xml]

5/18/13 09:52:51.780 AM IST [INFO] [main] [Manager.Authentication] Introscope WebView connections are enabled

5/18/13 09:52:51.780 AM IST [INFO] [main] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor stageOne

INFO: No outstanding OSGi service dependencies, completing initialization for OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.config, config=osgibundle:/META-INF/spring/*.xml)

May 18, 2013 9:52:51 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons

INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@672ae2bc: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,jaxb2Marshaller,jaxbFormattedOutput,jaxbSchemaLocation,booleanTrue,marshallerProperties,persister,safeConfig,monitorEventConfigManagerOsgi,monitorConfigPersisterOsgi,trigger,scheduler,configMediator,monitorEventConfigManager]; root of factory hierarchy

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor stageOne

INFO: No outstanding OSGi service dependencies, completing initialization for OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.config, config=osgibundle:/META-INF/spring/*.xml)

May 18, 2013 9:52:51 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons

INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@672ae2bc: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,jaxb2Marshaller,jaxbFormattedOutput,jaxbSchemaLocation,booleanTrue,marshallerProperties,persister,safeConfig,monitorEventConfigManagerOsgi,monitorConfigPersisterOsgi,trigger,scheduler,configMediator,monitorEventConfigManager]; root of factory hierarchy

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&monitorEventConfigManagerOsgi] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.config.persist.IMonitorEventConfigManager)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&monitorEventValueManagerOsgi] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.service.IMonitorEventValueManager)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&monitorEventValueDependencyOsgi] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.service.IMonitorEventValueManager)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&cmonitorConfigPersisterOsgi] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.config.persist.IMonitorConfigDependencyHandler)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&configPersisterOsgi] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.config.persist.IMonitorConfigPersister)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager doFindDependencies

INFO: Adding OSGi service dependency for importer [&configPersisterDependentServices] matching OSGi filter [(objectClass=com.wily.apm.em.monitor.entity.dependency.IMonitorConfigPersisterDependencyHelper)]

May 18, 2013 9:52:51 AM org.springframework.osgi.extender.internal.dependencies.startup.DependencyServiceManager findServiceDependencies

INFO: OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.entity.dependency, config=osgibundle:/META-INF/spring/*.xml) is waiting for unsatisfied dependencies [[&monitorEventConfigManagerOsgi, &monitorEventValueDependencyOsgi, &cmonitorConfigPersisterOsgi, &configPersisterOsgi, &configPersisterDependentServices]]

May 18, 2013 9:52:51 AM org.springframework.oxm.jaxb.Jaxb2Marshaller createJaxbContextFromContextPath

INFO: Creating JAXBContext with context path [com.wily.apm.em.monitor.config]

5/18/13 09:52:51.949 AM IST [INFO] [main] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private

May 18, 2013 9:52:52 AM org.springframework.scheduling.concurrent.ExecutorConfigurationSupport initialize

INFO: Initializing ExecutorService  'scheduler'

May 18, 2013 9:52:52 AM org.springframework.osgi.service.exporter.support.OsgiServiceFactoryBean registerService

INFO: Publishing service under classes [{com.wily.apm.em.monitor.config.persist.IMonitorConfigEmitter, com.wily.apm.em.monitor.config.persist.IMonitorEventConfigManager}]

May 18, 2013 9:52:52 AM org.springframework.osgi.service.exporter.support.OsgiServiceFactoryBean registerService

INFO: Publishing service under classes [{com.wily.apm.em.monitor.config.persist.IMonitorConfigDependencyHandler, com.wily.apm.em.monitor.config.persist.IMonitorConfigPersister}]

May 18, 2013 9:52:52 AM org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext publishContextAsOsgiServiceIfNecessary

INFO: Publishing application context as OSGi service with properties {org.springframework.context.service.name=com.wily.apm.em.monitor.config, Bundle-SymbolicName=com.wily.apm.em.monitor.config, Bundle-Version=9.1.0}

May 18, 2013 9:52:52 AM org.springframework.osgi.extender.internal.support.DefaultOsgiBundleApplicationContextListener onOsgiApplicationEvent

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

5/18/13 09:52:52.515 AM IST [INFO] [main] [Manager] Started hot config polling.  Polling interval set to 60 seconds

5/18/13 09:52:52.983 AM IST [INFO] [main] [Manager.ServerSocketFactory] Created Server Socket Factory: com.wily.jip.server.ext.DefaultServerSocketFactory

5/18/13 09:52:52.992 AM IST [INFO] [main] [Manager] Using data directory: /usr/sap/ccms/apmintroscope/willyintroscope/data

5/18/13 09:52:53.007 AM IST [INFO] [main] [Manager] Using archive directory /usr/sap/ccms/apmintroscope/willyintroscope/data/archive

5/18/13 09:52:53.008 AM IST [INFO] [main] [Manager] Reading Smartstor Metadata

5/18/13 09:52:53.036 AM IST [INFO] [main] [Manager] Loading metadata file: data/metrics.metadata

5/18/13 09:52:53.040 AM IST [INFO] [main] [Manager] Finished reading Smartstor Metadata

5/18/13 09:52:53.040 AM IST [INFO] [main] [Manager] The system will store non-counter zero values.

5/18/13 09:52:53.040 AM IST [INFO] [main] [Manager] The system will shut down if there are Disk I/O errors in 5 continuous timeslices.

5/18/13 09:52:53.046 AM IST [INFO] [main] [Manager] Thread priority set at 1

5/18/13 09:52:53.047 AM IST [INFO] [main] [Manager] Data tier 1 configured at collection frequency 15 seconds for 1 day

5/18/13 09:52:53.047 AM IST [INFO] [main] [Manager] Data tier 2 configured at collection frequency 60 seconds for 7 days

5/18/13 09:52:53.047 AM IST [INFO] [main] [Manager] Data tier 3 configured at collection frequency 300 seconds for 23 days

5/18/13 09:52:53.047 AM IST [INFO] [main] [Manager] SmartStor Tiering time offset configured to 0:00

5/18/13 09:52:53.048 AM IST [INFO] [main] [Manager] SmartStor conversion of Spool to Data time offset configured to 0 minute

5/18/13 09:52:53.074 AM IST [INFO] [main] [Manager] Available processors is 4

5/18/13 09:52:53.075 AM IST [INFO] [main] [Manager.ConnectionTicket] Agent connection tickets = 4

5/18/13 09:52:53.192 AM IST [INFO] [main] [Manager.Agent] Agent automatic unmount delay configured to 60 minute(s).

5/18/13 09:52:53.329 AM IST [WARN] [main] [Manager.AppMapAgentService] [Application Triage Map feature is disabled.  Please verify if introscope.apm.feature.enabled property is set to false by mistake in properties file.]

5/18/13 09:52:53.364 AM IST [INFO] [main] [Manager.TransactionTracer] Storage directory configured to /usr/sap/ccms/apmintroscope/willyintroscope/traces

5/18/13 09:52:53.364 AM IST [INFO] [main] [Manager.TransactionTracer] Configured introscope.enterprisemanager.transactionevents.storage.queue.limit to 1000

5/18/13 09:52:53.486 AM IST [ERROR] [main] [Manager] The EM failed to start. Unable to open the Perst backing store: /usr/sap/ccms/apmintroscope/willyintroscope/traces/traces_20130508.db

5/18/13 09:52:53.498 AM IST [INFO] [main] [Manager] Shutting down data persistence subsystem

5/18/13 09:52:53.500 AM IST [INFO] [main] [Manager] Shutting down the Isengard server

5/18/13 09:52:53.537 AM IST [INFO] [main] [Manager] Orderly shutdown complete.

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

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

Introscope Enterprise Manager failed to start because:

An error occurred while trying to start Isengard.

Press 'Enter' to acknowledge....

                                           

Thanks,

Thamodaran.

Vivek_Hegde
Active Contributor
0 Kudos

Hi,


Please check the solution mentioned in below thread.

http://scn.sap.com/thread/2093882


1. check if there is enough space in the directories /traces and /data.

2. use the script IndexRebuilder.sh in EM installation folder to try to rebuild the data corrupted.

3. If there is any error appearing during executing the script, that means the historical data got corrupted and cannot be rebuilt. Proceed to next item (4).

4. As mentioned in the section 2.17 "Enterprise Manager Corrupted Data Files" in the IntroscopeFAQ.pdf attached in the NOTE 797147, the solution is to delete the directories /traces and /data and restart your  EM to re-generate these directories. The side effect is that you will lose all historical data that is stored in the Enterprise Manager.

Vivek

Vivek_Hegde
Active Contributor
0 Kudos

Also check \usr\sap\ccms\wilyintroscope\config\IntroscopeEnterpriseManager properties file and see EM is pointing to the right port.