Manager of pid file quit without updating failed

Description: Failed to install an the client server RPM.

The server will not start: magare:~$ sudo rpm -i My SQL-client-5.1.25-0.glibc23.x86_64My SQL-server-5.1.25-0.glibc23.x86_64PLEASE REMEMBER TO SET A PASSWORD FOR THE My SQL root USER !

Install all components and restart, now you should have mysql server running again but now you will need to migrate the old data to the new.

manager of pid file quit without updating failed-70manager of pid file quit without updating failed-84

很明显是缺少了库文件 libstdc 5 ,这时我们搜索和libstdc相关的包安装即可。 如果是centos系统,默认会开启selinux,这个时候可以先关闭它,打开/etc/selinux/config,把SELINUX=enforcing改为SELINUX=disabled后存盘退出重启机器试试。 也有可能是第二次在机器上安装mysql,有残余数据影响了服务的启动,去mysql的数据目录/data看看,如果存在mysql-bin.index,就赶快把它删除掉吧,它就是罪魁祸首了。 四、确定数据目录的权限 数据目录一般是/data,检查一下它的归属,如果不是mysql所有者,一般安装mysql时都会创建mysql的用户和组的,这时要修改一下用户和组: chown -R mysql:mysql /var/data mysql在启动时没有指定配置文件时会使用/etc/my.cnf配置文件,请打开这个文件查看在[mysqld]节下有没有指定数据目录(datadir)。如果没有请在[mysqld]下设置这一行: datadir = /usr/local/mysql/data 如果这是第二次在机器上安装mysql就极有可能会出现这种情况的,这时系统上很有可能还有mysql进程在运行着。可以执行下列命令查看: ps -ef | grep mysql 如果出现的结果不止一行的就赶快把它kill掉吧。 可以检查一下/etc/my.cnf文件中有没有没被注释掉的skip-federated字段,如果有就立即注释掉吧。 也有可能你现在还不知道mysql的出错日志在哪里吧?这时你可以执行命令查看: 这时再试试吧。如果还是不行的话就留言让大家帮你看看吧……

以上摘自Angel Sanctuary 前因:因为硬盘满了,mysql启动不起来了。登录上去看了一下,发现原因。删除mysql的日志文件,重启mysql发现错误:Starting My SQL.

S Apr30 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysql 1666 0.0 0.9 130000 19356 ?

130319 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130319 [Warning] '--skip-locking' is deprecated and will be removed in a future release. 130319 [Warning] '--log' is deprecated and will be removed in a future release. ^G/usr/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 130319 [ERROR] Can't open the mysql.plugin table. 130319 Inno DB: Initializing buffer pool, size = 8.0M 130319 Inno DB: Completed initialization of buffer pool 130319 Inno DB: Operating system error number 13 in a file operation.

Version: '5.1.55' socket: '/var/lib/mysql/mysql.sock' port: 3306 My SQL Community Server 110305 mysqld_safe mysqld from pid file /var/lib/mysql/ended /usr/bin/mysqld_safe 120502 mysqld_safe Logging to '/var/lib/mysql/mysql-bin.err'.

120502 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120502 mysqld_safe mysqld from pid file /var/lib/mysql/tent.pid ended [email protected]:/var/lib/mysql$ ps aux | grep -i mysql root 1599 0.0 0.0 3712 1308 ?

For example, I experienced this problem today after upgrading the Apache and Ruby (Yes, My SQL is not part of the update), and I got this error message afterward.

After rebooting the computer, the error message is gone.

The mysql.socket is no longer visible in /tmp eventhough mysql thinks it is.

Tags: , ,