Segmentation fault - am I in big trouble...?
Posted: Wed Dec 28, 2005 1:52 pm
Hi,
2 days have no luck to make stable mysql. I'm not even talking about 4.x versions, because 3.23 is not working properly also - to be short, until the first restart
what do I get:
[root@xxx subsys]# /usr/bin/safe_mysqld --defaults-file=/etc/my.cnf
Starting mysqld daemon with databases from /var/lib/mysql
/usr/bin/safe_mysqld: line 1: 4673 Segmentation fault nohup /usr/libexec/mysqld --defaults-file=/etc/my.cnf --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --socket=/var/lib/mysql/mysql.sock >>/var/log/mysqld.log 2>&1
STOPPING server from pid file /var/run/mysqld/mysqld.pid
This is what I get when trying to start mysql "normally"
[root@xx subsys]# service mysqld start
Starting MySQL: [ OK ]
[root@xx subsys]# service mysqld status
mysqld dead but subsys locked
rm mysqld
rm: remove regular empty file `mysqld'? y
[root@xx subsys]# service mysqld status
mysqld is stopped
[root@xx subsys]# service mysqld start
Starting MySQL: [ OK ]
[root@xx subsys]# service mysqld status
mysqld dead but subsys locked
[root@xx subsys]#
And the error log shows:
051228 19:47:26 mysqld started
051228 19:47:26 mysqld ended
thats all!!!!
I'm running MySQL 4.0.25.art, Plesk 7.5.4 VPS, on RH 3ES on EV1...
Installed rpm's mysql, mysql-server, mysql-compat, mysql-devel - all with the same version of course
So this is hardware/system/image/VPS problem, o I am missing something in Mysql configuration?
2 days have no luck to make stable mysql. I'm not even talking about 4.x versions, because 3.23 is not working properly also - to be short, until the first restart
what do I get:
[root@xxx subsys]# /usr/bin/safe_mysqld --defaults-file=/etc/my.cnf
Starting mysqld daemon with databases from /var/lib/mysql
/usr/bin/safe_mysqld: line 1: 4673 Segmentation fault nohup /usr/libexec/mysqld --defaults-file=/etc/my.cnf --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --socket=/var/lib/mysql/mysql.sock >>/var/log/mysqld.log 2>&1
STOPPING server from pid file /var/run/mysqld/mysqld.pid
This is what I get when trying to start mysql "normally"
[root@xx subsys]# service mysqld start
Starting MySQL: [ OK ]
[root@xx subsys]# service mysqld status
mysqld dead but subsys locked
rm mysqld
rm: remove regular empty file `mysqld'? y
[root@xx subsys]# service mysqld status
mysqld is stopped
[root@xx subsys]# service mysqld start
Starting MySQL: [ OK ]
[root@xx subsys]# service mysqld status
mysqld dead but subsys locked
[root@xx subsys]#
And the error log shows:
051228 19:47:26 mysqld started
051228 19:47:26 mysqld ended
thats all!!!!
I'm running MySQL 4.0.25.art, Plesk 7.5.4 VPS, on RH 3ES on EV1...
Installed rpm's mysql, mysql-server, mysql-compat, mysql-devel - all with the same version of course

So this is hardware/system/image/VPS problem, o I am missing something in Mysql configuration?