IBM License Metric Tool (ILMT)

IBM License Metric Tool (ILMT)

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  Problem after migrate bigfix\ilmt to new server

    Posted 08/04/23 02:12 PM

    Hi Guys, 

    got problem with Bigfix/ILMT. 

    I made update i must make mudate to new infrastructure ad install new bigfix/ilmt. 

    Migrate computers to new server with these instruction -> 

    https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-all-license-metric-tool-server-components-different-computer

    Now can log to ilmt + console but cant import data because new ilmt looking for old instance. And must do  Software Classification again :( 

    Maybe i skip smt to do hmmm ....

    Any help will be welcome. 

    Regards

    Mariusz

    ... 

    Start Time: 08/04/2023 06:00 AM
    Status: Failed
    Duration: 0:00:04

     

    Import Log
    The last megabyte of data from the import log: 
    # Logfile created on 2023-08-04 04:00:00 +0000 by logger.rb/v1.5.1
2023-08-04 04:00:00 (+0:00:00.000) INFO: ILMT version: 9.2.32.0-20230621-0049
2023-08-04 04:00:00 (+0:00:00.000) INFO: All times in log are in UTC time zone!
2023-08-04 04:00:00 (+0:00:00.000) INFO: Import created at (UTC): 2023-08-04 04:00:00 UTC
2023-08-04 04:00:00 (+0:00:00.000) INFO: Import type: complete
2023-08-04 04:00:00 (+0:00:00.000) INFO: Local server timezone: CurrentTimeZone=120 (UTC+01:00) DaylightBias=-60
2023-08-04 04:00:00 (+0:00:00.000) INFO: Detected License Metric Tool database version: 16.0.4045.3
2023-08-04 04:00:00 (+0:00:00.000) INFO: [ILMTCore] (Import_ILMTCoreThread) ILMT Core version: 9.2.32.0-2023-06-20_22:59:52
2023-08-04 04:00:00 (+0:00:00.016) INFO: Previously imported Catalog version: 9.2.32.16
2023-08-04 04:00:00 (+0:00:00.109) INFO: Check datasources connectivity: Start
2023-08-04 04:00:02 (+0:00:02.048) INFO: Trying another TLS version because of an error during TLSv1.2 connection with IEM EOPX-LMT-SRV01.energa.loc: Connection refused: connect
2023-08-04 04:00:04 (+0:00:02.037) ERROR: TemServerAPI::TemServerAPIError: An error occured while preparing to send the request.
Error during TLSv1 connection with IEM EOPX-LMT-SRV01.energa.loc: Connection refused: connect
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:52:in `send_request'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:203:in `test_connection'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/app/models/datasource_tem_server.rb:99:in `method_missing'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:247:in `block in check_datasources'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:137:in `block in each'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:825:in `process_result_set'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:754:in `block in fetch_rows'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:259:in `block in execute'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:672:in `statement'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:251:in `block in execute'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/connection_pool/threaded.rb:114:in `hold'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/database/connecting.rb:254:in `synchronize'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:250:in `execute'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:921:in `execute'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:754:in `fetch_rows'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:137:in `each'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/model/plugins.rb:28:in `each'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:244:in `check_datasources'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:54:in `block in run'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:204:in `block in within_import'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/dss/logger.rb:22:in `log_to'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:186:in `block in within_import'
	org/jruby/RubyKernel.java:1940:in `tap'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:168:in `within_import'
	C:/IBM/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:41:in `run'
	:1:in `'
	:1:in `block in '


    ------------------------------
    Mariusz Kulma
    ------------------------------


  • 2.  RE: Problem after migrate bigfix\ilmt to new server

    Posted 08/05/23 03:17 AM

    Hello Mariusz,

    So, is the 'EOPX-LMT-SRV01.energa.loc' pointing to new or old instance ?
    Please keep in mind that this 'Migrating...' instruction assumes that you've created two independent datasources on ILMT (using 'Management > Data Sources' panel).
    This is the point of this     reconciliation mode...one datasource points to new instance and the other to an old instance.
    Of course, both BigFix instances needs to be up and running to allow ILMT to make a proper migration.

    That particular error (TemServerAPI::TemServerAPIError: An error occured while preparing to send the request) suggests that one of those two BigFix instances is unavailable.
    (ignore that 'TLS version' error as this is leftover from pre-TLSv1.2 times).


    To verify the current ILMT state please upload the screenshot from 'Management > Data Sources' panel.



    ------------------------------
    Thank you,
    Oktawian

    Oktawian Powązka, L3 Support
    IBM License Metric Tool
    ------------------------------



Related Content