About thirty minutes ago I started an update. Everything downloaded
fine. But when it came to "Running Transaction", it hung:
....
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : xulrunner
1/18
And there it sits still.
There's plenty of disk space. The load on the CPU is under 1.0. There
is some disk activity, but no way so much as to cause anything to hang
and no major writing related to yum. Disk reads are just about null,
except just now when I grep'ed for something to make sure that the disk
could be read. I'm not using even half of the available RAM.
Anyone else run into this problem?
On 07/01/2013 01:21 PM Reindl Harald wrote:> Am 01.07.2013 19:16, schrieb ken: >> About thirty minutes ago I started an update. Everything downloaded >> fine. But when it came to "Running Transaction", it hung: >> >> Running rpm_check_debug >> Running Transaction Test >> Finished Transaction Test >> Transaction Test Succeeded >> Running Transaction >> Updating : xulrunner >> 1/18 >> >> And there it sits still. >> >> There's plenty of disk space. The load on the CPU is under 1.0. There >> is some disk activity, but no way so much as to cause anything to hang >> and no major writing related to yum. Disk reads are just about null, >> except just now when I grep'ed for something to make sure that the disk >> could be read. I'm not using even half of the available RAM > > what about look in dmesg and/or /var/log/messages? >No. Nothing relevant there.
ken wrote:> About thirty minutes ago I started an update. Everything downloaded > fine. But when it came to "Running Transaction", it hung: > > .... > Running rpm_check_debug > Running Transaction Test > Finished Transaction Test > Transaction Test Succeeded > Running Transaction > Updating : xulrunner > 1/18 > > > And there it sits still. > > There's plenty of disk space. The load on the CPU is under 1.0. There > is some disk activity, but no way so much as to cause anything to hang > and no major writing related to yum. Disk reads are just about null, > except just now when I grep'ed for something to make sure that the disk > could be read. I'm not using even half of the available RAM. > > Anyone else run into this problem?I've only run into it with an selinux policy update, when it apparently decided to relabel about 5 zillion files.... mark
On 07/01/2013 01:16 PM ken wrote:> About thirty minutes ago I started an update. Everything downloaded > fine. But when it came to "Running Transaction", it hung: > > .... > Running rpm_check_debug > Running Transaction Test > Finished Transaction Test > Transaction Test Succeeded > Running Transaction > Updating : xulrunner > 1/18 > > > And there it sits still. > > There's plenty of disk space. The load on the CPU is under 1.0. There > is some disk activity, but no way so much as to cause anything to hang > and no major writing related to yum. Disk reads are just about null, > except just now when I grep'ed for something to make sure that the disk > could be read. I'm not using even half of the available RAM. > > Anyone else run into this problem?I had to kill yum to end the process. Then I tried again, less ambitiously and it hung again, this time earlier in the process: # yum -d 8 update firefox Loading "aliases" plugin Loading "allowdowngrade" plugin Loading "changelog" plugin Loading "downloadonly" plugin Loading "fastestmirror" plugin Loading "filter-data" plugin Loading "kernel-module" plugin Loading "keys" plugin Loading "kmod" plugin Loading "list-data" plugin Loading "merge-conf" plugin Loading "priorities" plugin Loading "security" plugin Loading "tsflags" plugin Loading "verify" plugin Running "config" handler for "aliases" plugin Running "config" handler for "allowdowngrade" plugin Running "config" handler for "changelog" plugin Running "config" handler for "downloadonly" plugin Running "config" handler for "filter-data" plugin Running "config" handler for "keys" plugin Running "config" handler for "list-data" plugin Running "config" handler for "merge-conf" plugin Running "config" handler for "priorities" plugin Running "config" handler for "security" plugin Running "config" handler for "verify" plugin And there it hangs now.
Hmm. Not even trying to do an update and yum hangs: # ls /var/run/yum* ls: /var/run/yum*: No such file or directory # yum -d 10 info xulrunner Loading "aliases" plugin Loading "allowdowngrade" plugin Loading "changelog" plugin Loading "downloadonly" plugin Loading "fastestmirror" plugin Loading "filter-data" plugin Loading "kernel-module" plugin Loading "keys" plugin Loading "kmod" plugin Loading "list-data" plugin Loading "merge-conf" plugin Loading "priorities" plugin Loading "security" plugin Loading "tsflags" plugin Loading "verify" plugin Running "config" handler for "aliases" plugin Running "config" handler for "allowdowngrade" plugin Running "config" handler for "changelog" plugin Running "config" handler for "downloadonly" plugin Running "config" handler for "filter-data" plugin Running "config" handler for "keys" plugin Running "config" handler for "list-data" plugin Running "config" handler for "merge-conf" plugin Running "config" handler for "priorities" plugin Running "config" handler for "security" plugin Running "config" handler for "verify" plugin
On 07/01/2013 05:52 PM Eero Volotinen wrote:> is this fixing the issue: > > http://fedoranews.org/alex/tutorial/rpm/16.shtmlI couldn't read any web pages because I shut down firefox hours ago (thinking I was upgrading it) and then it (the older version) wouldn't start again. But then I just solved the yum problem, upgraded several apps (including firefox) and the new firefox is working now. All I did was put the original /var/lib/rpm/Packages file back where it was. (If you read from a post from earlier today, I mv'd off this file and then ran rpm --rebuild to recreate it. This fixed the problem with yum hanging, but then I was getting crazy error messages from yum and from rpm.) Something told me to put the original Packages file back where it was, I did, and now yum works again. And the just-upgraded firefox works too. Thanks to you and everyone else who responded. I have to say, I still don't know what caused the problem in the first place. But sometimes things just have to be a mystery.