Bug 912998 - fedup fails to complete: issue with depsolve and Memory Error
Summary: fedup fails to complete: issue with depsolve and Memory Error
Keywords:
Status: CLOSED DUPLICATE of bug 896242
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-20 07:46 UTC by lmsilveira
Modified: 2013-06-07 18:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-07 18:03:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lmsilveira 2013-02-20 07:46:31 UTC
Description of problem:

# fedup-cli --network 18 
setting up repos...
default-installrepo/metalink                             |  31 kB     00:00     
rpmfusion-free-updates/18/i386                           | 3.3 kB     00:00     
rpmfusion-free-updates/primary_db                        |  92 kB     00:00     
rpmfusion-nonfree-updates/18/i386                        | 3.3 kB     00:00     
rpmfusion-nonfree-updates/primary_db                     |  61 kB     00:00     
updates/18/i386/metalink                                 |  25 kB     00:00     
updates/18/i386                                          | 4.7 kB     00:00     
updates/primary_db                                       | 6.2 MB     00:01     
getting boot images...
.treeinfo                                                | 1.2 kB     00:00     
setting up update...
rpmfusion-free-updates/filelists_db                      |  82 kB     00:00     
rpmfusion-nonfree-updates/filelists_db                   |  27 kB     00:00     
updates/filelists_db                                     | 8.6 MB     00:01     
finding updates 100% [=========================================================]Traceback (most recent call last):
  File "/usr/bin/fedup-cli", line 356, in <module>
    main(args)
  File "/usr/bin/fedup-cli", line 301, in main
    pkgs = download_packages(f)
  File "/usr/bin/fedup-cli", line 57, in download_packages
    updates = f.build_update_transaction(callback=output.DepsolveCallback(f))
  File "/usr/lib/python2.7/site-packages/fedup/download.py", line 188, in build_update_transaction
    (rv, msgs) = self.buildTransaction(unfinished_transactions_check=False)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1138, in buildTransaction
    (rescode, restring) = self._doSkipBroken(rescode, restring)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1292, in _doSkipBroken
    rescode, restring = self._skipPackagesWithProblems(rescode, restring)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1365, in _skipPackagesWithProblems
    rescode, restring = self.resolveDeps(True, skipping_broken=True)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 873, in resolveDeps
    CheckDeps, checkinstalls, checkremoves, missing = self._resolveRequires(errors)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 1020, in _resolveRequires
    errors += errormsgs
MemoryError

Version-Release number of selected component (if applicable):
fedup-0.7.3-0.git20130128.fc17.noarch

How reproducible:
Seems to always crash.  The "MemoryError" message appears intermittent.

Steps to Reproduce:
1. install fedup from fedora-updates-testing as suggested
2. run fedup from network
3.
  
Actual results:
Application crashes.

Expected results:
Normal completion, system ready to reboot.

Additional info:
fedup worked on two additional systems but seems to fail here consistently.

On this machine I get the same result if I do

fedup --iso /src/Fedora-18-i386-DVD.iso

Comment 1 Will Woods 2013-03-04 21:00:50 UTC
"MemoryError" just means your system ran out (or otherwise couldn't) allocate memory.

This is almost certainly the same as bug 896242 - the only difference is whether we run out of RAM while still in Python or while trying to run an external program.

How much RAM is in this system? Does the problem go away if you shut down unnecessary programs or run fedup from multi-user (non-graphical) mode?

Comment 2 Will Woods 2013-06-07 18:03:10 UTC

*** This bug has been marked as a duplicate of bug 896242 ***


Note You need to log in before you can comment on or make changes to this bug.