Topology errors in SiteScope 11.20 bac_integration.log files

Depending on the type of monitor being deployed and type of topology being sent, the errors in the bac_integration.log can be varied. Some examples of these errors are:

1. For a “Dynamic Disk Space” monitor sending its Default (Multiple) topology:

2012-10-10 20:52:21,995 [TopologyReporterSender] (TopologyReporterSender.java:393) ERROR – failed to run main topology agent. topologyCommand=TopologyCommand{commandType=RUN_SCRIPT, destinationData=<destination><destinationData name="class_type_id">1</destinationData><destinationData name="u_iConnectionId">1600736</destinationData><destinationData name="monitor_logical_name">Test_DDS_01</destinationData><destinationData name="measurements_to_eti_map" /><destinationData name="monitor_full_path">1600715</destinationData><destinationData name="is_report_default_hi">true</destinationData><destinationData name="logging_option">logAllData</destinationData><destinationData name="parent_group_name">Shrey_Test</destinationData><destinationData name="host_type">nt</destinationData><destinationData name="class_real_name">Dynamic Disk Space</destinationData><destinationData name="id">00000000000000000000000000000000</destinationData><destinationData name="domain_name">DefaultDomain</destinationData><destinationData name="monitor_description"></destinationData><destinationData name="monitor_properties">com.mercury.infra.xdr_utils.prop_bag_array@1602c39c</destinationData><destinationData name="file_system" />

…..

java.lang.Exception: Failed Running script :filesystem_topology.py

at com.hp.ucmdb.discovery.probe.services.dynamic.core.TopologyTablesProcessorUtil.processDestinationTables(TopologyTablesProcessorUtil.java:176)

at com.hp.ucmdb.discovery.probe.services.dynamic.core.TopologyDynamicService.process(TopologyDynamicService.java:37)

at com.hp.ucmdb.discovery.probe.agents.topology.MainTopologyAgent.run(MainTopologyAgent.java:487)

at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.send(TopologyReporterSender.java:380)

at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.run(TopologyReporterSender.java:330)

at java.lang.Thread.run(Thread.java:722)

Caused by: Traceback (innermost last):

File "<string>", line 2, in ?

File "filesystem_topology", line 26, in DiscoveryMain

AttributeError: module ‘system_lib’ has no attribute ‘createFileSystemFromMap’

at org.python.core.Py.AttributeError(Py.java)

at org.python.core.PyObject.__getattr__(PyObject.java)

2. For a “Script” monitor sending “Business Application” topology

2012-09-14 13:38:13,073 [TopologyReporterSender] (TopologyReporterSender.java:393) ERROR – failed to run main topology agent. topologyCommand=TopologyCommand{commandType=RUN_SCRIPT, destinationData=<destination><destinationData name="class_type_id">1</destinationData><destinationData name="u_iConnectionId">600568</destinationData><destinationData name="monitor_logical_name">prospero test script</destinationData><destinationData name="monitored_selected_ci_changed">true</destinationData><destinationData name="measurements_to_eti_map" /><destinationData name="monitor_full_path">600001.600012</destinationData><destinationData name="prev_organization_attr" /><destinationData name="is_report_default_hi">false</destinationData><destinationData name="logging_option">logOnlyThresholdsMeasuremnts</destinationData><destinationData name="parent_group_name">Test</destinationData><destinationData name="cur_key_attributes" /><destinationData name="host_type">unix</destinationData><destinationData name="class_real_name">Script</destinationData><destinationData name="id">00000000000000000000000000000000</destinationData><destinationData name="domain_name">DefaultDomain</destinationData><destinationData name="monitor_description"></destinationData><destinationData name="monitor_properties">com.mercury.infra.xdr_utils.prop_bag_array@1cc8130</destinationData>

java.lang.Exception: Failed Running script :user_defined_topology.py

at com.hp.ucmdb.discovery.probe.services.dynamic.core.TopologyTablesProcessorUtil.processDestinationTables(TopologyTablesProcessorUtil.java:176)

at com.hp.ucmdb.discovery.probe.services.dynamic.core.TopologyDynamicService.process(TopologyDynamicService.java:37)

at com.hp.ucmdb.discovery.probe.agents.topology.MainTopologyAgent.run(MainTopologyAgent.java:487)

at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.send(TopologyReporterSender.java:380)

at com.mercury.sitescope.integrations.bac.topology.TopologyReporterSender.run(TopologyReporterSender.java:330)

at java.lang.Thread.run(Thread.java:722)

Caused by: Traceback (innermost last):

File "<string>", line 2, in ?

File "user_defined_topology", line 32, in DiscoveryMain

AttributeError: module ‘common_lib’ has no attribute ‘getProductName’

at org.python.core.Py.AttributeError(Py.java)

at org.python.core.PyObject.__getattr__(PyObject.java)

This is a known defect when integrating SiteScope 11.20 with BSM 9.1x. The problem is that, BSM 9.1x contains .py and .py.11 files in the sitescope.zip package used for the integration. SiteScope is supposed to use the .py.11 files for topology generation. However, it ends up using the older .py files instead. This leads to failures when generating topology.

Fix the sitescope.zip package to contain only .py.11 script files:

You can use the fixed sitescope.zip package attached here or you can generate the fixed zip package manually using the steps below:

a. From BSM UI > Admin > RTSM Administration > Administration > Package Manager, navigate to the sitescope.zip package

b. Right click > Export package > Save on your local server

c. Extract sitescope.zip and, from sitescope/discoveryScripts, remove all .py files. It should only contain .py.11 files.

d. Zip the file -> make sure you zip only the contents of the sitescope folder and not the sitescope folder itself. That is, the structure inside the zip file should NOT be sitescope.zip -> sitescope -> actual folders. It should be sitescope.zip -> actual folders. Retain the name sitescope.zip for the fixed zip package.

Deploy the fixed zip package via BSM UI > Admin > RTSM Administration > Administration > Package Manager. Click on Deploy packages to server (from local disk).

Confirm that new .py files are automatically downloaded into SiteScope’s discovery\scripts folder.

Confirm that no more script related exceptions occur in the bac_integration.log file

P.S. The original out-of-the-box sitescope.zip package will still be available for reference in the DPS server – <HPBSM>\odb\conf\factory_packages\sitescope.zip

Advertisements

2 thoughts on “Topology errors in SiteScope 11.20 bac_integration.log files

  1. Gleb

    Thank you for suggestions, followed them, but I have SiteScope.zip already with only .py.11 files (SS 11.20 + BSM 9.2). But still have errors:

    File “filesystem_topology”, line 26, in DiscoveryMain
    AttributeError: module ‘system_lib’ has no attribute ‘createFileSystemFromMap’

    Can you please advice something?
    Thanks!

    Reply
  2. Marc Hurtado

    Hi Abdul.
    Your trick was OK until i restarted BSM last monday. Then, sitescope.zip was replaced by the original one on BSM Suite. Where is this packet stored, to modify it permanently?
    Thanks.

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s