Return
-
Title
"Fail to synchronize derivation calculation" messages -
Description
Shortly after upgrading the SQL cartridge, I am seeing several of the following WARN rolling in the FMS logs:
2011-06-21 17:38:27.469 WARN [TopologySync_Worker-1] com.quest.nitro.service.derivation.ComplexDerivationDefinition - Fail to synchronize derivation calculation DerivationCalculation for "availability" on 'BaselineResponseTimeSLP' calculated by ((#averageResponseTime# > (registry("BaselineFactor") * #baselineResponseTime#)) ? 0 : 1) TIME_DRIVEN with topology changes.
com.quest.nitro.service.derivation.DerivationDefinitionException: Encountered runtime error while starting derivation
at com.quest.nitro.service.derivation.DerivationCalculation.start(DerivationCalculation.java:379)
at com.quest.nitro.service.derivation.ComplexDerivationDefinition.syncTopology(ComplexDerivationDefinition.java:344)
at com.quest.nitro.service.derivation.DerivationService.performTopologySync(DerivationService.java:329)
at com.quest.nitro.service.derivation.DerivationService.syncTopology(DerivationService.java:307)
at com.quest.nitro.service.derivation.DerivationService.execute(DerivationService.java:1146)
at com.quest.nitro.service.scheduler.QuartzSchedulerService$ScheduleJob.execute(QuartzSchedulerService.java:462)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
Caused by: com.quest.nitro.service.topology.TopologyTypeNotFoundException: BaselineResponseTimeSLP
at com.quest.nitro.service.topology.TopologyService.getType(TopologyService.java:828)
at com.quest.nitro.service.topology.TopologyService.getType(TopologyService.java:790)
at com.quest.nitro.service.query.legacy.walker.inmemory.IMTopRoot.getResolvedTopologyType(IMTopRoot.java:177)
at com.quest.nitro.service.query.legacy.walker.inmResolution
The warning is not serious.
The ThresholdResponseTimeSLP topology type was removed from the system but some rogue derivations remained in memory and failed to process the topology change.
If the type was removed intentionally there should be no loss of functionality.Generate an FMS support bundle then restart the Foglight Management Server (see https://support.quest.com/Search/SolutionDetail.aspx?id=SOL41911 for details on generating support bundle).
If the problem persists after the restart, generate a second FMS support bundle and submit both support bundles to Support for further review.
Leave a Comment
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy