+++ This bug was initially created as a clone of Bug #716662 +++

Created attachment 509949 [details]
Anaconda dump

Description of problem:
Anaconda crashes, depending on the combination of packages selected

Version-Release number of selected component (if applicable):
15.31

How reproducible:
Reliable with the same set of packages selected

Steps to Reproduce:
1. pxe-install F15 (text mode)
2.
3.
  
Actual results:
Anaconda crashes after last package is loaded, but before installing boot (sorry, that's all that's available from screen info)

Expected results:
Anaconda completes the install (or at least handles the exception properly if I'm doing something silly).

Additional info:
1. Success/failure depends on the particular set of packages selected. However it's not a simple dependence. I can choose one subset of packages, A, which installs correctly, and another subset, B, which also installs correctly, but A U B won't install. It's also not a space dependence, A U B still fails even if I double the available filesystem space.

2. I suspect that the problem may be partially to do with selecting graphical components for a non-graphical install; I eventually got an acceptable install by eliminating everything that might have a graphical component. But it isn't purely a result of that, because of 1.

3. Of course, this looks a lot like Bug 601291. However I think it must be a different issue, because that was reported against F13 and F14 installs, whereas the kickstart script I was using here worked fine for F13 and F14 (modulo obvious changes in directory names etc).

--- Additional comment from akozumpl on 2011-06-27 03:42:36 EDT ---

Hi,

can you try resyncing your repos? There seems to be a problem with RPM db checksum according to the logs:

Rpmdb checksum is invalid: dCDPT(pkg checksums)

Ales

--- Additional comment from urilabob on 2011-06-27 17:49:01 EDT ---

Yes, I noticed that also but assumed it was a red herring. This is an install directly from a copy of the F15 i386 install DVD (so the only repo involved is the copy of the install DVD NFS-mounted into anaconda, as far as I can understand). OK, I better make sure I checksummed the iso. Other than that, I'm not sure what I can do - any more detailed directions would be greatly appreciated.

--- Additional comment from urilabob on 2011-06-27 18:26:14 EDT ---

Dear Ales, the iso is OK according to sha256. So I'm not sure what else to check. If I'm misunderstanding your request (i.e. if there is some way I could resync the DVD repo), please clarify.

--- Additional comment from clumens on 2011-06-28 09:13:36 EDT ---

There's more than just that checksum error, though.  Check out install.log right at the Django package.  That's where the real weirdness begins:

Installing Django-1.3-2.fc15.noarch
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region
error: rpmdb: unable to allocate memory for mutex; resize mutex region

--- Additional comment from akozumpl on 2011-06-28 10:34:39 EDT ---

This really points to a bug in RPM or yum, cloning.

In Anaconda I am going to have a better exception window displayed (not directly a traceback).