From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 Description of problem: I have many fc core 3 machine and all update via yum successfully however two of them are firewalls running iptables and they never update sucessfully. I run yum update and the output is normally the following Setting up Update Process Setting up Repo: base repomd.xml 100% |=========================| 1.1 kB 00:00 Setting up Repo: updates-released repomd.xml 100% |=========================| 951 B 00:00 Reading repository metadata in from local files Terminated I run up2date and it patches sucessfully but was under the impression that up2date is decpreciated and that it was advisable to use yum Thanks Version-Release number of selected component (if applicable): yum-2.1.11-3 How reproducible: Always Steps to Reproduce: 1. Install and run ipatables firewall 2. once running run yum update 3. Actual Results: Setting up Update Process Setting up Repo: base repomd.xml 100% |=========================| 1.1 kB 00:00 Setting up Repo: updates-released repomd.xml 100% |=========================| 951 B 00:00 Reading repository metadata in from local files Terminated Expected Results: packages patched. Additional info:
Terminated is an odd error. Can you give me a little more info? 1. how much memory on this system? 2. what does 'yum -d4 update' return? 3. do you see anything in dmesg about the OOM killer? or Out-of-Memory?
Yes I do appologise. I believed the system had 128MB when in fact it has 32MB and is indeed showing an out of memory error. Thus I presume this is the cause of the problem and I will upgrade. Please can you confirm if you need any error logs from the system if it should have done things differently. Thanks for the prompt assistance
Yes the OOM is causing the exit. A trick you can _try_ though I'm not sure it will work: yum --disablerepo=base update that will remove all rpms in the 'base' repo and should dramatically lessen the memory footprint. Though, to be clear 32MB is NOT sufficient.
Not sure what to do now. I am happy with the resolution and the help - much appreciated. The --disablerepo does work fine. Thus I am attempting to close this call. Many thanks for the prompt help
Well, before you do anything else you should first ADD MEMORY :)