Find the answer to your Linux question:
Results 1 to 4 of 4
Hi All-- I 'accidentally' deleted /lib64/libz.so.1 on my F17 64-bit Dell a couple of weeks ago. To repair, I booted the machine from a live F17_64 CD, and copied libz.so.1 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2008
    Posts
    7

    F17_64: deleted then replaced libz.so.1 --> ok *but*


    Hi All--

    I 'accidentally' deleted /lib64/libz.so.1 on my F17 64-bit Dell a couple of weeks ago.

    To repair, I booted the machine from a live F17_64 CD, and copied libz.so.1 from the CD into the host's /lib64

    After reboot, everything works fine, except:

    when I install a package, or update the system, I get warnings

    Code:
    /lib64/libz.so.1 is not a symbolic link
    here's the output of ls -l /lib64/libz.*

    Code:
    lrwxrwxrwx. 1 root root    25 Dec 24 15:30 /lib64/libz.so -> ../../lib64/libz.so.1.2.5
    -rwxr-xr-x. 1 root root 96264 Mar 24 17:22 /lib64/libz.so.1
    -rwxr-xr-x. 1 root root 93824 Mar 24 17:22 /lib64/libz.so.1.2.5
    My question: Where do I go from here??? Do I replace my /lib64/libz.so.1 with a soft link to ../../lib64/libz.so.1.2.5, or do something else?

    I'm aware that in this case, being close will not win me a cigar. Can anyone help?

    Thanks in advance...

  2. #2
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    On my F17 box I have:
    Code:
    $ ls -l /lib/libz.*
    lrwxrwxrwx. 1 root root    13 Nov 22 18:20 /lib/libz.so.1 -> libz.so.1.2.5
    -rwxr-xr-x. 1 root root 85772 Aug  2  2012 /lib/libz.so.1.2.5
    so perhaps you could manually fix it (as root) like:
    Code:
    cd /lib64
    rm -f libz.so.1
    ln -s libz.so.1.2.5 libz.so.1
    rm -f /etc/ld.so.cache
    ldconfig
    but personally, i would just try to reinstall it and let rpm handle things:
    Code:
    rpm -e --justdb --nodeps zlib
    yum install zlib

  3. #3
    Just Joined!
    Join Date
    Jun 2008
    Posts
    7
    Whew! Thanks so much, Atreyu!

    I chose door number 2, the reinstall via rpm and yum. yum installed zlib fine, but with a warning:

    Code:
    Warning: RPMDB altered outside of yum.
    ** Found 209 pre-existing rpmdb problem(s), 'yum check' output follows:
    ImageMagick-6.7.5.6-4.fc17.x86_64 has missing requires of libz.so.1()(64bit)
    --- snip ---

    followed by 208 more problems.

    After the install, I ran 'yum check' and came up clean.

    I guess that each install and update was introducing errors, and sooner or later the system would have died. I *really* appreciate your help.

  4. #4
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    no worries, glad you got it sorted.

Posting Permissions

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