Red Hat Bugzilla – Bug 164871
Bad: Installer crashed
Last modified: 2008-08-02 19:40:32 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Description of problem: I boot the installation kernel with pxeboot, and the chose NFS image as installation media. when the NFS encouter network problem with RPC time out, the installation procedure return me signal 11, it seems like: Install exited abnormally â received signal 11, sending termination signal ⦠done Sending kill signal ⦠done Disabling swap⦠Umounting filesystems⦠proc/bus/usb done /proc done /dev/pts done /sys done /tmp/ramfs done You may safely reboot your system. Version-Release number of selected component (if applicable): U2 alpha How reproducible: Always Steps to Reproduce: 1.boot with pxe 2.choose NFS as installation image, the destination of NFS server may not reachable 3.wait the time out Actual Results: signal 11 occurs Expected Results: I should choose another NFS server Additional info:
Is this with RHEL 4 GA or U1? Also, what is the last thing printed on tty3?
this is RHEL4 U2 alpha. tty3 showes like: mounting nfs path ...../RHEL4-U2-alpha/AS ia32 version. ia32e doesn't appear such phenomenon.
What sorts of NFS problems cause this error to occur - nfs server not running, directory not being exported, etc.?
in normal case, it should be RPC time out, the nfs server is running and the directory is exported. I think it should be network problem caused the RPC time out, because there are at least two routers at the path to the nfs server.
This bug still occurs against RHEL4 U2 Beta ia32
The bug still occurs against RHEL4 U2 RC ia32
Does this still occur with U4 or RHEL5 beta?
If you can reproduce this with FC6, that would be very helpful because we now print out a stack trace if there is a bug in the anaconda loader itself. That trace would show where the problem is, and we could probably work back to RHEL4 from that point since a lot of this loader code doesn't change much. Of course if this is being caused by a kernel problem or other component, you either won't get a stack trace or it will be totally useless.