2.2 and bind package: libz.so.5


  • Hi all,

    I upgraded my pfSense firewall 2.1.2 to the latest 2.2 release. Unfortunately, my installed bind package does not run any more. :o
    Logfile says:

    
    php-fpm[82338]: /rc.start_packages: The command '/usr/local/etc/rc.d/named.sh restart' returned exit code '1', the output was 'Shared object "libz.so.5" not found, required by "named"'
    
    ```:-[
    Anyone having an idea if there is an updated bind package available? Or how I can re-enable my bind? ???
  • Banned


  • Hi doktornotor,

    indeed, it is a full install. Sorry, I tried to search for libz.so.5 and pfSense but did not get any useful results.

    So it appears it is a known issue?
    There is a fix created, but not yet released?
    On my system it looks like the following:

    
    [2.2-RELEASE][root@pfsense2.evs-nb.de]/usr/lib: ls -al| grep libz
    -r--r--r--   1 root  wheel    93028 Jan 22 22:07 libz.a
    lrwxr-xr-x   1 root  wheel       14 Feb  8 11:49 libz.so -> /lib/libz.so.5
    -r--r--r--   1 root  wheel   328020 Jan 22 22:07 libzfs.a
    lrwxr-xr-x   1 root  wheel       16 Jan 22 22:07 libzfs.so -> /lib/libzfs.so.2
    -r--r--r--   1 root  wheel    13964 Jan 22 22:07 libzfs_core.a
    lrwxr-xr-x   1 root  wheel       21 Jan 22 22:07 libzfs_core.so -> /lib/libzfs_core.so.2
    -r--r--r--   1 root  wheel  5863836 Jan 22 22:07 libzpool.a
    lrwxr-xr-x   1 root  wheel       18 Jan 22 22:07 libzpool.so -> /lib/libzpool.so.2
    
    

    I read your other post:

    ln /lib/libz.so.6 /lib/libz.so.5
    

    Uh no, this is completely wrong "fix".

    You are fixing the wrong thing! That .5 vs .6 actually has a meaning - the new version of the library does not have a backward-compatible ABI! If you want to fix something, then fix the dead /usr/lib/*.so symlinks so that they point to proper file. Don't create "compatibility" symlinks pretending a deliberately removed outdated ABI library is still there.

    So I do not see any valid version of libz.so! Should I re-install bind? Will this cause any issues with the broken libraries?

    Or when is a fix available for this? Read: When will 2.2.1 be released?

  • Banned

    @knebb:

    Or when is a fix available for this? Read: When will 2.2.1 be released?

    When it's ready… :D If you want to fix something manually, then fix the broken /usr/lib/libz.so symlink so that it points to /lib/libz.so.6; certainly do not symlink /lib/libz.so.5 to /lib/libz.so.6


  • @doktornotor:

    @knebb:

    Or when is a fix available for this? Read: When will 2.2.1 be released?

    When it's ready… :D

    Why did I expect such an answer?  ;) ;D ;

    If you want to fix something manually, then fix the broken /usr/lib symlink, certainly do not symlink /lib/libz.so.5 to /lib/libz.so.6

    Of course not. So I re-create the /usr/lib/libz.so to point to /lib/libz.so.6? I did so, but the error still exists:

    
    php-fpm[4281]: /pkg_edit.php: The command '/usr/local/etc/rc.d/named.sh restart' returned exit code '1', the output was 'Shared object "libz.so.5" not found, required by "named"'
    

    Any further ideas?

  • Banned

    No. Not interested in debugging PBI frenzy. Maybe uninstall, reboot, reinstall will fix it. No idea. PBI suxxx goats nuts.


  • @doktornotor:

    No. Not interested in debugging PBI frenzy. Maybe uninstall, reboot, reinstall will fix it. No idea. PBI suxxx goats nuts.

    :o ;D
    Got it! No worries- thanks for your help anyways. Tried to reinstall but got an error of not being able to install bind.
    Fiddled out it came due to no DNS resolver running any longer.  :P

    Now re-installed bind and it appears to be running fine. Just wondering as there is now no symlink libz.so.5 nor libz.so anywhere…

  • Banned

    @knebb:

    Just wondering as there is now no symlink libz.so.5 nor libz.so anywhere…

    Well yes, that is the point! It does NOT need libz.so.5. It gets moaning about that one since the linker symlink under /usr/lib points to the non-existent deprecated library version. (If you look into /usr/pbi, the PBI thing somehow creates its own directory structure for each package under /usr/pbi/<packagename-$arch>/local, and redirects the calls and produces its own symlinks copies there. So, just removing/fixing the broken symlink under /usr/lib is not enough. You need to nuke and reinstall the package as well.

    At least that's my understanding of these stupid issues, I hate the PBI thing with passion and pretty sure at least some of the few remaining package maintainers are of the same opinion.</packagename-$arch>