Results 1 to 7 of 7

Thread: zypper => not found ?!

  1. #1

    Default zypper => not found ?!

    I have two machines that have OpenSuSE 11.3 (64-bit) loaded on them.

    On one machine zypper stopped working yesterday, on the other zypper works fine.

    Both machines are being updated with patches 4 times per day via zypper via...
    (zypper --non-interactive refresh; zypper --non-interactive update --auto-agree-with-licenses --skip-interactive )

    Here is what I have.....

    # which zypper

    Both machines have the file /usr/bin/zypper which has the same md5 signature on both machines...
    a91b6a3cfbee351f962de8190281b1ff /usr/bin/zypper

    The directory information on both files looks exactly the same...
    -rwxr-xr-x 1 root root 1506752 2010-11-16 19:41 /usr/bin/zypper

    However, on one of the machines zypper does not run but gives the error....
    # zypper
    zypper: error while loading shared libraries: cannot open shared object file: No such file or directory

    I did a 'ldd' on both zypper files. On the machine where zypper works the output is....
    # ldd `which zypper` => (0x00007fff3c74e000) => /usr/lib64/ (0x00007f477d08c000) => /lib64/ (0x00007f477ce45000) => /usr/lib64/ (0x00007f477cc0b000) => /usr/lib64/ (0x00007f477c901000) => /lib64/ (0x00007f477c6aa000) => /lib64/ (0x00007f477c494000) => /lib64/ (0x00007f477c134000) => /lib64/ (0x00007f477bf17000) => /lib64/ (0x00007f477bd0e000) => /lib64/ (0x00007f477bb0b000) => /usr/lib64/ (0x00007f477b7cb000) => /usr/lib64/ (0x00007f477b575000) => /usr/lib64/ (0x00007f477b21f000) => /lib64/ (0x00007f477b009000) => /lib64/ (0x00007f477addf000) => /lib64/ (0x00007f477aa30000) => /lib64/ (0x00007f477a822000) => /lib64/ (0x00007f477a5cd000) => /usr/lib64/ (0x00007f477a3c0000)
    /lib64/ (0x00007f477d743000) => /usr/lib64/ (0x00007f477a16c000) => /usr/lib64/ (0x00007f4779f3b000) => /lib64/ (0x00007f4779d31000) => /lib64/ (0x00007f4779b12000) => /usr/lib64/ (0x00007f47798df000) => /usr/lib64/ (0x00007f4779698000) => /usr/lib64/ (0x00007f4779462000) => /lib64/ (0x00007f4779206000) => /usr/lib64/ (0x00007f4778fdf000) => /lib64/ (0x00007f4778ddb000) => /lib64/ (0x00007f4778bcc000) => /usr/lib64/ (0x00007f47789b7000) => /lib64/ (0x00007f4778795000) => /usr/lib64/ (0x00007f4778586000) => /lib64/ (0x00007f477836f000) => /usr/lib64/ (0x00007f4778154000) => /usr/lib64/ (0x00007f4777e89000) => /usr/lib64/ (0x00007f4777c62000) => /lib64/ (0x00007f4777a5e000) => /usr/lib64/ (0x00007f4777855000) => /lib64/ (0x00007f4777652000)

    On the machine where zypper does NOT work the output is.....
    # ldd `which zypper` => (0x00007fffd5111000) => /usr/lib64/ (0x00007fd385686000) => /lib64/ (0x00007fd38543f000) => /usr/lib64/ (0x00007fd385205000) => /usr/lib64/ (0x00007fd384efb000) => /lib64/ (0x00007fd384ca4000) => /lib64/ (0x00007fd384a8e000) => /lib64/ (0x00007fd38472e000) => /lib64/ (0x00007fd384511000) => /lib64/ (0x00007fd384308000) => /lib64/ (0x00007fd384105000) => /usr/lib64/ (0x00007fd383dc5000) => /usr/lib64/ (0x00007fd383b6f000) => /usr/lib64/ (0x00007fd383819000) => /lib64/ (0x00007fd383603000) => /lib64/ (0x00007fd3833d9000) => /lib64/ (0x00007fd38302a000) => /lib64/ (0x00007fd382e1c000) => /lib64/ (0x00007fd382bc7000) => /usr/lib64/ (0x00007fd3829ba000)
    /lib64/ (0x00007fd385d3d000) => /usr/lib64/ (0x00007fd382766000) => /usr/lib64/ (0x00007fd382535000) => /lib64/ (0x00007fd38232b000) => /lib64/ (0x00007fd38210c000) => /usr/lib64/ (0x00007fd381ed9000) => /usr/lib64/ (0x00007fd381c92000) => /usr/lib64/ (0x00007fd381a5c000) => /lib64/ (0x00007fd381800000) => /lib64/ (0x00007fd385e18000) => /lib64/ (0x00007fd3815fc000) => /lib64/ (0x00007fd3813ed000) => /usr/lib64/ (0x00007fd3811d8000) => /lib64/ (0x00007fd380fb6000) => /usr/lib64/ (0x00007fd380da7000) => /lib64/ (0x00007fd380b90000) => /usr/lib64/ (0x00007fd380975000) => /usr/lib64/ (0x00007fd3806aa000) => /usr/lib64/ (0x00007fd380483000) => /lib64/ (0x00007fd38027f000) => /usr/lib64/ (0x00007fd380076000) => not found => /lib64/ (0x00007fd37fe73000)

    In both cases they appear to be the same with the exception of the additional libcrypto on the machine that does not work. Interestingly enough the ldd of the one that does NOT work has references to two libcrypto's.

    I also did an 'md5sum' on all of the libraries above on both of the machines and found that the md5s of all libraries on both machines are the same.

    Can someone please let me know what has happened. Could it be that a zypper package install did not complete on the one machine, and I need to run "ldconfig" as root on the machine that is broken?? Is there another problem???

    Thank you so much!


  2. #2
    Join Date
    Jun 2008
    Groningen, Netherlands
    Blog Entries

    Default Re: zypper => not found ?!

    Is GoogleEarth installed on either one of them?
    - Athlon X6 3.6 GHz, 16 GB DDR3, 30 GB SSD, 3 TB of disks, GT540, openSUSE 12.2 x86_64 + KDE 4.10 + GNOME 3
    - ASUS A73SD, Intel + GT610M Optimus, 6 GB, 120 GB SSD, openSUSE Tumbleweed

    Anything that can go wrong.... will teach us

  3. #3

    Default Re: zypper => not found ?!

    No. They are both servers with minimal X-11. There are NO toolkits like gtk+ installed.

    It is also the case that yast2 does not work. I looked at the log. If it matters to anyone I will post it.

    Any hint of what might be going on here would be greatly appreciated.

    Again both machines are 64-bit opensuse 11.3, both zypper binaries have the same md5s, all of the shared objects also have the same md5s. ldd shows one extra 'missing' shared library. It's curious that the library that it shows missing is a 32-bit library. But clearly all other libraries are 64-bit.

  4. #4

    Default Re: zypper => not found ?!

    Can someone suggest a better forum to post something like this on?

    Thank you much in advance.


  5. #5

    Default Re: zypper => not found ?!

    Since yast2 no longer works on one of these machines, I looked at the y2log. The logs are the same until this point....

    Machine where it works....
    2011-08-11 12:58:33 <1> crisma2(15971) [Pkg] Redirecting ZYPP log to y2log

    Machine where it does not work...
    2011-08-11 12:25:54 <3> crisma3(15227) [liby2] error loading plugin /usr/lib64\
    /YaST2/plugin/ cannot open shared object file: No such file or directory
    2011-08-11 12:25:54 <3> crisma3(15227) [liby2] error loading plugin /usr/lib64\
    /YaST2/plugin/ cannot open shared object file: No such file or directory
    2011-08-11 12:25:54 <3> crisma3(15227) [Interpreter] clients/sw_single.ycp:25 Loading module 'Pkg' failed
    2011-08-11 12:25:54 <3> crisma3(15227) [libycp] No matching component found
    2011-08-11 12:25:54 <3> crisma3(15227) [Interpreter] clients/sw_single.ycp:25 Import 'Pkg' failed...
    2011-08-11 12:25:54 <3> crisma3(15227) [Interpreter] clients/sw_single.ycp:25 Could not create its namespace
    2011-08-11 12:25:54 <3> crisma3(15227) [libycp] Caught invalid bytecode in '/usr/share/Y\
    2011-08-11 12:25:54 <3> crisma3(15227) [Interpreter] clients/sw_single.ycp:25 Loading module 'PackageCallbacks' fai\
    2011-08-11 12:25:54 <3> crisma3(15227) [Parser] clients/sw_single.ycp:25 Can't load module 'PackageCallbacks'.

    For "/usr/lib64/YaST2/plugin/", the md5s are the same on both machines, and "ldd" of both showed one additional "not found" shared object' on the one that did not work. Otherwise all shared objects were the same.

  6. #6

    Default Re: zypper => not found ?!

    Somehow, the 64-bit version of "" got uninstalled. I did a...

    # wget
    # rpm -i libopenssl0_9_8-0.9.8m-3.3.2.x86_64.rpm
    # SuSEconfig
    # ldconfig

    And it works again!

  7. #7

    Default Re: zypper => not found ?!

    and so this works. However....

    could someone please explain to me why two identical binaries on different machines would have identical shared library dependencies except for one additional library? My understanding was that programs are compiled and linked against specific shared objects. So this should not be?!

    Thank you in advance!

Posting Permissions

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