Hi,

I am running mysql 3.23.38-log with the my-huge.cnf and I saw that one table was 
getting pretty close to the 2gb's so I decided to recompile the mysql with the 
--with-raid parameter. And I do so, the compile goes fine and when I tried to run up 
the server it did this:

root     15677  1.0  0.0  2140 1028 pts/2    S    10:48   0:00 /bin/sh 
/usr/local/bin/safe_mysqld --datadir=/u01/mysql --pid-file=/u01/mysql/cartman.pid
root     15702  3.0  0.0 11988 1668 pts/2    S    10:48   0:00 
/usr/local/libexec/mysqld --basedir=/usr/local --datadir=/u01/mysql --user=root 
--pid-file=/u
root     15704  0.0  0.0     0    0 pts/2    Z    10:48   0:00 [mysqld <defunct>]

And just stopped there. I checked all the tables with myisamchk, tried starting it up 
without the config, recompiling the server with the old configure line. Then when I 
changed the mysql-server to startup safe_mysqld with strace to try to see where it 
stopped it started up normally. Ok I thought the problem was solved so I take out the 
strace and run it again and the server halts. Since I needed the server to be running 
it worked fine if I started the mysql without the safe_mysqld directly from command 
line.

./mysqld --basedir=/usr/local --datadir=/u01/mysql --user=root 
--pid-file=/u01/mysql/cartman.pid --skip-locking &

Has anyone seen anything like that or have any solutions for me? Since I don't want to 
be running the server like that.

regards,
Gudmundur


Some info on the machine:

RedHat 7.1
Linux cartman 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686 unknown

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sda3              6048352   2473604   3267508  44% /
/dev/sda1                31079     14120     15355  48% /boot
/dev/sdb1            104957340  25894880  73730892  26% /u01
/dev/sda4             10381036   3465764   6387940  36% /var

HP NetServer LT6000r 
2 x Intel PIII Xeon 700 1M Cache
4 GB ECC RAM 
2 x HP 18.2GB 10K Ultra3 Wide keyrandi Raid 1
6 x HP 36.4GB 10K Ultra3 Wide keyrandi Raid 0,1 in a RS 12.


Reply via email to