I recently built a CentOS from the 4.3 ISOs. Now I'm ready to build another 10 systems using kickstart. I took the anaconda-ks.cfg file from the first system I built manually, modified it slightly (see below), and made it available via http. I booted the new system from the first CentOS 4.3 CD and typed the following: boot: linux ks=http://hostname/test-ks.cfg Here are the changes I made to the kickstart file: - Replaced "cdrom" with "url --url http://hostname" - Removed xconfig line (slightly different video HW) - Changed the host name in the network line - Uncommented the partition information The system boots the initial kernel, gets an IP address, gets the kickstart file via http, but then dies with a "installation exited abnormally -- received signal 11" message. I've done this successfully in the past. Can a misconfigured kickstart file cause this problem? How can I debug this? Alfred
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, May 31, 2006 at 05:22:29PM -0400, Alfred von Campe wrote:> kickstart file via http, but then dies with a "installation exited > abnormally -- received signal 11" message. I've done this > successfully in the past. Can a misconfigured kickstart file cause > this problem? How can I debug this?In 90% of the cases, a signal 11 means faulty memory. In 9% of the cases, something wrong with the processor (usually overheating) 1%: Others reasons Suggestion: Running memtest86 - -- Rodrigo Barbosa <rodrigob at suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfgxgpdyWzQ5b5ckRAq2aAJ95/BTWeEtr+MbbHDLc7FU6Beat0ACcCi5+ AzeaTf+blSTXN2HIHsA1sgc=FRwc -----END PGP SIGNATURE-----