Kernel panic during install of Cpanel

[WebRuss]

Hello All

Can anyone assist? I'm trying to install cpanel on a dell poweredge 100 and part way through the install I get a kernel panic during the install process. I have a pristine Centos 4.1 installation.

Hardware specs:
dell poweredge 100
P3 750Mhz
256 MB ram

A quick look at the /var/log files shows:
cpanel-install-thread0.log
cpanel-install-thread1.log

There does not seem to be any way to attach a file here so here are the last few lines of cpanel-install-thread1.log:


Making Encode (dynamic)
make[2]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode'
Warning: ../../lib/Config.pm may be out of date with ../../config.sh
cd ../.. && make lib/Config.pm
.make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[3]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
make[2]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode'
make[2]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode'
Warning: ../../lib/Config.pm may be out of date with ../../config.sh
cd ../.. && make lib/Config.pm
make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
.sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[3]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/Byte'
Warning: ../../../lib/Config.pm may be out of date with ../../../config.sh
cd ../../.. && make lib/Config.pm
make[4]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[4]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
make[3]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/Byte'
make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/CN'
Warning: ../../../lib/Config.pm may be out of date with ../../../config.sh
cd ../../.. && make lib/Config.pm
.make[4]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[4]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
make[3]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/CN'
make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/EBCDIC'
Warning: ../../../lib/Config.pm may be out of date with ../../../config.sh
cd ../../.. && make lib/Config.pm
make[4]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
.sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[4]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
make[3]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/EBCDIC'
make[3]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7/ext/Encode/JP'
Warning: ../../../lib/Config.pm may be out of date with ../../../config.sh
cd ../../.. && make lib/Config.pm
make[4]: Entering directory `/home/cpins/installd/perl587installer/perl-5.8.7'
./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
sh mv-if-diff configpm.tmp lib/Config.pm
File lib/Config.pm not changed.
make[4]: Leaving directory `/home/cpins/installd/perl587installer/perl-5.8.7'
../../../miniperl "-I../../../lib" ../bin/enc2xs -"Q" -o eu_01_t.c -f eu_01_t.fnm
...Writing compiled form
.

[chirpy]

Did you manage to get the panic information from the console? Usually, panics on new servers are down to fault memory sticks, or perhaps fault filesystems/disks.