libc problems after Debian update

Comments

• MassNodes Member

  February 2014

  Just remove it and install libc6-i686
• MassNodes Member

  February 2014

  Be careful though, my friend had the same issue and he ended up re-installing his system.
• black Member

  February 2014

  @MassNodes said:
  Be careful though, my friend had the same issue and he ended up re-installing his system.

  I did remove it, but once you do, everything breaks. It's really strange because I have identical setups and some are fine
• MassNodes Member

  February 2014 edited February 2014

  I would google it Did you try to install multi-lib?
• black Member

  February 2014 edited February 2014

  @MassNodes said:
  I would google it Did you try to install multi-lib?

  I tried everything on Google within the first 2 search page results. Some say it's a kernel issue and in openvz, I don't have my own kernel so I can't do anything. Then again, that doesn't make much sense because other ovz containers are just fine. Some say it's something in the sources.list file, which also doesn't make sense either because I have identical setups on other machines and they work fine.
• sleddog Member

  February 2014

  Did you find this: http://serverfault.com/questions/486254/cant-upgrade-libc6

  See the first answer....

  Thanked by 1black
• black Member

  February 2014

  @sleddog said:
  Did you find this: http://serverfault.com/questions/486254/cant-upgrade-libc6

  See the first answer....

  Nope I didn't. Maybe because I put wheezy in the search terms.
  

  This does seem to work though, thanks a lot!
  
• mikho Member

  February 2014

  There is a post about this on the lowendspirit forums, think Nyr gave a solution that worked.

  http://forum.lowendspirit.com/viewtopic.php?id=721

  Thanked by 1trexos
• trexos Member

  February 2014

  Can you post your solution? I tried this from nyr:
  dpkg-deb -c /var/cache/apt/archives/libc6_2.13-38+deb7u1_i386.deb | awk {'print $6'} | cut -f2- -d. | sed 's|^/$|/.|' | sed 's|/$||' > /var/lib/dpkg/info/libc6:i386.list

  But it doesn't work.
• rubik Member

  February 2014 edited February 2014

  @trexos said:
  Can you post your solution? I tried this from nyr:
  dpkg-deb -c /var/cache/apt/archives/libc6_2.13-38+deb7u1_i386.deb | awk {'print $6'} | cut -f2- -d. | sed 's|^/$|/.|' | sed 's|/$||' > /var/lib/dpkg/info/libc6:i386.list

  But it doesn't work.

  Are you on 64-bit Debian by any chance? (EDIT: I think you are, just saw your LES post...)

  If yes, your command should be this:

  dpkg-deb -c /var/cache/apt/archives/libc6_2.13-38+deb7u1_amd64.deb | awk {'print $6'} | cut -f2- -d. | sed 's|^/$|/.|' | sed 's|/$||' > /var/lib/dpkg/info/libc6:amd64.list
  

  Followed by forcing an upgrade:

  apt-get upgrade -f
  

  Worked for me, at least... (I also posted in that LES thread)

  Thanked by 2trexos aMunster
• trexos Member

  February 2014 edited February 2014

  @rubik

  Thank you so much, it worked great. This is my only LES box where I use x64. Forgot it^^

  Btw can somebody explan me what this command does and what the problem was?
• rds100 Member

  February 2014

  None of the VPSes i upgraded showed such problem. This must be some problem specific to your installation or to the template used for your VPS.
• MitchellRobert Member

  February 2014

  @black said:
  I did remove it, but once you do, everything breaks. It's really strange because I have identical setups and some are fine

  Because even the bash terminal you're in depends on it as a shared library...
• black Member

  February 2014 edited February 2014

  @MitchellRobert said:
  Because even the bash terminal you're in depends on it as a shared library...

  That's correct. I didn't know about LD_PRELOAD variable in bash. I guess you learn something new everyday
• Ishaq Member

  February 2014

  I've had this problem recently, this should fix it:

  apt-get -f install libc6-i686
• Ishaq Member

  February 2014

  And yes it's something to do with the kernel and libc. Is it on RHEL5?
• typh0n Member

  February 2014

  @black
  I'm curious about this. Did you encounter this error with a Prometeus VPS?
• black Member

  February 2014

  @typh0n said:
  black
  I'm curious about this. Did you encounter this error with a Prometeus VPS?

  No. They're all openvz containers, but even on identical setups, one has this problem and the other one doesn't so the host shouldn't matter.
• CharlesA Member

  February 2014

  That's so strange. At least you were able to find a fix for it, but the strange part is it affected some machines but not the others even on identical setups.
• IceCream Member

  February 2014

  Had the issue too. Thanks rubik for the solution. Anyway, http://howfuckedismydistro.com/debian/
• sleddog Member

  February 2014

  As I understand it, there was a bugged Debian/Ubuntu package released sometime March/April 2013, which later got fixed.

  Thanked by 1Mark_R
• rubik Member

  February 2014 edited February 2014

  I think some Debian 7 (minimal?) templates are messed up (or more messed up than others?)

  I am running Debian 7 x64 (all installed from minimal templates) on 3 VPS instances with 3 different providers and only had this issue happen with one of the three.

  No big deal, the fix was easy enough. /shrug

  EDIT: Actually, now that I think about it, I think the instance that puked on me started out as a Debian 6 x64 minimal install (there was no Debian 7 template available). I then updated the apt sources to point to Debian 7 and did a dist-upgrade which brought me to Debian 7.3, which was current up until the other day when 7.4 came out. Only THEN I started getting the libc errors (upgradeing from 7.3 to 7.4).
• typh0n Member

  February 2014

  I also had the problem with Debian 7 minimal x86.
• MassNodes Member

  February 2014

  I can sewer that this happened in Debian 6 too.
• aMunster Member

  February 2014

  I had this same problem with debian 7 minimal x64 at ramnode. Nyr's oneliner was magic!