Informix

nested-group-icon.png

DB2

Expand all | Collapse all

onkstore keeps crashing when configuring KMIP

  • 1.  onkstore keeps crashing when configuring KMIP

    Posted 28 days ago
      |   view attached
    Hi All,

    I am trying to configure KMIP Keystore in Informix. But the onkstore keeps on crashing. Not sure how to troubleshoot this. Any suggestions?

    =======
    Creating a 'kmip' type keystore.
    *** Error in `onkstore': munmap_chunk(): invalid pointer: 0x00000000004afed3 ***
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x7f5d4)[0x7f5858cc15d4]
    /lib64/libgsk8cms_64.so(gsk_free+0x19)[0x7f5855779735]
    /lib64/libgsk8cms_64.so(_Z8gsk_freePvS_+0x24)[0x7f58557799a0]
    /lib64/libgsk8km_64.so(GSKKM_Free+0x52)[0x7f58559c6686]
    onkstore(genEAR_StoreCert+0xc8)[0x4b0068]
    onkstore(PKCS12FileFromCreds+0x3ec)[0x4bd7cc]
    onkstore(main+0x1f9)[0x4ad5b9]
    /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5858c643d5]
    onkstore[0x4add91]
    ======= Memory map: ========
    00400000-0078c000 r-xp 00000000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    0098c000-009aa000 r-xp 0038c000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    009aa000-009c3000 rwxp 003aa000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    009c3000-009de000 rwxp 00000000 00:00 0
    0266d000-02822000 rwxp 00000000 00:00 0 [heap]
    7f5854f79000-7f585519d000 r-xp 00000000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7f585519d000-7f585529c000 ---p 00224000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7f585529c000-7f58552cd000 rwxp 00223000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7f58552cd000-7f58552da000 rwxp 00000000 00:00 0
    7f58552da000-7f5855379000 r-xp 00000000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7f5855379000-7f5855479000 ---p 0009f000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7f5855479000-7f585547f000 rwxp 0009f000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7f585547f000-7f5855867000 r-xp 00000000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7f5855867000-7f5855966000 ---p 003e8000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7f5855966000-7f5855996000 rwxp 003e7000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7f5855996000-7f5855a91000 r-xp 00000000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7f5855a91000-7f5855b91000 ---p 000fb000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7f5855b91000-7f5855ba4000 rwxp 000fb000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7f5855ba4000-7f585754c000 rwxp 00000000 00:00 0
    7f585754c000-7f5857559000 r-xp 00000000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7f5857559000-7f5857758000 ---p 0000d000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7f5857758000-7f5857759000 r-xp 0000c000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7f5857759000-7f585775b000 rwxp 0000d000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7f585775b000-7f5857a02000 r-xp 00000000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7f5857a02000-7f5857c02000 ---p 002a7000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7f5857c02000-7f5857c11000 r-xp 002a7000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7f5857c11000-7f5857c13000 rwxp 002b6000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7f5857c13000-7f5857c14000 rwxp 00000000 00:00 0
    7f5857c14000-7f5857dd1000 r-xp 00000000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7f5857dd1000-7f5857fd0000 ---p 001bd000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7f5857fd0000-7f5857fe3000 r-xp 001bc000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7f5857fe3000-7f5857fe4000 rwxp 001cf000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7f5857fe4000-7f5857fe6000 rwxp 00000000 00:00 0
    7f5857fe6000-7f5857fe7000 r-xp 00000000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7f5857fe7000-7f58581e6000 ---p 00001000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7f58581e6000-7f58581e7000 r-xp 00000000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7f58581e7000-7f58581f3000 r-xp 00000000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7f58581f3000-7f58583f2000 ---p 0000c000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7f58583f2000-7f58583f3000 r-xp 0000b000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7f58583f3000-7f58583f4000 rwxp 0000c000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7f58583f4000-7f58583fa000 rwxp 00000000 00:00 0
    7f58583fa000-7f58583fe000 r-xp 00000000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7f58583fe000-7f58585fe000 ---p 00004000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7f58585fe000-7f58585ff000 r-xp 00004000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7f58585ff000-7f5858600000 rwxp 00005000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7f5858600000-7f585861e000 r-xp 00000000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7f585861e000-7f585881d000 ---p 0001e000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7f585881d000-7f585881e000 r-xp 0001d000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7f585881e000-7f585881f000 rwxp 0001e000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7f585881f000-7f5858829000 rwxp 00000000 00:00 0
    7f5858829000-7f585883e000 r-xp 00000000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7f585883e000-7f5858a3d000 ---p 00015000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7f5858a3d000-7f5858a3e000 r-xp 00014000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7f5858a3e000-7f5858a3f000 rwxp 00015000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7f5858a3f000-7f5858a41000 r-xp 00000000 ca:01 70032 /usr/lib64/libfreebl3.so
    7f5858a41000-7f5858c40000 ---p 00002000 ca:01 70032 /usr/lib64/libfreebl3.so
    7f5858c40000-7f5858c41000 r-xp 00001000 ca:01 70032 /usr/lib64/libfreebl3.soAborted
    [informix@ip-172-31-23-184 ~]$

    ============


    ------------------------------
    Amit Kumar Thakur
    Software Engineer
    +91-9953946465
    ------------------------------


  • 2.  RE: onkstore keeps crashing when configuring KMIP

    Posted 28 days ago
    Hi Amit,

    1. it is always helpful to let people know, which version of Informix you are using.
        (For the moment, I assume it is some 14.10.xC? with '?' in [ 1,2,3]. But knowing
        the '?' precisely could be helpful/decisive.)

    2. based on my above assumption, it looks to me that there is a problem with the
        CA certificate file that you have to provide as part of the KMIP credentials.
        This file is supposed to be in PEM format (a.k.a 'base64 encoded') and should have
        as header and footer line:
        -----BEGIN CERTIFICATE-----
        -----END CERTIFICATE-----

    3. in order to put the CA certificate into the keystore to be created, the CA certificate file
        is first decoded (from the PEM format to binary data). From the backtrace stack you
        provided, my guess is, that this decoding didn't work.

    4. did you get any error message on stdout or stderr? I guess, you did not.
        (In case you did, such an error message may provide a better indication as to what
        the problem is.)

    5. to test the PEM format of your CA certificate file, you may use an OpenSSL command
        like the following:
          openssl enc -d -base64 -in <your_pem_file> -none -out <some_output_file>
        This command should work successfully.
        (Unfortunately, I do not know of an equivalent command using the GSKit
        utility "gsk8capicmd".)

    6. Having said all of the above, I strongly suggest, that you open a case with
        Informix Tech Support.

        While there can always be some problem with an input file, "onkstore" should not
        crash in the way you described. Instead, it should provide an error message (that hopefully
        is meaningful enough to help you determine the problem). In that sense, the crash instread
        of provision of an error message is a defect that should be fixed (if it is not already fixed
        in the new version to be released).
        A Tech Support case helps a lot to get such things fixed.

    Regards, Martin
    --
    Martin Fuerderer
    Informix Development Germany


    HCL Technologies Germany GmbH
    Frankfurter Ring 17
    80807 Munich, Germany
    http://www.hcltech.com/de
    --DISCLAIMER--
    ------------------------------------------------------------------------------------------------------------
    This document is intended for transmission to the named recipient only. If you are not that person, you should note that legal rights reside in this document and you are not authorized to access, read, disclose, copy, use or otherwise deal with it and any such actions are prohibited and may be unlawful. The views expressed in this document are not necessarily those of HCL Technologies Ltd. Notice is hereby given that no representation, contract or other binding obligation shall be created by this e-mail, which must be interpreted accordingly. Any representations, contractual rights or obligations shall be separately communicated in writing and signed in the original by a duly authorized officer of the relevant company.
    ------------------------------------------------------------------------------------------------------------

    ::DISCLAIMER::

    The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.






  • 3.  RE: onkstore keeps crashing when configuring KMIP

    Posted 27 days ago
    Hi Martin,

    Thanks for the update.

    Some open-ended questions answered below.

    > I am using HCL Informix Latest Version: 14.10.FC3.

    > The CA Certificate is not an issue here as I created 2-3 times a remote KMIP Keystore and a key was created. You can create as many keys as per your infra security requirement but now when i try to create a new key "onkstore crashes " with the above error. 

    > As per documentation it is expecting a .crt file which has the private key intact.

    ==========HCL Informix Documentation=============

    When asked to create a KMIP type keystore the following information must be readily available by the operator:
    • KMIP Server, the IP address or hostname where the KMIP server is listening for request. If the port where the server listens is different from the default (5696), the port must be specified (ie "myserver.hcl.com:2356).
    • KMIP Username, username to access the KMIP server. This is optional since in most cases, the access to the server is done by using SSL certificates.
    • KMIP Password, password for the given username. This is also optional.
    • KMIP Client Certificate File, a file containing the certificate for the client, The file must also contain the Private Key matching the certificate. The private key is expected to be a PKCS#8 key. The certificate is expected to have Authentication extensions.
    • KMIP CA Certificate File, a file containing the root CA used to sign both the KMIP Client Certificate File and the KMIP Server Certificate File.
    • KMIP Key Name, The name of the KMIP Key used as MEK by the Storage Spaces Encryuption feature or as RMEK by the Integrated backup Encryption Feature. It is optional. If not present, onkstore will generate a new key and report its Id to the operator.

    =================

    https://informix.hcldoc.com/14.10/help/topic/com.ibm.adref.doc/ids_adr_onkstore.htm

    Do let me if you need some more info.

    Regards
    Amit Kumar Thakur 


    ------------------------------
    Amit Kumar Thakur
    Software Engineer
    +91-9953946465
    ------------------------------



  • 4.  RE: onkstore keeps crashing when configuring KMIP

    Posted 27 days ago
    Hi Amit,

    I think you really should open a case with Informix Tech Support for this problem.

    I'm not sure, what exactly you mean by "a .crt file".
    If I understand you correctly, you are saying that you already have created and stored keys in your KMIP service using the same KMIP CA certificate file. Are you suggesting, that instead the problem is with the KMIP Client Certificate File? Which is different each time you create/store a key in your KMIP service? In that case, can you look at the older KMIP Client Certificate files, that you have used successfully, to figure out the differences between those (successful) files and the one you want to use now, which causes the error?

    Regards, Martin

    --
    Martin Fuerderer
    Informix Development Germany


    HCL Technologies Germany GmbH
    Frankfurter Ring 17
    80807 Munich, Germany
    http://www.hcltech.com/de
    --DISCLAIMER--
    ------------------------------------------------------------------------------------------------------------
    This document is intended for transmission to the named recipient only. If you are not that person, you should note that legal rights reside in this document and you are not authorized to access, read, disclose, copy, use or otherwise deal with it and any such actions are prohibited and may be unlawful. The views expressed in this document are not necessarily those of HCL Technologies Ltd. Notice is hereby given that no representation, contract or other binding obligation shall be created by this e-mail, which must be interpreted accordingly. Any representations, contractual rights or obligations shall be separately communicated in writing and signed in the original by a duly authorized officer of the relevant company.
    ------------------------------------------------------------------------------------------------------------

    ::DISCLAIMER::

    The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.






  • 5.  RE: onkstore keeps crashing when configuring KMIP

    Posted 27 days ago

    The GSK should be able to validate the cert – so we can remote/confirm that as the issue

     

    Cheers

    Paul

     






  • 6.  RE: onkstore keeps crashing when configuring KMIP

    Posted 27 days ago
    Hi Paul,

    Cert is not the issue as of now. If it would be it should have never created a key at the first place. It should have thrown the error as SSL Error : 414.

    ------------------------------
    Amit Kumar Thakur
    Software Engineer
    +91-9953946465
    ------------------------------



  • 7.  RE: onkstore keeps crashing when configuring KMIP

    Posted 27 days ago
    Hi Martin,

    I am working with Infra team to get a support ticket open with IBM.

    So this is the Certificate file with which I created a KMIP key.

    KMIP Client Certificate File
    > /home/informix/Certificates/kmip_client.crt
    KMIP CA Certificate File
    > /home/informix/Certificates/sdkms_cert.crt

    When I run Onkstore -verify command, it verifies the same.
    ===========

    [informix@ip-172-31-23-184 Certificates]$ ls
    archive ca.pem certs client.csr faisal sdkms_ca_chain.crt sdkms_ca.crt sdkms_ca.crt.orig sdkms_ca_final.crt sdkms_test_ca.crt
    [informix@ip-172-31-23-184 Certificates]$ onkstore -verify
    Enter the filename for the target <<NEED NAME FOR P12 FILE HERE>>:/home/informix/server/etc/fortanix.p12
    Keystore Verify Successful. Type: KMIP, Cipher: aes192
    Key exists at a7359609-a368-4462-b629-07e65dd56447.
    [informix@ip-172-31-23-184 Certificates]$
    [informix@ip-172-31-23-184 Certificates]$
    [informix@ip-172-31-23-184 Certificates]$
    ===============================

    Now let's create a new KMIP key name as Amit with Cipher Aes256

    [informix@ip-172-31-23-184 etc]$ onkstore -file Amit -cipher aes256
    Which type of keystore would you like to create:
    1 - Local Keystore
    2 - AWS EAR Keystore
    3 - AWS BAR Keystore
    4 - KMIP EAR Keystore
    5 - Azure EAR
    6 - Azure BAR
    4
    KMIP Server
    > sdkms.fortanix.com
    KMIP Username
    > 31b030a9-ccf3-4121-978c-750ebcb53b97
    KMIP Password
    > IcN00ryh6KFuhq0Ecesx2g
    KMIP Client Certificate File
    > /home/informix/Certificates/kmip_client.crt
    KMIP CA Certificate File
    > /home/informix/Certificates/sdkms_cert.crt
    KMIP Key Name
    > ee5a219d-6ebb-4c9c-aac0-164dc7bc1a1d
    Creating a 'kmip' type keystore.
    *** Error in `onkstore': munmap_chunk(): invalid pointer: 0x00000000004afed3 ***
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x7f5d4)[0x7fdfdbc485d4]
    /lib64/libgsk8cms_64.so(gsk_free+0x19)[0x7fdfd8700735]
    /lib64/libgsk8cms_64.so(_Z8gsk_freePvS_+0x24)[0x7fdfd87009a0]
    /lib64/libgsk8km_64.so(GSKKM_Free+0x52)[0x7fdfd894d686]
    onkstore(genEAR_StoreCert+0xc8)[0x4b0068]
    onkstore(PKCS12FileFromCreds+0x3ec)[0x4bd7cc]
    onkstore(main+0x1f9)[0x4ad5b9]
    /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fdfdbbeb3d5]
    onkstore[0x4add91]
    ======= Memory map: ========
    00400000-0078c000 r-xp 00000000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    0098c000-009aa000 r-xp 0038c000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    009aa000-009c3000 rwxp 003aa000 ca:01 14162775 /opt/informix/14.10.FC3/bin/onkstore
    009c3000-009de000 rwxp 00000000 00:00 0
    00ccc000-00e80000 rwxp 00000000 00:00 0 [heap]
    7fdfd7f00000-7fdfd8124000 r-xp 00000000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7fdfd8124000-7fdfd8223000 ---p 00224000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7fdfd8223000-7fdfd8254000 rwxp 00223000 ca:01 5838894 /usr/local/ibm/gsk8_64/lib64/C/icc/icclib/libicclib084.so
    7fdfd8254000-7fdfd8261000 rwxp 00000000 00:00 0
    7fdfd8261000-7fdfd8300000 r-xp 00000000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7fdfd8300000-7fdfd8400000 ---p 0009f000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7fdfd8400000-7fdfd8406000 rwxp 0009f000 ca:01 8671914 /usr/local/ibm/gsk8_64/lib64/libgsk8kicc_64.so
    7fdfd8406000-7fdfd87ee000 r-xp 00000000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7fdfd87ee000-7fdfd88ed000 ---p 003e8000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7fdfd88ed000-7fdfd891d000 rwxp 003e7000 ca:01 8671911 /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so
    7fdfd891d000-7fdfd8a18000 r-xp 00000000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7fdfd8a18000-7fdfd8b18000 ---p 000fb000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7fdfd8b18000-7fdfd8b2b000 rwxp 000fb000 ca:01 8671916 /usr/local/ibm/gsk8_64/lib64/libgsk8km_64.so
    7fdfd8b2b000-7fdfda4d3000 rwxp 00000000 00:00 0
    7fdfda4d3000-7fdfda4e0000 r-xp 00000000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7fdfda4e0000-7fdfda6df000 ---p 0000d000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7fdfda6df000-7fdfda6e0000 r-xp 0000c000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7fdfda6e0000-7fdfda6e2000 rwxp 0000d000 ca:01 1974335 /opt/informix/14.10.FC3/gls/dll/64-libglu.so.60
    7fdfda6e2000-7fdfda989000 r-xp 00000000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7fdfda989000-7fdfdab89000 ---p 002a7000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7fdfdab89000-7fdfdab98000 r-xp 002a7000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7fdfdab98000-7fdfdab9a000 rwxp 002b6000 ca:01 2063329 /opt/informix/14.10.FC3/gls/dll/64-libicui18n.so.60
    7fdfdab9a000-7fdfdab9b000 rwxp 00000000 00:00 0
    7fdfdab9b000-7fdfdad58000 r-xp 00000000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7fdfdad58000-7fdfdaf57000 ---p 001bd000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7fdfdaf57000-7fdfdaf6a000 r-xp 001bc000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7fdfdaf6a000-7fdfdaf6b000 rwxp 001cf000 ca:01 2063330 /opt/informix/14.10.FC3/gls/dll/64-libicuuc.so.60
    7fdfdaf6b000-7fdfdaf6d000 rwxp 00000000 00:00 0
    7fdfdaf6d000-7fdfdaf6e000 r-xp 00000000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7fdfdaf6e000-7fdfdb16d000 ---p 00001000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7fdfdb16d000-7fdfdb16e000 r-xp 00000000 ca:01 2063328 /opt/informix/14.10.FC3/gls/dll/64-libicudata.so.60
    7fdfdb16e000-7fdfdb17a000 r-xp 00000000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7fdfdb17a000-7fdfdb379000 ---p 0000c000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7fdfdb379000-7fdfdb37a000 r-xp 0000b000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7fdfdb37a000-7fdfdb37b000 rwxp 0000c000 ca:01 88243 /usr/lib64/libnss_files-2.17.so
    7fdfdb37b000-7fdfdb381000 rwxp 00000000 00:00 0
    7fdfdb381000-7fdfdb385000 r-xp 00000000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7fdfdb385000-7fdfdb585000 ---p 00004000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7fdfdb585000-7fdfdb586000 r-xp 00004000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7fdfdb586000-7fdfdb587000 rwxp 00005000 ca:01 96159 /usr/lib64/libcap-ng.so.0.0.0
    7fdfdb587000-7fdfdb5a5000 r-xp 00000000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7fdfdb5a5000-7fdfdb7a4000 ---p 0001e000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7fdfdb7a4000-7fdfdb7a5000 r-xp 0001d000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7fdfdb7a5000-7fdfdb7a6000 rwxp 0001e000 ca:01 96162 /usr/lib64/libaudit.so.1.0.0
    7fdfdb7a6000-7fdfdb7b0000 rwxp 00000000 00:00 0
    7fdfdb7b0000-7fdfdb7c5000 r-xp 00000000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7fdfdb7c5000-7fdfdb9c4000 ---p 00015000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7fdfdb9c4000-7fdfdb9c5000 r-xp 00014000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7fdfdb9c5000-7fdfdb9c6000 rwxp 00015000 ca:01 88213 /usr/lib64/libz.so.1.2.7
    7fdfdb9c6000-7fdfdb9c8000 r-xp 00000000 ca:01 70032 /usr/lib64/libfreebl3.so
    7fdfdb9c8000-7fdfdbbc7000 ---p 00002000 ca:01 70032 /usr/lib64/libfreebl3.so
    7fdfdbbc7000-7fdfdbbc8000 r-xp 00001000 ca:01 70032 /usr/lib64/libfreebl3.soAborted
    [informix@ip-172-31-23-184 etc]$

    =============

    This error is consistent.


     


    ------------------------------
    Amit Kumar Thakur
    Software Engineer
    +91-9953946465
    ------------------------------