IBM Support

Infosphere Information Analyzer thin client error: "Asset metadata search failed!!"

Troubleshooting


Problem

When logging into or working with InfoSphere Information Analyzer thin client, you receive an error message: “Asset metadata search failed!!"

Symptom

Infosphere Information Analyzer thin client fails to display data sets, and you receive an error code 500 containing one the following messages:

  • "Found no active Solr nodes."
  • "Connection to http://<SolrCloud server>:port refused"
  • "No response from Solr."

Cause

  1. ZooKeeper could be down or not responsive.
  2. Solr could be down or not responsive.
  3. Unable to start IBM Information Server SolrCloud service (applicable to Rollup patch 4 or earlier, and on Windows only)
  4. ZooKeeper ensemble is not reachable.
  5. Required "da-datasets" Solr collection (index) has not been created.

Environment

All platforms
Product: Information Server 11.5, with Information Server 11.5 Governance Rollup patch 1 or later installed

Diagnosing The Problem

If the log file contains the following messages then it indicates a problem with ZooKeeper service:
... SystemErr  R ...SearchException: ... ConnectionLoss for /collections/da-datasets/state.json
... SystemErr  R     at ...getActiveBaseUrls(SolrCloudWrapper.java:412)
... SystemErr  R     at ...updateActiveBaseUrlsAndCredentials(SolrCloudWrapper.java:357)
... SystemErr  R     at ...access$000(SolrCloudWrapper.java:57)

... com.ibm.iis.dq.da.util.DALogging E ... Found no active Solr nodes.

If the log file contains the following messages then it indicates a problem with SolrCloud service:


... SystemErr  R ...HttpHostConnectException: Connection to http://<SolrCloud server>:port refused
... SystemErr  R     at ...DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190)
..  SystemErr  R     at ...ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
...
... SystemErr  R     at com.ibm.iis.solr.search.impl.SolrCloudWrapper.doPost(SolrCloudWrapper.java:223)
... SystemErr  R     at com.ibm.iis.solr.search.impl.SolrCloudWrapper.search(SolrCloudWrapper.java:147)
...
... com.ibm.iis.dq.da.util.DALogging E An ... Assert metadata search failed!!... No response from Solr.

If the log file contains following messages then it indicates that the required "da-datasets" Solr collection (index) has not been created.:


... SystemErr  R ...SearchException: ... NoNode for /collections/da-datasets/state.json
... SystemErr  R     at ...getActiveBaseUrls(SolrCloudWrapper.java:412)
... SystemErr  R     at ...updateActiveBaseUrlsAndCredentials(SolrCloudWrapper.java:357)
... SystemErr  R     at ...SolrCloudWrapper.initialize(SolrCloudWrapper.java:264)

The default location of the log file is:


    For InfoSphere Information Server with WebSphere Application Server Network Deployment
    AIX or Linux
    /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1/SystemOut.log
    Windows
    C:\IBM\WebSphere\AppServer\profiles\InfoSphere\logs\server1\SystemOut.log

    For InfoSphere Information Server with WebSphere Application Server Liberty Profile
    AIX or Linux
    /opt/IBM/InformationServer/wlp/usr/servers/iis/logs/messages.log
    Windows
    C:\IBM\InformationServer\wlp\usr\servers\iis\logs\messages.log 

Resolving The Problem

1. Make sure ZooKeeper service, has started successfully. If not, start the ZooKeeper service and then start/restart SolrCloud.

    AIX or Linux
    InfoSrvZookeeper
    Windows
    IBM Information Server ZooKeeper

2. Make sure SolrCloud service has started successfully. If not, start the SolrCloud service.
    AIX or Linux
    InfoSrvSolrCloud
    Windows
    IBM Information Server SolrCloud

3. Windows specific - If you have Rollup patch 4 or earlier, and installed on a non-default drive, for example "F:" drive, then "IBM Information Server SolrCloud" service fails to start due to a known defect in solr.cmd batch file. Use the following steps to remediate the problem; use the appropriate drive letter and directory path for your installation:

    1) Stop Solr if it has been already stated from a command line.

        cd F:\IBM\InformationServer\shared-open-source\solr
        stop-solr.bat

    2) Make a copy of the solr.cmd batch file in F:\IBM\InformationServer\shared-open-source\solr\install\bin folder.

    3) Open the solr.cmd batch file for editing (in Notepad, for example) and change the following line at 867, from:

    cd "%SOLR_SERVER_DIR%"
    to:
    cd /d "%SOLR_SERVER_DIR%"

    4) Save and close the file.

    5) Start "IBM Information Server SolrCloud" service.

4. If you are not using the default port (52181) for ZooKeeper then make sure the ZooKeeper connection string (com.ibm.iis.sdp.zookeeper.connect) is set correctly. If not, use the iisAdmin tool to set to correct value. In a command line window, run the following commands using the appropriate directory path, host and port numbers for your installation:

    AIX or Linux
    cd /opt/IBM/InformationServer/ASBServer/bin
    ./iisAdmin.sh -set -key com.ibm.iis.sdp.zookeeper.connect -value localhost:52181 

    Windows
    C:\IBM\InformationServer\ASBServer\bin 
    iisAdmin -set -key com.ibm.iis.sdp.zookeeper.connect -value localhost:52181 

5. Create "da-datasets" Solr collection (index). In a command line window, run the following commands using the appropriate directory path and right Solr port number for your installation (58983 is default Solr port number):

    AIX or Linux
    export JAVA_HOME="/opt/IBM/InformationServer/jdk"
    cd /opt/IBM/InformationServer/shared-open-source/solr/install/bin

    If you have Rollup patch 4 or later:
    ./solr create_collection -c "da-datasets" -shards 1 -replicationFactor 1 -port 58983 -d da-datasets_configs

    If you have Rollup patch 3 or earlier:
    ./solr create_collection -c "da-datasets" -shards 1 -replicationFactor 1 -port 58983 -d /opt/IBM/InformationServer/ASBServer/solr_configs/da_datasets_configs

    Note: You may need permission to run solr batch command or may need to use sudo.

    Windows
    "set JAVA_HOME=C:\IBM\InformationServer\jdk\jre" (without double quotes)
    cd C:\IBM\InformationServer\shared-open-source\solr\install\bin

    If you have Rollup patch 4 or later:
    .\solr create_collection -c "da-datasets" -shards 1 -replicationFactor 1 -port 58983 -d da-datasets_configs

    If you have Rollup patch 3 or earlier:
    .\solr create_collection -c "da-datasets" -shards 1 -replicationFactor 1 -port 58983 -d C:\IBM\InformationServer\ASBServer\solr_configs\da_datasets_configs

    Note: Make sure to remove any trailing spaces after jre in the above set command. Any trailing spaces will cause running solr batch file to fail.


You do not need to restart InfoSphere Information Server. InfoSphere Information Analyzer thin client should start to function properly after two minutes. If you are using InfoSphere Information Server with WebSphere Application Server Network Deployment, you can restart the InfoSphere Information Server application immediately.

Helpful hint: Solr Administration web user interface (UI) can be used to check if Solr is running or not. To bring up the UI, use the following URL: http://<Solr server>:<port>/solr/#/. This UI also contains "Core Selector" drop-down button at the bottom left which lists available Solr cores. It can be used to check if "da-datasets" is created or not.

[{"Product":{"code":"SSZJLG","label":"InfoSphere Information Analyzer"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 June 2018

UID

swg21977845

Page Feedback