Commodore Commodore
Commodore
519 views

[BSM 9.24] View is empty in Service Health but contains CIs

Jump to solution

Hello there,

I have created a Local Impact view which was working fine yesterday. But today, the view displays no data (see screenshot "01_emptyview.png").

In Admin > Service Health > CI Indicators, the view is also empty (see screenshot "02_admin_ci.png").

BUT when I look at the View Builder, the view is perfectly showing results (see screenshots "03_builder_calc.png" and "04_builder_preview.png".

How is it possible? Does anyone has the idea of how to fix that please?

Thanks!

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Commodore Commodore
Commodore

Hi,

After almost one week without error, I think I can mark the topic as solved!

So to resume: one Local Impact View was too big and generated errors in the liv.log (see post above). The solution was to delete the big view (because I think a Local Impact view should always be a small one), and after that to edit the empty views in the Modeling Studio (to force the views to update and regenerate datas).

After that, no more errors!

View solution in original post

0 Likes
6 Replies
Micro Focus Expert
Micro Focus Expert

the last 2 screenshots are from the TQL calculate and preview which are ad-hoc actions. please check the view result in IT Universe.

the first 2 screenshots are from Service Health which using the Viewing System cache results (kept on the GW). try restart the GW and see if you get results or make some change to the view definition which forces recalculation of the view.

0 Likes
Commodore Commodore
Commodore

Hi Asaf,

Thanks for your answer.

I have checked the view in the IT Universe Manager and it was empty too.

I have edited the view in the Modeling Studio, only changing the Hierarchy mode (from Rule-based to Manual) and after saving the view got fulled with the CIs. So after that I have edited the view to reset the mode to Rule-based, and the view displays correctly.

But this is the 2nd time this matter occurs, so I'd like to figure out what's happening. You said it may be related to the Viewing cache system, is there any way to check its state (with JMX of logs)?

On of my teammates has recently added a second Gateway server, do you think this can be related?

Thanks for your help.

0 Likes
Micro Focus Expert
Micro Focus Expert

If the view was empty in ITU then it has nothing to do with the Viewing System cache on the GW. it might be related to RTSM.

in the GW you can goto jmx console (port 8080) and search for viewing_system_cache. you can then see if the View is in the cache and the result size.

0 Likes
Commodore Commodore
Commodore

Hi Asaf,

Ok this morning new CIs have been created in the RTSM, the view has been updated fine for some times but arround midday it showed empty again.

So I had a look to the logs files on the DPS and I found those one that may be interesting (inside topaz_all.ejb.log)

2016-09-08 12:20:01,816 [ajp-0.0.0.0-8009-76] (OdbTreePathUtils.java:254) ERROR - Failed to execute getViewResultTreeNodeFromMETreePath()
java.lang.Exception: METreePath is broken !
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:249)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:122)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:100)
2016-09-08 12:20:01,820 [ajp-0.0.0.0-8009-76] (OdbTreePathUtils.java:304) ERROR - Failed to retrieve a  view result tree node with given UCMDB id (465e6715389a83c85719fb9e664d268c)
2016-09-08 12:20:01,820 [ajp-0.0.0.0-8009-76] (ViewingSystemAccessor.java:229) ERROR - Unexpected error occured while running method getSubTree
java.util.NoSuchElementException: Failed to retrieve a  view result tree node with given UCMDB id (465e6715389a83c85719fb9e664d268c)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:305)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:284)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:255)
2016-09-08 12:20:01,828 [ajp-0.0.0.0-8009-76] (DashboardViewSystemFacade.java:626) ERROR - failed to get data from viewing system
com.hp.bsm.dashboard.dal.exceptions.ViewDataProviderException: Unexpected error occured while running  method getSubTree
	at com.hp.bsm.dashboard.dal.api.impl.ViewingSystemAccessor.getSubTree(ViewingSystemAccessor.java:230)
	at com.hp.bsm.dashboard.dal.api.impl.ViewingSystemAccessor.getSubTree(ViewingSystemAccessor.java:413)
	at com.hp.bsm.dashboard.bl.operation.DashboardViewSystemFacade.getSubTreeWithNoKpis(DashboardViewSystemFacade.java:624)
Caused by: java.util.NoSuchElementException: Failed to retrieve a  view result tree node with given UCMDB id (465e6715389a83c85719fb9e664d268c)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:305)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:284)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:255)
2016-09-08 12:20:01,835 [ajp-0.0.0.0-8009-76] (KpiFL.java:532) ERROR - MERQ-120570: Error while convertVTTNodeIdToCmdbObjectID
com.hp.bsm.dashboard.bl.exceptions.BLException: Unexpected error occured while running  method getSubTree
	at com.hp.bsm.dashboard.bl.operation.DashboardViewSystemFacade.getSubTreeWithNoKpis(DashboardViewSystemFacade.java:627)
	at com.hp.bsm.dashboard.bl.operation.DashboardViewSystemFacade.getSubTreeWithNoKpis(DashboardViewSystemFacade.java:651)
	at com.mercury.am.bac.eum.reports.kpiovertime.KpiFL.getChildrenCmdbIds(KpiFL.java:627)
Caused by: com.hp.bsm.dashboard.dal.exceptions.ViewDataProviderException: Unexpected error occured while running  method getSubTree
	at com.hp.bsm.dashboard.dal.api.impl.ViewingSystemAccessor.getSubTree(ViewingSystemAccessor.java:230)
	at com.hp.bsm.dashboard.dal.api.impl.ViewingSystemAccessor.getSubTree(ViewingSystemAccessor.java:413)
	at com.hp.bsm.dashboard.bl.operation.DashboardViewSystemFacade.getSubTreeWithNoKpis(DashboardViewSystemFacade.java:624)
	... 94 more
Caused by: java.util.NoSuchElementException: Failed to retrieve a  view result tree node with given UCMDB id (465e6715389a83c85719fb9e664d268c)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:305)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromUCmdbID(OdbTreePathUtils.java:284)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:255)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:122)
	at com.hp.me.base.tree.provider.data.server.impl.OdbTreePathUtils.getViewResultTreeNodeFromMETreePath(OdbTreePathUtils.java:100)
	at com.hp.bsm.dashboard.dal.api.impl.ViewingSystemAccessor.getSubTree(ViewingSystemAccessor.java:210)
	... 96 more

I have removed the full stacktrace to prevent this post to become too long.

The cmdbId given is not related to the view (it's not part of it), but maybe this can have side effect?

Do you think this can be related? Maybe I'll have to open a support case?

0 Likes
Commodore Commodore
Commodore

Update : I've also found interesting things in the liv.log file:

2016-09-08 12:37:38,765 [pool-livTopologyPoller-thread-1] (LivService.java:545) FATAL - Liv [Airbus - End User Monitors] of customerId=[1] has breached the maximum allowed size=[1000]
2016-09-08 12:37:38,765 [pool-livTopologyPoller-thread-1] (TopologyPoller.java:381) ERROR - performLivRebuild() - Failed to rebuild tqlName=[Airbus - End User Monitors] for customerId=[1] tqlState=[<TqlState><currentLivQueryVersion>null</currentLivQueryVersion><latestQueryVersion>null</latestQueryVersion><successiveChangesCounter>9</successiveChangesCounter><Collection name='viewNames'><Entry>Airbus - End User Monitors</Entry></Collection></TqlState>]
com.hp.bsm.liv.api.exception.BreachMaxLivCIsAmountException: Liv [Airbus - End User Monitors] of customerId=[1] has breached the maximum allowed size=[1000]
	at com.hp.bsm.liv.internal.service.LivService.rebuildLiv(LivService.java:546)
	at com.hp.bsm.liv.internal.adapter.topology.synchronizer.TopologyPoller.performLivRebuild(TopologyPoller.java:371)
	at com.hp.bsm.liv.internal.adapter.topology.synchronizer.TopologyPoller.processTqlPollingResults(TopologyPoller.java:322)
	at com.hp.bsm.liv.internal.adapter.topology.synchronizer.TopologyPoller.run(TopologyPoller.java:129)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
2016-09-08 12:44:28,983 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Airbus - Dashboard IN Infra Monitoring] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:28,984 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - IC Criticals] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:28,984 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - ICTMonitoring_E2E] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:29,983 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Airbus - Dashboard IN Infra Monitoring] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:29,983 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - IC Criticals] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:29,984 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - ICTMonitoring_E2E] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:31,986 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Airbus - Dashboard IN Infra Monitoring] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:31,986 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - IC Criticals] customerId = [1]. View has not returned from CMDB.
2016-09-08 12:44:31,986 [JMS Session Delivery Thread - FR0-BSM-P02_businessImpact_service_IMS$SESSION$2:-7531823781782749184] (IndicatorsListenerImpl.java:106) ERROR - could not synchronize LIV = [Dashboard - ICTMonitoring_E2E] customerId = [1]. View has not returned from CMDB.

Obviously one local view was too big, maybe impacting all the others local views! So I have removed the big view (not important). Let's see if it changes anything.

0 Likes
Commodore Commodore
Commodore

Hi,

After almost one week without error, I think I can mark the topic as solved!

So to resume: one Local Impact View was too big and generated errors in the liv.log (see post above). The solution was to delete the big view (because I think a Local Impact view should always be a small one), and after that to edit the empty views in the Modeling Studio (to force the views to update and regenerate datas).

After that, no more errors!

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.