The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

upgrading from CentOS 4.3 -> 4.4 Missing Dependency: glibc-common

Discussion in 'General Discussion' started by jamesbond, Aug 31, 2006.

  1. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    I tried upgrading from CentOS 4.3 to 4.4 but I get this error:

    Code:
    --> Running transaction check
    --> Processing Dependency: libgomp = 4.1.0-18.EL4 for package: gcc4
    --> Processing Dependency: glibc-common = 2.3.4-2.19 for package: glibc-dummy-centos-4
    --> Restarting Dependency Resolution with new changes.
    --> Populating transaction set with selected packages. Please wait.
    ---> Package libgomp.i386 0:4.1.0-18.EL4 set to be updated
    --> Running transaction check
    --> Processing Dependency: glibc-common = 2.3.4-2.19 for package: glibc-dummy-centos-4
    --> Finished Dependency Resolution
    Error: Missing Dependency: glibc-common = 2.3.4-2.19 is needed by package glibc-dummy-centos-4
    
    I tried updating/installing glibc, which didn't work.
     
  2. rachweb

    rachweb Well-Known Member

    Joined:
    Jun 26, 2004
    Messages:
    268
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    amsterdam
    Remove kernel (line exclude) in the yum.conf
     
  3. chilihost

    chilihost Well-Known Member

    Joined:
    Mar 1, 2005
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    this upgrade has been DISASTEROUS. After up2date, I have had to set the cPanel updates to STABLE tree and then to a /scripts/upcp - I believe the problem is CentOS 4.4 installs a new version of Perl which cPanel cannot locate, plus there was heaps of issues with named too.
     
  4. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    I'm trying this on a VPS, I doubt removing the kernel form yum.conf will do any good...
     
  5. rachweb

    rachweb Well-Known Member

    Joined:
    Jun 26, 2004
    Messages:
    268
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    amsterdam
    The problem is that centos 4.4 requires the new kernel version. If you don't want install the new one then you can't upgrade.
     
  6. rachweb

    rachweb Well-Known Member

    Joined:
    Jun 26, 2004
    Messages:
    268
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    amsterdam
    Use yum upgrade instead of up2date -u
     
  7. chilihost

    chilihost Well-Known Member

    Joined:
    Mar 1, 2005
    Messages:
    72
    Likes Received:
    0
    Trophy Points:
    6
    really??? is it that easy...holy cow!!! I am all for that new kernel - I was installing it as a seperate task to be safe. Thanks for the tip, will give it a go right now :)
     
  8. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    Thanks, I was not aware of that.
     
  9. WebScHoLaR

    WebScHoLaR Well-Known Member

    Joined:
    Dec 14, 2005
    Messages:
    511
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    Planet Earth
    Are you on a Virtuozzo VPS?
     
  10. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    Indeed I am.
     
  11. imkite

    imkite Member

    Joined:
    Sep 3, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    add exclude=glibc* to /etc/yum.conf

    had the same problem that fixed it
     
  12. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    Thanks, that worked! Did you remove glibc* from the exclude line after updating to 4.4 or are you leaving it there?
     
  13. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You should leave it there.
     
  14. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    It seems /scripts/upcp removes the glibc* entry at the end of the exclude line for some reason.

    Haven't tried adding exclude=glibc* on a seperate line.
     
  15. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    That's naughty - I'd log a bugzilla entry asking that /scripts/checkyum doesn't strip out any exclusions that you've added yourself.
     
  16. rikgarner

    rikgarner Well-Known Member

    Joined:
    Mar 31, 2006
    Messages:
    75
    Likes Received:
    1
    Trophy Points:
    8
    Location:
    /dev/null
    I popped a "yum upgrade" on our development (read test) Centos 4.3 boxes, and it all went through to 4.4 pretty much seamlessly. I did remove kernel* from the yum excludes before doing it (and have since put it back in), but as far as I can tell, it didnt break anything.

    I have stopped using up2date - it seems to cause more problems than yum does (do they perform dependancy checking in a different way? I generally feel yum is more thorough).

    Rich
     
  17. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    Just to be clear, the glibc problem described in my opening post is occuring on VPS only, dedicated servers are fine.
     
Loading...

Share This Page