Bug#759530: libc-bin: ldconfig breaks a system
Hi, Could this bug be caused by a corrupt aux-cache[1] (possibly, in addition to a corrupt ld.so.cache)? A bit of google searching suggests that a broken aux-cache can cause ldconfig to seg. fault. With the ld.so.cache itself being corrupt (or sufficiently outdated?), both ldconfig and most other binaries would simply just seg. fault fitting the symptoms pretty well so far. It partly also fits with the removal of libjasper1, as the removed library would force ldconfig to *not* use its cache for said library. Though I cannot explain why it seems like stat itself seg. faults. Assuming my hypothesis is correct, a broken system could be restored by running[2]: $ ldconfig.real --ignore-aux-cache Failling that: $ /var/cache/ldconfig/aux-cache $ ldconfig.real Maybe take a copy of the aux-cache before doing the restore command(s). This way we should be able to re-break the system by re-instating the old aux-cache (and possibly breaking the ld.so.cache). Thanks, ~Niels [1] /var/cache/ldconfig/aux-cache [2] Using ldconfig.real in case /bin/sh got borked by the ld.so.cache as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759530: libc-bin: ldconfig breaks a system
Package: libc-bin
Version: 2.19-11
Followup-For: Bug #759530
Hello!
Something similar happened to me (after upgrade to 2.19-11). If this
report wasn't on top of libc-bin and absolutely recent, I would not have
said a word: read on!
Foundation-laying: the scenario. All packages that call ldconfig in their
install scripts started sputtering like this one:
Setting up golang (2:1.3.2-1) ...
Processing triggers for libc-bin (2.19-11) ...
Segmentation fault
/sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once
/usr/lib/x86_64-linux-gnu/libfakeroot:
libfakeroot-0.so - libfakeroot-tcp.so
/usr/local/lib:
/lib/x86_64-linux-gnu:
libthread_db.so.1 - libthread_db-1.0.so
[...]
libglib-2.0.so.0 - libglib-2.0.so.0.4200.0
/usr/lib/x86_64-linux-gnu:
Segmentation fault
dpkg: error processing package libc-bin (--configure):
subprocess installed post-installation script returned error exit status 139
Errors were encountered while processing:
libc-bin
Hu? ldconfig dies like this (strace):
[natural-looking output]
stat(/usr/lib/x86_64-linux-gnu/libQtScript.so.4, {st_mode=S_IFREG|0644,
st_size=2692504, ...}) = 0
stat(/usr/lib/x86_64-linux-gnu/libjasper.so.1, unfinished ...
+++ killed by SIGSEGV +++
Segmentation fault
Oh?
# file /usr/lib/x86_64-linux-gnu/libjasper.so.1
Segmentation fault
Drastic measures (wtf?):
# ls !$
ls /usr/lib/x86_64-linux-gnu/libjasper.so.1
Segmentation fault
# rm /usr/lib/x86_64-linux-gnu/libjasper.so.1
Segmentation fault
# unlink !$
unlink /usr/lib/x86_64-linux-gnu/libjasper.so.1
# ls /usr/lib/x86_64-linux-gnu/libjasper.so.1
ls: cannot access /usr/lib/x86_64-linux-gnu/libjasper.so.1: No such file or
directory
Done (reinstall libjasper1).
Now, ordinarily, I'd say: severe FS corruption, something or other.
But, with this report on top, perhaps there's something deeper going on.
No idea.
Note: I now have no way of returning to the broken state.
I doubt anyone can profit from this, but I had to throw it in (as I
already mentioned).
Such is my tale of woe.
Regards,
Hagen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759530: libc-bin: ldconfig breaks a system
Aurelien Jarno aurel...@aurel32.net writes: On Thu, Aug 28, 2014 at 10:07:57AM +0400, Dmitrii Kashin wrote: Package: libc-bin Version: 2.19-9 Severity: grave File: /sbin/ldconfig Dear Maintainer, I had an upgrade of libc6 and libc-bin packages up to the version 2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the begin it seemed as a usual upgrade but after a while (supposedly after these two packages) an upgrade was interrupted showing numerous segmentation fault errors. Then almost for every command in shell I got segmentation fault. I was surprised. I tried to log into another tty, but failed. Then I tried to reboot... And got a kernel panic after 2 seconds of system bootstrap. I took a livecd. I failed to chroot (got the same segfault problem). I supposed that I had some problems with libc6, so I took a package libc6_2.19-9_amd64.deb from /var/cache/apt/archives and unpacked it into the root mount point via `dpkg-deb -x pkg'. After that I managed to chroot into the system. I tried to finish an upgrade process, but I got the same faults. I put here inline the first lines of `apt-get upgrade' output: # apt-get upgrade Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: alsa-base libabw-0.0-0 libcdr-0.0-0 libe-book-0.0-0 libetonyek-0.0-0 libfreehand-0.0-0 libgeoclue0 libmspub-0.0-0 libmwaw-0.2-2 libodfgen-0.0-0 liborcus-0.6-0 libvisio-0.0-0 libwpd-0.9-9 libwpg-0.2-2 libwps-0.2-2 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 108 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up liblcms2-2:i386 (2.6-3) ... Setting up libmbim-glib0:amd64 (1.8.0-1) ... dpkg: error processing package libmbim-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmm-glib0:amd64 (1.2.0-1) ... dpkg: error processing package libmm-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmng1:i386 (1.0.10+dfsg-3.1) ... ... After it I had to unpack libc6 package again. Then I looked intently at the first package with problems (libmbim-glib0). I unpacked it and saw in the postinst script the command `ldconfig'. After a while I realized that segfaults happen after and only after execution of `ldconfig'. I managed with the problem by downgrading libc6 and libc-bin (amd64 and i386 versions both, because I'm using multiarch) back to the version 2.19-4 from the apt cache. For me it looks like the ld.so symlink is overriden when running ldconfig, a bug which is supposed to be fixed months ago. Can you please give me the list of libc packages installed on your system by running the dpkg -l libc* command? Also what is the output of which ldconfig? Sorry for being a little bit late. I had a great pile of work. This information could be useful: freehck@nb-mita3:~% apt-mark showhold libc-bin libc6 libc6-i686:i386 libc6:i386 freehck@nb-mita3:~% apt-cache policy libc6 libc-bin libc6: Installed: 2.19-4 Candidate: 2.19-9 Version table: 2.19-9 0 500 http://mirror.yandex.ru/debian/ jessie/main amd64 Packages *** 2.19-4 0 100 /var/lib/dpkg/status 2.13-38+deb7u2 0 1 http://mirror.yandex.ru/debian/ wheezy/main amd64 Packages 2.11.3-4 0 1 http://mirror.yandex.ru/debian/ squeeze/main amd64 Packages libc-bin: Installed: 2.19-4 Candidate: 2.19-9 Version table: 2.19-9 0 500 http://mirror.yandex.ru/debian/ jessie/main amd64 Packages *** 2.19-4 0 100 /var/lib/dpkg/status 2.13-38+deb7u2 0 1 http://mirror.yandex.ru/debian/ wheezy/main amd64 Packages 2.11.3-4 0 1 http://mirror.yandex.ru/debian/ squeeze/main amd64 Packages # I understand it's more then you need, but you have asked to grep by # `libc*' pattern. =/ freehck@nb-mita3:~% dpkg -l libc\* | grep ^ii ii libcaca0:amd64 0.99.beta19-2amd64colour ASCII art library ii libcairo-gobject2:amd641.12.16-2amd64The Cairo 2D vector graphics library (GObject library) ii libcairo2:amd641.12.16-2amd64The Cairo 2D vector graphics library ii libcanberra0:amd64 0.30-2 amd64simple abstract interface for playing event sounds ii libcap-ng0:amd64 0.7.4-2 amd64An alternate POSIX capabilities library ii libcap2:amd64 1:2.24-4 amd64POSIX 1003.1e capabilities (library) ii libcap2:i386 1:2.24-4 i386 POSIX 1003.1e
Bug#759530: libc-bin: ldconfig breaks a system
Package: libc-bin Version: 2.19-9 Severity: grave File: /sbin/ldconfig Dear Maintainer, I had an upgrade of libc6 and libc-bin packages up to the version 2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the begin it seemed as a usual upgrade but after a while (supposedly after these two packages) an upgrade was interrupted showing numerous segmentation fault errors. Then almost for every command in shell I got segmentation fault. I was surprised. I tried to log into another tty, but failed. Then I tried to reboot... And got a kernel panic after 2 seconds of system bootstrap. I took a livecd. I failed to chroot (got the same segfault problem). I supposed that I had some problems with libc6, so I took a package libc6_2.19-9_amd64.deb from /var/cache/apt/archives and unpacked it into the root mount point via `dpkg-deb -x pkg'. After that I managed to chroot into the system. I tried to finish an upgrade process, but I got the same faults. I put here inline the first lines of `apt-get upgrade' output: # apt-get upgrade Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: alsa-base libabw-0.0-0 libcdr-0.0-0 libe-book-0.0-0 libetonyek-0.0-0 libfreehand-0.0-0 libgeoclue0 libmspub-0.0-0 libmwaw-0.2-2 libodfgen-0.0-0 liborcus-0.6-0 libvisio-0.0-0 libwpd-0.9-9 libwpg-0.2-2 libwps-0.2-2 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 108 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up liblcms2-2:i386 (2.6-3) ... Setting up libmbim-glib0:amd64 (1.8.0-1) ... dpkg: error processing package libmbim-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmm-glib0:amd64 (1.2.0-1) ... dpkg: error processing package libmm-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmng1:i386 (1.0.10+dfsg-3.1) ... ... After it I had to unpack libc6 package again. Then I looked intently at the first package with problems (libmbim-glib0). I unpacked it and saw in the postinst script the command `ldconfig'. After a while I realized that segfaults happen after and only after execution of `ldconfig'. I managed with the problem by downgrading libc6 and libc-bin (amd64 and i386 versions both, because I'm using multiarch) back to the version 2.19-4 from the apt cache. I suppose that there's some problems with caches which ldconfig generates for ld. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'stable'), (1, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc-bin depends on: pn libc6none ii libcap2 1:2.24-4 libc-bin recommends no packages. libc-bin suggests no packages. -- Configuration Files: /etc/gai.conf changed: /etc/ld.so.conf changed: include ld.so.conf.d/*.conf include /etc/ld.so.conf.d/*.conf -- no debconf information pgpwOmUWLSH8b.pgp Description: PGP signature
Bug#759530: libc-bin: ldconfig breaks a system
On Thu, Aug 28, 2014 at 10:07:57AM +0400, Dmitrii Kashin wrote: Package: libc-bin Version: 2.19-9 Severity: grave File: /sbin/ldconfig Dear Maintainer, I had an upgrade of libc6 and libc-bin packages up to the version 2.19-9 from 2.19-4 while executing `apt-get upgrade'. In the begin it seemed as a usual upgrade but after a while (supposedly after these two packages) an upgrade was interrupted showing numerous segmentation fault errors. Then almost for every command in shell I got segmentation fault. I was surprised. I tried to log into another tty, but failed. Then I tried to reboot... And got a kernel panic after 2 seconds of system bootstrap. I took a livecd. I failed to chroot (got the same segfault problem). I supposed that I had some problems with libc6, so I took a package libc6_2.19-9_amd64.deb from /var/cache/apt/archives and unpacked it into the root mount point via `dpkg-deb -x pkg'. After that I managed to chroot into the system. I tried to finish an upgrade process, but I got the same faults. I put here inline the first lines of `apt-get upgrade' output: # apt-get upgrade Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: alsa-base libabw-0.0-0 libcdr-0.0-0 libe-book-0.0-0 libetonyek-0.0-0 libfreehand-0.0-0 libgeoclue0 libmspub-0.0-0 libmwaw-0.2-2 libodfgen-0.0-0 liborcus-0.6-0 libvisio-0.0-0 libwpd-0.9-9 libwpg-0.2-2 libwps-0.2-2 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 108 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up liblcms2-2:i386 (2.6-3) ... Setting up libmbim-glib0:amd64 (1.8.0-1) ... dpkg: error processing package libmbim-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmm-glib0:amd64 (1.2.0-1) ... dpkg: error processing package libmm-glib0:amd64 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up libmng1:i386 (1.0.10+dfsg-3.1) ... ... After it I had to unpack libc6 package again. Then I looked intently at the first package with problems (libmbim-glib0). I unpacked it and saw in the postinst script the command `ldconfig'. After a while I realized that segfaults happen after and only after execution of `ldconfig'. I managed with the problem by downgrading libc6 and libc-bin (amd64 and i386 versions both, because I'm using multiarch) back to the version 2.19-4 from the apt cache. For me it looks like the ld.so symlink is overriden when running ldconfig, a bug which is supposed to be fixed months ago. Can you please give me the list of libc packages installed on your system by running the dpkg -l libc* command? Also what is the output of which ldconfig? -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
