AIX Open Source

 View Only
Expand all | Collapse all

DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

  • 1.  DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Tue December 13, 2022 07:42 AM

    Hallo,

    i have taken follow Updates:

    AIX --> 7200-05-05-2246 (for this Problem no effect.. same on other 7200-05-04)
    openssl :
    openssl.base 1.1.1.1202 COMMITTED Open Secure Socket Layer
    openssl.license 1.1.1.1202 COMMITTED Open Secure Socket License
    openssl.man.en_US 1.1.1.1202 COMMITTED Open Secure Socket Layer
    openssl.base 1.1.1.1202 COMMITTED Open Secure Socket Layer

    ->
    curl-7.85.0-1.ppc
    krb5-libs-1.18.5-2.ppc
    -->
    I have erase openssl-1.0.2u-1withsslv2.ppc with my rpm manager
    -->
    Update all newest Packages with dnf update...
    -->

    After this think the DNF operate normaly but follow test fail:

    -->
    dnf install tripwire ## Test install Fileset tripwire --- ALL OK. (Installed: tripwire-2.4.3.7-1.ppc Complete!)
    dnf erase tripwire ##  Test to erase this
    -->snip-->
    Running transaction check
    Transaction check succeeded.
    Running transaction test
    Transaction test succeeded.
    Running transaction
    Preparing : 1/1
    Erasing : tripwire-2.4.3.7-1.ppc [==================================================================================================================== ] 1/1Illegal instruction

    # rpm -qa
    warning: rpmdb: Freeing read locks for locker 0x11a: 10027274/1
    warning: rpmdb: Freeing read locks for locker 0x11c: 10027274/1
    warning: rpmdb: Freeing read locks for locker 0x11d: 10027274/1
    warning: rpmdb: Freeing read locks for locker 0x11e: 10027274/1

    after rpm --rebuilddb i take the package list on rpm -qa, i try to remove with rpm -e tripwire... this running ok (some filesets are allready deletet (from dnf)).

    My systems without this update running OK ..

    Any help ?

    Tomas













    ​​

    ------------------------------
    Tomas Michal
    ------------------------------


  • 2.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Tue December 13, 2022 07:56 AM

    Follow Info:

    This behaivor is very strange:
    It only happens with the tripwire package.

    i Test with the package (screen) on my first step i running in the same error.. But when i reinstall the screen and remove with rpm -e screen, after this action works
    dnf install screen and dnf erase screen completly.

    The dnf erase tripwire command generate the fail and the follow coredump : errpt:

    -->
    LABEL: CORE_DUMP
    IDENTIFIER: A924A5FC

    Date/Time: Tue Dec 13 13:55:03 NFT 2022
    Sequence Number: 2050
    Machine Id: 00CFEA074C00
    Node Id: wnppia13
    Class: S
    Type: PERM
    WPAR: Global
    Resource Name: SYSPROC

    Description
    SOFTWARE PROGRAM ABNORMALLY TERMINATED

    Probable Causes
    SOFTWARE PROGRAM

    User Causes
    USER GENERATED SIGNAL

    Recommended Actions
    CORRECT THEN RETRY

    Failure Causes
    SOFTWARE PROGRAM

    Recommended Actions
    RERUN THE APPLICATION PROGRAM
    IF PROBLEM PERSISTS THEN DO THE FOLLOWING
    CONTACT APPROPRIATE SERVICE REPRESENTATIVE

    Detail Data
    SIGNAL NUMBER
    4
    USER'S PROCESS ID:
    8454420
    FILE SYSTEM SERIAL NUMBER
    9
    INODE NUMBER
    4256
    CORE FILE NAME
    /opt/freeware/core
    PROGRAM NAME
    python3_32
    STACK EXECUTION DISABLED
    0
    COME FROM ADDRESS REGISTER
    ??
    PROCESSOR ID
    hw_fru_id: 2
    hw_cpu_id: 27

    ADDITIONAL INFORMATION
    ??
    rpmlogLev 50
    rpmlogDef 1A8
    dolog 1D0
    rpmlog 148
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    ??
    _PyMethod 450
    _PyMethod 68
    _PyEval_E 85E0
    PyEval_Ev 34
    function_ A4
    _PyEval_E 830C
    PyEval_Ev 34
    _PyEval_E B44
    _PyFuncti AC
    _PyEval_E 7B30
    PyEval_Ev 34
    _PyEval_E B44
    _PyFuncti AC
    _PyEval_E 830C
    PyEval_Ev 34
    _PyEval_E B44
    _PyFuncti AC
    _PyEval_E 7B30
    PyEval_Ev 34
    function_ A4
    _PyEval_E 7638
    PyEval_Ev 34
    function_ A4
    _PyEval_E 7638
    PyEval_Ev 34
    function_ A4
    _PyEval_E 7638
    PyEval_Ev 34
    _PyEval_E B44
    _PyFuncti AC
    _PyEval_E 7638
    PyEval_Ev 34
    _PyEval_E B44
    _PyFuncti AC
    _PyEval_E 7B30
    PyEval_Ev 34
    _PyEval_E B44
    PyEval_Ev 58
    PyEval_Ev 30
    run_mod 48
    PyRun_Fil C8
    PyRun_Sim 11C
    PyRun_Any A4
    pymain_ma 498
    _Py_UnixM 48
    main 10
    __start 6C

    Symptom Data
    REPORTABLE
    1
    INTERNAL ERROR
    0
    SYMPTOM CODE
    PCSS/SPI2 FLDS/python3_3 SIG/4 FLDS/rpmlogLev VALU/50
    -->






    ------------------------------
    Tomas Michal
    ------------------------------

    Original Message


  • 3.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Wed December 14, 2022 04:56 AM

    Dear IBM-OpenSource-Community-Team,

    we have the same issue after upgrading AIX 7.2 to the latest level auf TL5 (7200-05-05-2246) with some of our own RPM-packages:

    ====================================================================================================================
    Package Architecture Version Repository Size
    ====================================================================================================================
    Installing:
    dnf-test ppc 1.0.0-1 @commandline 6.0 k

    Transaction Summary
    ====================================================================================================================
    Install 1 Package

    Total size: 6.0 k
    Installed size: 0
    Is this ok [y/N]: y
    Downloading Packages:
    Running transaction check
    Transaction check succeeded.
    Running transaction test
    Transaction test succeeded.
    Running transaction
    Preparing : 1/1
    Installing : dnf-test-1.0.0-1.ppc [ ] 1/1Illegal instruction (core dumped)

    After some tests we found out, that this happens with our rpms, when setting user-rights of a non-existing user or group.

    So, we can reproduce the coredump with a very simple SPEC-File.

    The "Source0"-File is a simple "touch /opt/freeware/src/packages/SOURCE/dnf-test.txt".

    The spec-file for producing the above coredump is:

    Summary: Test DNF Install-Coredump
    Name: dnf-test
    Version: 1.0.0
    Release: 1%{?dist}
    License: Apache
    Group: System Environment/Daemons
    URL: https://www.medat.de
    Source0: dnf-test.txt
    BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
    Provides: dnf-test = %{version}

    %description
    Test of dnf coredump

    %prep
    export PATH=/opt/freeware/bin:$PATH
    rm -rf %{_builddir}/%{name}
    %setup -q -c -T -n %{name}

    %build

    %install
    [ "${RPM_BUILD_ROOT}" != "/" ] && rm -rf ${RPM_BUILD_ROOT}

    mkdir -p ${RPM_BUILD_ROOT}/tmp/dnf-test
    cp %{SOURCE0} ${RPM_BUILD_ROOT}/tmp/dnf-test

    %clean
    [ "${RPM_BUILD_ROOT}" != "/" ] && rm -rf ${RPM_BUILD_ROOT}

    %files
    %defattr(-,root,system,-)
    %attr(771,abc,def) %dir /tmp/dnf-test/

    %changelog
    * Web Dec 14 2022 Stefan Kirchberg <s.kirchberg@medat.de>-1.0.0-1
    - Testpackage for dnf-Coredump created

    On older AIX (7.1 or old 7.2) Versions this works fine.
    Changing "%attr(771,abc,def) %dir /tmp/dnf-test/" in "%attr(771,root,system) %dir /tmp/dnf-test/" works without generating a coredump:

    Running transaction
    Preparing : 1/1
    Installing : dnf-test-1.0.1-1.ppc 1/1
    Verifying : dnf-test-1.0.1-1.ppc 1/1

    Installed:
    dnf-test-1.0.1-1.ppc

    Complete!

    In our own RPM-Files we have the opportunity to set correct usernames.
    The problem is critical with not self-created packages. Is it possible to prevent python from coredumping on errors (other than looking for the corresponding SPEC-file to lookup what's wrong or which usernames are used and create unknown users first)?

    Best regards

    Stefan



    ------------------------------
    Stefan Kirchberg
    ------------------------------

    Original Message


  • 4.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Wed December 14, 2022 09:45 PM
    I had the same issue today, but thought it was due to some HIGHLY experimental things :-)

    I did the following, and that cleared it up:
    # rm -r /var/lib/rpm/__db*
    # rpm --rebuilddb

     

    ​​

    ------------------------------
    Jan Harris
    AIX Development Support (Liaison to the AIX Toolbox for Open Source)
    IBM (Contract)
    Austin TX
    ------------------------------

    Original Message


  • 5.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Thu December 15, 2022 03:24 AM
    Hi Jan,

    with an "rpm --rebuild" it is possible to get rid of the RPM-Errors after a coredump, but the coredump of the dnf-install occurs every time I try to install (or deinstall) the same rpm-Package producing the core.
    The only option is to use "rpm" on command line. rpm is able to install/uninstall these packages without any errors. But it cannot install/uninstall dependencies on it's own.

    Best regards
    Stefan


    ------------------------------
    Stefan Kirchberg
    ------------------------------

    Original Message


  • 6.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Thu December 15, 2022 04:26 AM
    Hello,

    as already described there is a problem with the dnf, with an erase the package remains in the RPM DB but the files are already deleted. The RPB DB is then also possibly broken.

    This results of course then further errors with dnf, since by the previous actions the DB is defective.

    the rpm --reubuilddb repairs the DB, after then you must must delete  the rpm package with rpm manually since they are contained in the catalog but on the system no more contents have.

    The rpm gives here error messages that he can no longer delete files, but the package is then out of the DB.

    But I don't think it's because of the new TL AIX.

    I have two Systems:
    7200-05-04-2220 (System A / RPM´s little bit older)
    7200-05-04-2220 (System B / RPM´s new updatet)

    Follow Filesets are different :

    System A System B
    bzip2-1.0.8-4.ppc bzip2-1.0.8-2.ppc FALSCH
    curl-7.83.1-1.ppc curl-7.85.0-1.ppc FALSCH
    expat-2.4.6-1.ppc expat-2.4.9-1.ppc FALSCH
    gettext-0.21-1.ppc gettext-0.21-2.ppc FALSCH
    gnutls-3.7.1-1.ppc gnutls-3.7.2-1.ppc FALSCH
    krb5-libs-1.18.5-1.ppc krb5-libs-1.18.5-2.ppc FALSCH
    libcomps-0.1.11-100.ppc libcomps-0.1.11-101.ppc FALSCH
    libgpg-error-1.42-1.ppc libgpg-error-1.45-1.ppc FALSCH
    libksba-1.4.0-1.ppc libksba-1.6.0-1.ppc FALSCH
    libsmbclient-4.14.12-1.ppc libsmbclient-4.16.5-1.ppc FALSCH
    libtextstyle-0.21-1.ppc libtextstyle-0.21-2.ppc FALSCH
    libunistring-1.0-1.ppc libunistring-0.9.10-1.ppc FALSCH
    libxml2-2.9.14-1.ppc libxml2-2.10.2-1.ppc FALSCH
    libzstd-1.4.4-100.ppc libzstd-1.5.2-1.ppc FALSCH
    - openldap-devel-2.4.59-2.ppc FALSCH
    openssl-1.0.2u-1withsslv2.ppc - FALSCH
    python3-3.7.12-1.ppc python3-3.7.15-1.ppc FALSCH
    python3-libcomps-0.1.11-100.ppc python3-libcomps-0.1.11-101.ppc FALSCH
    samba-4.14.12-1.ppc samba-4.16.5-1.ppc FALSCH
    samba-client-4.14.12-1.ppc samba-client-4.16.5-1.ppc FALSCH
    samba-common-4.14.12-1.ppc samba-common-4.16.5-1.ppc FALSCH
    samba-devel-4.14.12-1.ppc samba-devel-4.16.5-1.ppc FALSCH
    samba-libs-4.14.12-1.ppc samba-libs-4.16.5-1.ppc FALSCH
    samba-winbind-4.14.12-1.ppc samba-winbind-4.16.5-1.ppc FALSCH
    samba-winbind-clients-4.14.12-1.ppc samba-winbind-clients-4.16.5-1.ppc FALSCH
    sqlite-3.37.2-1.ppc sqlite-3.39.3-1.ppc FALSCH
    vim-common-8.2.4938-1.ppc vim-common-9.0.0325-1.ppc FALSCH
    vim-minimal-8.2.4938-1.ppc vim-minimal-9.0.0325-1.ppc FALSCH

    System A have:
    openssl.base 1.0.2.2103 COMMITTED Open Secure Socket Layer
    openssl.base 1.0.2.2103 COMMITTED Open Secure Socket Layer

    System B have:
    openssl.base 1.1.1.1202 COMMITTED Open Secure Socket Layer
    openssl.license 1.1.1.1202 COMMITTED Open Secure Socket License
    openssl.man.en_US 1.1.1.1202 COMMITTED Open Secure Socket Layer
    openssl.base 1.1.1.1202 COMMITTED Open Secure Socket Layer

    but the openssl is not the problem.

    System A Operating normally with dnf, the System B have the same Errors (Coredumps etc.) with dnf.

    TOmas










    ------------------------------
    Tomas Michal
    ------------------------------

    Original Message


  • 7.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Fri December 16, 2022 12:15 PM
    Hi Team,

    I had a similar issue with the dnf install and the db install failed. The install failure also corrupted the rpm database. I performed the rpm db rebuild from this IBM Support post.

    https://www.ibm.com/support/pages/how-resolve-rpm-dbrunrecovery-errors

    But every time I tried the install of the new db rpm file using dnf I received the illegal instruction error and corrupted the rpm database again.

    I performed the rpm database rebuild a second time then downloaded the new db-5.3.28-1 rpm from the link below.

    https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/db/db-5.3.28-1.aix6.1.ppc.rpm

    and installed with rpm -i db/db-5.3.28-1.aix6.1.ppc.rpm

    I received an error that the new version conflicted with an older db version db-4.8.24-3.ppc which I then deleted using the rpm -e command

    rpm -e db-4.8.24-3.ppc

    Finally I installed the new db rpm with the rpm -i command

    rpm -i db/db-5.3.28-1.aix6.1.ppc.rpm

    Now the dnf check shows no errors and I was able to install the updated clamav using dnf with no errors.

     
    I hope this helps!

    Stan

    ------------------------------
    Stanley
    ------------------------------

    Original Message


  • 8.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Thu December 22, 2022 06:11 AM

    Hi,

    we got an Update on python3 and some dnf-libs via the Community Repository.
    Afterwards our test-rpms, which were causing a cordump prior to this update, can be installed only with the expected warnings.

    Thanks for the changes!
    Happy holidays and a happy new year!

    Best regards

    Stefan



    ------------------------------
    Stefan Kirchberg
    ------------------------------

    Original Message


  • 9.  RE: DNF Illegal instruction after Update Openssl (1.1.1.1202) / CURL and AIX TL05 / Coredump /

    Posted Thu December 22, 2022 06:58 AM
    Hi Stefan,

    Yes. Also, please also have a look at this post https://community.ibm.com/community/user/power/discussion/recent-dnf-and-yum-issues-with-newer-python3-and-curl-builds

    ------------------------------
    SANGAMESH
    ------------------------------

    Original Message