Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Ciore dump on zypper update

  1. #11

    Default Re: Ciore dump on zypper update

    Quote Originally Posted by xorbe View Post
    I see that poster's problem is crashing while downloading in all 3 logs, smells like a hardware issue to me. Or corrupted binaries. Or both.
    Yea, go with the easy answer. The old corrupted binaries and hardware issue.

  2. #12
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,769

    Default Re: Ciore dump on zypper update

    Try force install zypper from yast.

    or download the rpm and use rpm to install bypassing zypper entirely

  3. #13

    Default Re: Ciore dump on zypper update

    Quote Originally Posted by rpiskac View Post
    Yea, go with the easy answer. The old corrupted binaries and hardware issue.
    It's visibly crashing while downloading packages. The odds of a hardware issue are very high, imho. Can you run a memory tester? Or prime95 in test mode?

  4. #14
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,047
    Blog Entries
    14

    Default Re: Ciore dump on zypper update

    Try this:
    Code:
    zypper clean
    zypper ref
    and post the output here

    And please post output of
    Code:
    df -h
    And please post this between CODE tags, the # in the editor. Use Ctrl-Shift-V to paste, so that these colors that make things unreadable on a light background.

    We need to find out if you're not running in to a corrupted zypper cache, or a full filesystem.

    To find out if it's not a hardware problem, you could create a Live USB stick, and see if zypper segfaults inthere too.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #15

    Default Re: Ciore dump on zypper update

    looks like an issue with the encryption library on my server.


    The following product is going to be upgraded:
    openSUSE Tumbleweed 20180804-0 -> 20190201-0


    The following 5 packages are going to be downgraded:
    fonttosfnt 1.0.5+20170126.aead36f-1.6 -> 1.0.5-1.3
    libKF5Syndication5 18.04.3-1.1 -> 5.54.0-1.1
    libwayland-egl1 18.1.4-203.1 -> 1.16.0-3.2
    python2-backports 4.0.0-3.1 -> 1.0.0-1.2
    rpmdevtools 8.10-9.d_t.2 -> 8.10-3.2


    The following 2 packages are going to change architecture:
    python3-javapackages 5.2.0+git20180620.70fa2258-1.1 -> 5.3.0-2.2 x86_64 -> noarch
    xorg-x11-libX11-ccache 7.6-20.6 -> 7.6-21.2 noarch -> x86_64


    The following package is going to change vendor:
    rpmdevtools 8.10-9.d_t.2 -> 8.10-3.2 obs://build.opensuse.org/devel:tools -> openSUSE


    3649 packages to upgrade, 5 to downgrade, 101 new, 58 to remove, 1 to change vendor, 2 to change arch.
    Overall download size: 2.38 GiB. Already cached: 2.7 MiB. After the operation, additional 987.8 MiB will be used.
    Continue? [y/n/...? shows all options] (y): y
    Detaching after fork from child process 7307.
    /usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
    /usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
    Do you agree with the terms of the license? [yes/no] (no): yes
    Detaching after fork from child process 7317.
    /usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
    /usr/bin/file: error while loading shared libraries: libmagic.so.1: failed to map segment from shared object
    Do you agree with the terms of the license? [yes/no] (no): yes
    Detaching after fork from child process 7327.
    committing
    Detaching after fork from child process 7329.
    Detaching after fork from child process 7331.
    Detaching after fork from child process 7333.
    In cache AdobeICCProfiles-2.0-155.14.noarch.rpm (1/3755), 2.5 MiB ( 5.4 MiB unpacked)
    In cache GeoIP-data-1.6.12-2.2.noarch.rpm (2/3755), 13.0 KiB ( 0 B unpacked)
    In cache Mesa-KHR-devel-18.3.1-210.2.x86_64.rpm (3/3755), 118.5 KiB ( 10.0 KiB unpacked)
    In cache MozillaFirefox-branding-openSUSE-45-4.2.x86_64.rpm (4/3755), 12.2 KiB ( 8.4 KiB unpacked)
    In cache akonadi-mime-18.12.1-1.1.x86_64.rpm (5/3755), 29.3 KiB ( 46.6 KiB unpacked)
    Retrieving package alsa-docs-1.1.8-1.1.noarch (6/3755), 822.4 KiB ( 13.0 MiB unpacked)
    Retrieving: media ..........................................................................................................................................................................................................................[done]
    Retrieving: alsa-docs-1.1.8-1.1.noarch.rpm ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[starting]Detaching after fork from child process 7337.
    Detaching after fork from child process 7338.
    Detaching after fork from child process 7339.
    Detaching after fork from child process 7340.
    Detaching after fork from child process 7341.


    Program received signal SIGSEGV, Segmentation fault.
    0x00007ffff57cf2b0 in X509_get_subject_name () from /usr/local/lib64/libcrypto.so.1.1

  6. #16
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,224
    Blog Entries
    15

    Default Re: Ciore dump on zypper update

    Hi
    That would be likely due to the long delay between upgrading.... 20180804-0 ==>>> 20190201-0
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #17

    Default Re: Ciore dump on zypper update

    I question some of the replies in this thread....

    I have been trying about once a month to update my Tumbleweed install and today it finally worked. Have I done something, No. This happened once before but it took about 6 months for it to start working again.

    First reported problem date: 20-Sep-2018
    Working date: 30-Nov-2019

    just tried zipper dup --no-recommends

    and it updated.

    Thank you to who ever fixed my issue, out there in tumbleweed land!!!!!!!!!!!!!!!

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •