Bug 86211 - Installer Crashes citing /usr/lib/anaconda/gui.py as reason
Summary: Installer Crashes citing /usr/lib/anaconda/gui.py as reason
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 8.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-17 10:38 UTC by Ranganath P. Kashyap.
Modified: 2007-04-18 16:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-05-21 09:50:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Ranganath P. Kashyap. 2003-03-17 10:38:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
traceback(most recent call last)

file "/usr/lib/anaconda/gui.py", line 786,in
handleRenderCallbackself.CurrentWindow.renderCallback()

file "/usr/lib/anaconda/iw/progress.gui.py",line 149, in 
renderCallbackself.icw.nextclicked()

file "/usr/lib/anaconda/gui.py", line 632 , in 
nextClickedself.dispatch.gotonext()

file "/usr/lib/anaconda/dispatch.py", line 150, in 
gotoNextself.moveStep()

file "/usr/lib/anaconda/dispatch.py", line 215, in 
MoveStep.rc=apply(func,self.bindArgs(args))

file "/usr/lib/anaconda/packages.py", line 430, in 
turnOnFilesystemspartitions.doMetaDeletes(diskset)

file "/usr/lib/anaconda/partitions.py",line 1110, in 
doMetaDeleteslvm.vgactivate()

file "/usr/lib/anaconda/lvm.py", line 54, in vgactivate 
searchPath=1)

file "/usr/lib/anaconda/iutil.py", line 66, in 
execWithRedirectchildpid=os.fork()

OSError: [Errno 12] cannot allocate memory


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


How reproducible:
Always

Steps to Reproduce:
1.try installing(on my machine though;-)
2.
3.
    

Actual Results:  installer crashes

Expected Results:  installer should proceed normally

Additional info:

Comment 1 Michael Fulbright 2003-03-17 19:24:25 UTC
How much RAM does your system have?

Comment 2 Ranganath P. Kashyap. 2003-03-18 05:30:54 UTC
System Info:-
P3 - 500MHz
Intel810 MotherBoard
64MB RAM (I was able to install Psyche on another s/m with 64MB RAM)
20GB HDD (with first partition for linux)

anything else?

Comment 3 Michael Fulbright 2003-03-21 15:58:44 UTC
I would recommend at least 128MB (192MB wouldn't hurt) of swap for this system.
How much were you using when the error occurred?


Comment 4 Ranganath P. Kashyap. 2003-03-27 10:31:28 UTC
i was using 128MB! the partitioning on the 20Gig disk was like 
first partition Ext2 3.5GB (Created using PartitionMagic)
second partition swap 128MB (Created using PartitionMagic)
third partition FAT32
fouth partition FAT32
fifth partition FAT32

Comment 5 Michael Fulbright 2003-04-02 20:23:17 UTC
Then probably you need to try 192MB of swap.

Comment 6 Ranganath P. Kashyap. 2003-04-04 05:01:29 UTC
do you think that is all the problem? how about the partitioning? am i doing it 
right?

Comment 7 Michael Fulbright 2003-04-04 21:18:14 UTC
I would recommend creating a swap partition of at least 192MB.

Comment 8 Ranganath P. Kashyap. 2003-04-14 04:21:39 UTC
hi,
i tried using 256MB swap space; but that didn't help either!
regards,
-kashyap.

Comment 9 Trev 2003-04-18 23:56:59 UTC
Hi, I just tried it on a system with 48MB RAM and got the same error, but when 
I did a text-only installation, it worked fine.

I don't think it has any relation to the swap, as it crashed *before* creating 
the swap partition! Must be a bug with 8.0 - the 7.3 install worked fine for me.

Comment 10 Michael Fulbright 2003-05-12 21:21:09 UTC
Usually 128MB is enough for the graphical install to start up and work. You need
the extra swap for upgrades usually since these take more RAM to process than a
fresh install.

Try booting with 'linux text' on the command line.

Comment 11 Ranganath P. Kashyap. 2003-05-21 09:50:44 UTC
it worked for me. thanks a lot
regards,
kashyap


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