IBM License Metric Tool (ILMT)

 View Only
Expand all | Collapse all

ILMT failed import data - error during TLSv1.2 connection with IEM

  • 1.  ILMT failed import data - error during TLSv1.2 connection with IEM

    Posted Fri November 11, 2022 09:28 AM
    Dear Expert,

    I am currently having problems with ILMT. I found an error when importing data from ILMT.
    Here is the import log from ILMT:

    Import Log
    The last megabyte of data from the import log:
    # Logfile created on 2022-10-01 17:00:00 +0000 by logger.rb/v1.2.7
    2022-10-01 17:00:00 (+0:00:00.000) INFO: ILMT version: 9.2.24.0-20210616-1757
    2022-10-01 17:00:00 (+0:00:00.000) INFO: All times in log are in UTC time zone!
    2022-10-01 17:00:00 (+0:00:00.000) INFO: Import created at (UTC): 2022-10-01 17:00:00 UTC
    2022-10-01 17:00:00 (+0:00:00.000) INFO: Import type: complete
    2022-10-01 17:00:00 (+0:00:00.000) INFO: Local server timezone: +0700 ..Asia/Jakarta
    2022-10-01 17:00:00 (+0:00:00.002) INFO: Detected License Metric Tool database version: 11.5.0.0
    2022-10-01 17:00:00 (+0:00:00.003) INFO: [ILMTCore] (Import_ILMTCoreThread) ILMT Core version: 9.2.24.0-2021-06-16_16:05:59
    2022-10-01 17:00:00 (+0:00:00.008) INFO: Previously imported Catalog version: 9.2.24.0
    2022-10-01 17:00:05 (+0:00:05.042) INFO: Check datasources connectivity: Start
    2022-10-01 17:00:05 (+0:00:00.018) INFO: Trying another TLS version because of an error during TLSv1.2 connection with IEM tosmon101p: Connection refused (Connection refused)
    2022-10-01 17:00:05 (+0:00:00.004) ERROR: TemServerAPI::TemServerAPIError: An error occured while preparing to send the request.
    Error during TLSv1 connection with IEM tosmon101p: Connection refused (Connection refused)
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:52:in `send_request'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:203:in `test_connection'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/app/models/datasource_tem_server.rb:95:in `method_missing'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:229:in `block in check_datasources'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/dataset/actions.rb:137:in `block in each'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:825:in `process_result_set'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:754:in `block in fetch_rows'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:259:in `block in execute'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:672:in `statement'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:251:in `block in execute'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/connection_pool/threaded.rb:114:in `hold'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/connecting.rb:254:in `synchronize'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:250:in `execute'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/dataset/actions.rb:921:in `execute'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/adapters/jdbc.rb:754:in `fetch_rows'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/dataset/actions.rb:137:in `each'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/model/plugins.rb:28:in `each'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:226:in `check_datasources'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:45:in `block in run'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:186:in `block in within_import'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/dss/logger.rb:22:in `log_to'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:168:in `block in within_import'
    org/jruby/RubyKernel.java:1897:in `tap'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:158:in `within_import'
    /apps/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:41:in `run'
    :1:in `'
    :1:in `block in '
    2022-10-01 17:00:05 (+0:00:00.013) INFO: Import failed in 0:00:05
    2022-10-01 17:00:05 (+0:00:00.000) INFO: Import contains 1 errors.

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    I need some advice to solve that problem.
    thank you.

    Regards,
    Dodi

    ------------------------------
    Dodi setianto
    ------------------------------


  • 2.  RE: ILMT failed import data - error during TLSv1.2 connection with IEM

    Posted Tue November 29, 2022 01:13 PM
    Hi @Dodi setianto,

    sorry it took us so long to respond, we're in the process of moving to the new Community site and we need more time to get fully up to speed.

    As to the issue you experience, let's start with the basic check - are you able to connect to the BigFix Server using e.g. BigFix Console?

    The next check (assuming you can log in to BigFix Console) would be to see if you are able to reach the BigFix Server from the ILMT Server - you would need to go to the machine where ILMT Server resides and then use e.g. browser to connect to the BigFix:
    https://<BigFix_host>:<BigFix_port>/api/login

    I can see your ILMT Server is running on Linux, so in case you don't have any browser installed there you can also use cURL to check the connectivity:
    curl -k -v "https://<BigFix_host>:<BigFix_port>/api/login"

    Trying to get the above URL should return HTTP 401 response (Unauthorized), but this will prove that the BigFix Server is reachable.

    Also, in many cases, upgrading the ILMT Server to the latest version fixes the issue. Being on the latest ILMT Server version is a requirement from the licensing perspective, so this should be done anyway. It's worth to try whether with this, the issue will also be gone.

    ------------------------------
    kind regards,
    Łukasz
    ------------------------------

    Original Message