Bug#555205: libc6: segfault when upgrading from 2.9-25 -> 2.10.1-5 on squeeze renders system unusable
On Sun, Nov 08, 2009 at 05:19:42PM -0500, bjn wrote:
> Package: libc6
> Version: 2.9-25
> Severity: critical
> Justification: breaks the whole system
>
>
> I tried to upgrade to the current "testing" version of libc6: 2.10.1-5
>
> Below is the output from aptitude:
>
> -----
> Preparing to replace libc-bin 2.9-25 (using .../libc-bin_2.10.1-5_i386.deb) ...
> Unpacking replacement libc-bin ...
> Processing triggers for man-db ...
> Setting up libc-bin (2.10.1-5) ...
> (Reading database ... 56540 files and directories currently installed.)
> Preparing to replace libc6 2.9-25 (using .../libc6_2.10.1-5_i386.deb) ...
> Checking for services that may need to be restarted...
> Checking init scripts...
> Unpacking replacement libc6 ...
> Setting up libc6 (2.10.1-5) ...
> dpkg: error processing libc6 (--configure):
> subprocess installed post-installation script killed by signal (Segmentation fault)
> Errors were encountered while processing:
> libc6
> E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi'
> E: Sub-process returned an error code
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> -----
This is not the first time someone reported such an error (also on
earlier version), but we have never been able to find the cause of the
problem. Usually reinstalling the machine fixes the problem, which tends
to say it is related to a local change. If you have any idea of such a
change, don't hesitate to tell us.
> I was upgrading this system remotely (bad, yes, I know) and could no
> longer enter any commands. Every command would return a "segmentation
> fault."
You can install busybox-static on such a machine, it can help in such
situations.
> Rebooting the system did not help either. I ultimately had to boot into
> another OS and copy back the files from version 2.9-25 in order to have
> a usable system.
>
> I can try to provide additional details if necessary.
Given I have no idea what can cause this problem, let me ask a few
(more or less random) questions that can help solving the issue:
- Are you using SELinux?
- Do you have any message related to the issue in dmesg/system log? A
log of the crash or a filesystem corruption for example.
- What's the output of 'cat /proc/cpuinfo'?
- What's the output of 'find /lib'?
- What's the output of 'ldd /bin/ls'
- Have you changed something in the pam configuration?
That's all that comes to mind for now ;-)
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: