[opensuse] Weird error after zypper dup: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Hello, I've just updated my server from 42.3 to Lead 15.0. Most stuff works fine but I'm seeing these errors in /var/log/zypp/history: # 2019-03-03 11:24:25 system-user-wwwrun-20170617-lp150.3.34.noarch.rpm installed ok [...] # nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link 2019-03-03 11:24:25|install|system-user-wwwrun|20170617-lp150.3.34|noarch||repo-oss|736861021fd7782938b3b00f5fc82539140c751e8a09fc5ad121f186ef25d89e| # 2019-03-03 11:24:25 system-user-nobody-20170617-lp150.3.34.noarch.rpm installed ok [...] # nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link Also when starting privoxy, I get: /usr/sbin/privoxy: relocation error: /lib64/libnss_dns.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Google tells me this happens when I have two versions of libc installed but that doesn't seem to be the case: # /sbin/ldconfig -v | grep libc.so /lib libc.so.6 -> libc-2.26.so /lib64 libc.so.6 -> libc-2.26.so The RPM package glibc has no modifed files: # rpm -V glibc # I'm stumped what could cause this error. Any ideas? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04.03.19 um 22:20 schrieb Aaron Digulla: Update: I found the source of the privoxy problem: When the service is started, the pre-start steps in /usr/lib/systemd/system/privoxy.service will copy two libraries into ~privoxy/lib64/ *if they don't exist*. I had started the service before the update, so the files existed. They were from the previous version of glibc. *sigh*. Fix: mv ~privoxy/lib64/ ~privoxy/lib64.bak/ mkdir ~privoxy/lib64/ systemctl stop privoxy.service systemctl start privoxy.service and it works again. Which just leaves nscd. Looking at the log, nscd was updated very late in the upgrade. After installing the new nscd, I saw no more errors (but also no calls to nscd). Running nscd manually showed no error. My guess is that the update processes tried to use the old version after glibc had already been updated. Maybe that points to a bug in the upgrade process: Packages should be installed in the order of dependencies (i.e. an installatio should only happen after all dependencies have been updated). Regards,
Hello,
I've just updated my server from 42.3 to Lead 15.0. Most stuff works fine but I'm seeing these errors in /var/log/zypp/history:
# 2019-03-03 11:24:25 system-user-wwwrun-20170617-lp150.3.34.noarch.rpm installed ok [...] # nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link 2019-03-03 11:24:25|install|system-user-wwwrun|20170617-lp150.3.34|noarch||repo-oss|736861021fd7782938b3b00f5fc82539140c751e8a09fc5ad121f186ef25d89e| # 2019-03-03 11:24:25 system-user-nobody-20170617-lp150.3.34.noarch.rpm installed ok [...] # nscd: relocation error: nscd: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link
Also when starting privoxy, I get:
/usr/sbin/privoxy: relocation error: /lib64/libnss_dns.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Google tells me this happens when I have two versions of libc installed but that doesn't seem to be the case:
# /sbin/ldconfig -v | grep libc.so /lib libc.so.6 -> libc-2.26.so /lib64 libc.so.6 -> libc-2.26.so
The RPM package glibc has no modifed files:
# rpm -V glibc #
I'm stumped what could cause this error. Any ideas?
Regards,
-- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (1)
-
Aaron Digulla