Interesting problem here...perhaps.
I just upgraded about 6 machines this morning after syncing a local yum server with no problems...until I get to my personal laptop of course. I did the usual:
yum update yum yum update
It went about half way through and then the terminal seemed to just die. It just sat there stuck in limbo. I let it go for about 30 minutes and it never moved, so I killed the terminal, but yet yum was still running as a process which I had to kill.
Reluctantly I rebooted, and everything came up ok, but I'm very hesitant to believe that things are tip-top. Is there anything I can do or anyway I can check anything to double check things are actually fine?
The /etc/redhat-release shows ok:
cat /etc/redhat-release CentOS release 4.4 (Final)
I've been watching top and all that good stuff. All my services appear ok as well, but call me paranoid because I'm convinced something has to be wrong.
Should I stop with my paranoia and just chalk it up to my bash session died, yum completed ok, but hung afterwards? Thanks!
Max
Max H. wrote:
Interesting problem here...perhaps.
I just upgraded about 6 machines this morning after syncing a local yum server with no problems...until I get to my personal laptop of course. I did the usual:
yum update yum yum update
It went about half way through and then the terminal seemed to just die. It just sat there stuck in limbo. I let it go for about 30 minutes and it never moved, so I killed the terminal, but yet yum was still running as a process which I had to kill.
Reluctantly I rebooted, and everything came up ok, but I'm very hesitant to believe that things are tip-top. Is there anything I can do or anyway I can check anything to double check things are actually fine?
The /etc/redhat-release shows ok:
cat /etc/redhat-release CentOS release 4.4 (Final)
I've been watching top and all that good stuff. All my services appear ok as well, but call me paranoid because I'm convinced something has to be wrong.
Should I stop with my paranoia and just chalk it up to my bash session died, yum completed ok, but hung afterwards? Thanks!
FYI, I just seemed to discover that the actual upgrade process completed, but the cleanup afterwards part is what died. I'm showing various packages with two versions of packages installed. For example:
[root@laptop me]# rpm -q thunderbird thunderbird-1.5.0.5-0.el4.1.centos4 thunderbird-1.5.0.5-0.el4.2.centos4
Now, I'm in thunderbird right now as I type with no problems or anything. Is there a way to re-run the yum process and force the cleanup at this point? Or am I stuck here?
Max
On 31/08/06, Max H. btmanmeh@verizon.net wrote:
Max H. wrote:
yum update yum yum update
It went about half way through and then the terminal seemed to just die. It just sat there stuck in limbo. I let it go for about 30 minutes and it never moved, so I killed the terminal, but yet yum was still running as a process which I had to kill.
FYI, I just seemed to discover that the actual upgrade process completed, but the cleanup afterwards part is what died. I'm showing various packages with two versions of packages installed. For example:
Again, sounds like you encoutered the Yum futex error/bug. See my response to Simen in the parallel "Yum upgrade to 4.4 problem" thread and the old threads back in the 4.2 -> 4.3 days.
"futex.. How to remove lots of duplicate packages" http://lists.centos.org/pipermail/centos/2006-March/thread.html#62319
"yum update killed on cleanup stage - anything to worry about?" http://lists.centos.org/pipermail/centos/2006-March/thread.html#62568
I don't know if there's any easy way to avoid this, but you can mitigate the problem by batching your yum updates into smaller chunks which will, if the futext problem halts the update, leave you with a less hosed system. :)
Will.
Will McDonald wrote:
I don't know if there's any easy way to avoid this, but you can mitigate the problem by batching your yum updates into smaller chunks which will, if the futext problem halts the update, leave you with a less hosed system. :)
Thanks Will! I think I'll just sort through the packages manually and remove the older versions after I check and make sure the newer one is actually installed.
It's supposed to be a rainy weekend anyways here... ;)
I never realized this was a common problem, because I've never had this issue before and I've done quite a few upgrades with Fedora and CentOS the past two years. Like I said, I guess it's my turn. Thanks again!
Max
Will McDonald wrote:
I don't know if there's any easy way to avoid this, but you can mitigate the problem by batching your yum updates into smaller chunks which will, if the futext problem halts the update, leave you with a less hosed system. :)
I don't understand what you mean when you say "batch yum updates into smaller chunks". I usually just do a "yum update", eyeball the packages that it thinks I need, then hit ENTER to agree to the update. What does this "batching" involve?
Cheers,
On Thu, Aug 31, 2006 at 11:44:05AM -0400, chrism@imntv.com wrote:
I don't understand what you mean when you say "batch yum updates into smaller chunks". I usually just do a "yum update", eyeball the packages that it thinks I need, then hit ENTER to agree to the update. What does this "batching" involve?
10 Run "yum check-update". 20 Look at the list of packages to be updated. 30 Stop if there aren't any. 40 Pick several arbitrarily. 50 REM Although I suggest starting with python-sqlite -- see other thread. 60 Run "yum -y update onepackagename anotherpackagename maybeathird". 70 goto 10
:)
Matthew Miller wrote:
On Thu, Aug 31, 2006 at 11:44:05AM -0400, chrism@imntv.com wrote:
I don't understand what you mean when you say "batch yum updates into smaller chunks". I usually just do a "yum update", eyeball the packages that it thinks I need, then hit ENTER to agree to the update. What does this "batching" involve?
10 Run "yum check-update". 20 Look at the list of packages to be updated. 30 Stop if there aren't any. 40 Pick several arbitrarily. 50 REM Although I suggest starting with python-sqlite -- see other thread. 60 Run "yum -y update onepackagename anotherpackagename maybeathird". 70 goto 10
:)
Wow, suitable for parsing on my TRS-80. :)
Thanks!
On 31/08/06, chrism@imntv.com chrism@imntv.com wrote:
Will McDonald wrote:
I don't know if there's any easy way to avoid this, but you can mitigate the problem by batching your yum updates into smaller chunks which will, if the futext problem halts the update, leave you with a less hosed system. :)
I don't understand what you mean when you say "batch yum updates into smaller chunks". I usually just do a "yum update", eyeball the packages that it thinks I need, then hit ENTER to agree to the update. What does this "batching" involve?
Just yum update a few packages at a time, that way if the process hangs you only have a handful of packages to clean up after rather than dozens or more. So do
# yum check-update
Look at the list then maybe do...
# yum update package1 package2 package3 package4
Yum will sort out the first 4 packages in the list and their dependencies, then repeat until done.
Will.
Sorry...I didn't realize there was a similar thread started this morning on this very matter. That has answered my questions. I've never had a problem like this before, I guess I'm overdue!
Max
-
chrism＠imntv.com -
Matthew Miller -
Max H. -
Will McDonald