<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 7/19/2010 4:00 PM, James Hogarth wrote:
<blockquote
cite="mid:AANLkTimq2xebQrSbXFl8PHmsVJMRWikk4vkyvoOQ7aVT@mail.gmail.com"
type="cite">
<p>With the kernel logging an out of memory error? My first
instinct would be to check free to see the status of RAM and
swap and perhaps end unnecessary processes..</p>
<p>James</p>
<p>Sent from Android mobile</p>
<p>On 19 Jul 2010 20:18, "Bowie Bailey" <<a
moz-do-not-send="true" href="mailto:Bowie_Bailey@buc.com">Bowie_Bailey@buc.com</a>>
wrote:<br type="attribution">
> On 7/19/2010 1:00 PM, James B. Byrne wrote:<br>
>> I am experiencing a problem with yum on one of my
CentOS-5.5<br>
>> systems. Specifically, on Friday past (July 16), I ran
yum update<br>
>> as root. Yum displayed all of the outdated packages and
asked if I<br>
>> wanted to proceed. An answered yes. This first package
downloaded<br>
>> was nss. At this point yum simply stopped processing or
responding.<br>
>> A ctrl-c at the yum session terminal window did not
interrupt the<br>
>> task. Top did not display any yum processes.<br>
>><br>
>> I killed that particular process to regain the console
session, but<br>
>> I had to use -9 because nothing else worked. Yum
continues to<br>
>> behave in this strange manner. Any invocation of yum
with any<br>
>> option just stops responding.<br>
>><br>
>> Before I manually remove yum and reinstall it using rpm
could anyone<br>
>> provide a clue as to what might be happening here and
how it might<br>
>> be cured. I found this one entry from yum in the log
files:<br>
>><br>
>> /var/log/messages.1:Jul 16 00:14:43 gway01 kernel: Out
of memory:<br>
>> Killed process 1380, UID 0, (yum-updatesd-he).<br>
>><br>
>> However, this entry occurred some time before I
attempted my update<br>
>> task later that same morning.<br>
>><br>
>> I would like to be directly copied on any replies as I
am a digest<br>
>> subscriber.<br>
> <br>
> My first attempt would be to do a "yum clean all" and then
try it again.</p>
</blockquote>
<blockquote type="cite">
<p>With the kernel logging an out of memory error? My first
instinct would be to check free to see the status of RAM and
swap and perhaps end unnecessary processes..<br>
</p>
</blockquote>
<br>
Ahh... I must have missed that.<br>
<br>
So if memory is the problem, then check your RAM as James
suggested. Run 'free' and see how much free memory you have.<br>
<br>
On the other hand, it's still a good idea to clean out yum's
databases from time to time.<br>
<br>
-- <br>
Bowie<br>
</body>
</html>