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?
Segmentation fault - am I in big trouble...?
seems, like my problems are solved!!!!!scott wrote:My gut feeling on this is either you've got the wrong distro's version of mysql installed, or that possibly the box has been rooted and the badguy's put in an incompatible rootkit.
glib, glibc, glib-devel rpm packages are not compatible with my configuration (VPS + any MySQL versions, RH 3ES)
I cannot say which one exactly, because I'am so tired to make an "investigation" on this, but if I updatethose rpm's from Your channels, mysql is not starting at all.
So, still have no compiler on the system to build Midnight Commander, but i'll think something.
Generally, it seems, that you are right - incompatible rpm's = wrong distro's.
P.s. Official Chkrootkit link is dead http://freshmeat.net/redir/chkrootkit/2 ... kit.tar.gz
Does anyone know working mirror?
http://www.chkrootkit.org/Audrius wrote: P.s. Official Chkrootkit link is dead http://freshmeat.net/redir/chkrootkit/2 ... kit.tar.gz
Does anyone know working mirror?
--
This is not a signature. This is a bunch of meaningless words. Don't read it.
This is not a signature. This is a bunch of meaningless words. Don't read it.
thanx a lot! have succesfully installed chkrootkit from the source.scott wrote:Ive got chkrootkit and rkhunter in the [atomic] channel.
yum install rkhunter chkrootkit
I've mentioned, that some of libs for art channels are not compatible with ES3 on Virtuozzo - I was wrong. I don't know what I was doing differently this time, but all the glib, glibc and related rpm are installed and system is working fine.
The problem may be that I was too lazy and simply wanted to install/update all the rpm's at once with 1 yum command. Now, after I've carefully picked the steps everything is working fine. Still not updated ~20 packages, but they are not "vital".