FAQ
Somewhere in the process of doing a yum update from a terminal window
open in an NX/freenx desktop session, the whole session blew up -
perhaps when ssh restarted or when freenx was updated. The yum update
did not complete beyond that point and the session was gone when I
reconnected. Is that supposed to happen? (Centos 5.x)

--
Les Mikesell
lesmikesell at gmail.com

Search Discussions

  • Akemi Yagi at Dec 24, 2008 at 7:48 pm

    On Wed, Dec 24, 2008 at 11:42 AM, Les Mikesell wrote:
    Somewhere in the process of doing a yum update from a terminal window
    open in an NX/freenx desktop session, the whole session blew up -
    perhaps when ssh restarted or when freenx was updated. The yum update
    did not complete beyond that point and the session was gone when I
    reconnected. Is that supposed to happen? (Centos 5.x)
    Yes, it does happen. For more details, please see (warning, very long thread):

    http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id166&forum7

    If you now have a broken rpm database because of the interrupted yum
    session, the thread has a remedy for that.

    Akemi / toracat
  • Akemi Yagi at Dec 25, 2008 at 1:19 am

    On Wed, Dec 24, 2008 at 11:48 AM, Akemi Yagi wrote:
    On Wed, Dec 24, 2008 at 11:42 AM, Les Mikesell wrote:
    Somewhere in the process of doing a yum update from a terminal window
    open in an NX/freenx desktop session, the whole session blew up -
    perhaps when ssh restarted or when freenx was updated. The yum update
    did not complete beyond that point and the session was gone when I
    reconnected. Is that supposed to happen? (Centos 5.x)
    Yes, it does happen. For more details, please see (warning, very long thread):

    http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id166&forum7

    If you now have a broken rpm database because of the interrupted yum
    session, the thread has a remedy for that.
    OK, that long thread caused a headache for someone (can't tell you
    who), so I'm going to give you a shortcut.

    Run the command:

    rpm -qa --qf "%{NAME} %{ARCH}\n" | sort | uniq -c | awk '$1 != 1 {
    print $2 }' | sort

    If the output shows anything other than gpg-pubkey or kernel*, then
    your rpm database is most likely broken. Go to #45 of that thread.
    The OP nicely summarized the procedure to fix it.

    Akemi / toracat

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcentos @
categoriescentos
postedDec 24, '08 at 7:42p
activeDec 25, '08 at 1:19a
posts3
users2
websitecentos.org
irc#centos

2 users in discussion

Akemi Yagi: 2 posts Les Mikesell: 1 post

People

Translate

site design / logo © 2022 Grokbase