ERROR! MySQL manager or server PID file could not be found! Starting MySQL.....

最新推荐文章于 2024-04-23 11:44:54 发布
最新推荐文章于 2024-04-23 11:44:54 发布
阅读量299 收藏
点赞数
文章标签： 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/sincosabc/article/details/84683237
版权

wdlinux

在mysql 安装目录下

新建 /home/wddata/var  文件即可  mysql-bin.000008

 

141026 20:13:49 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141026 20:13:49 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141026 20:13:49 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141026 20:13:50  InnoDB: Initializing buffer pool, size = 8.0M
141026 20:13:50  InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141026 20:13:50  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141026 20:13:50  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141026 20:13:50 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141026 20:13:50 [ERROR] Could not open log file
141026 20:13:50 [ERROR] Can't init tc log
141026 20:13:50 [ERROR] Aborting

141026 20:13:50  InnoDB: Starting shutdown...
141026 20:13:55  InnoDB: Shutdown completed; log sequence number 0 44243
141026 20:13:55 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141026 20:13:55 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141029 20:12:20 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141029 20:12:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141029 20:12:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141029 20:12:20  InnoDB: Initializing buffer pool, size = 8.0M
141029 20:12:20  InnoDB: Completed initialization of buffer pool
141029 20:12:20  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141029 20:12:20 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141029 20:12:20 [ERROR] Could not open log file
141029 20:12:20 [ERROR] Can't init tc log
141029 20:12:20 [ERROR] Aborting

141029 20:12:20  InnoDB: Starting shutdown...
141029 20:12:26  InnoDB: Shutdown completed; log sequence number 0 44243
141029 20:12:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141029 20:12:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 11:51:17 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 11:51:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 11:51:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 11:51:18  InnoDB: Initializing buffer pool, size = 8.0M
141101 11:51:18  InnoDB: Completed initialization of buffer pool
141101 11:51:19  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 11:51:19 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 11:51:19 [ERROR] Could not open log file
141101 11:51:19 [ERROR] Can't init tc log
141101 11:51:19 [ERROR] Aborting

wdlinux  下数据库文件位置


/home/wddata/var



141101 11:51:19  InnoDB: Starting shutdown...
141101 11:51:24  InnoDB: Shutdown completed; log sequence number 0 44243
141101 11:51:24 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141101 11:51:24 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:03:50 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:03:50 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:03:50 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:03:50  InnoDB: Initializing buffer pool, size = 8.0M
141101 19:03:50  InnoDB: Completed initialization of buffer pool
141101 19:03:50  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:03:50 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:03:50 [ERROR] Could not open log file
141101 19:03:50 [ERROR] Can't init tc log
141101 19:03:50 [ERROR] Aborting

141101 19:03:50  InnoDB: Starting shutdown...
141101 19:03:55  InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:03:55 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141101 19:03:55 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:40:21 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:40:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:40:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:40:21  InnoDB: Initializing buffer pool, size = 8.0M
141101 19:40:21  InnoDB: Completed initialization of buffer pool
141101 19:40:21  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:40:21 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:40:21 [ERROR] Could not open log file
141101 19:40:21 [ERROR] Can't init tc log
141101 19:40:21 [ERROR] Aborting

141101 19:40:21  InnoDB: Starting shutdown...
141101 19:40:26  InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:40:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141101 19:40:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended
141101 19:57:20 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.1.61/var
141101 19:57:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:57:20 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141101 19:57:20  InnoDB: Initializing buffer pool, size = 8.0M
141101 19:57:20  InnoDB: Completed initialization of buffer pool
141101 19:57:20  InnoDB: Started; log sequence number 0 44243
/www/wdlinux/mysql-5.1.61/libexec/mysqld: File './mysql-bin.000008' not found (Errcode: 2)
141101 19:57:20 [ERROR] Failed to open log (file './mysql-bin.000008', errno 2)
141101 19:57:20 [ERROR] Could not open log file
141101 19:57:20 [ERROR] Can't init tc log
141101 19:57:20 [ERROR] Aborting

141101 19:57:20  InnoDB: Starting shutdown...
141101 19:57:26  InnoDB: Shutdown completed; log sequence number 0 44243
141101 19:57:26 [Note] /www/wdlinux/mysql-5.1.61/libexec/mysqld: Shutdown complete

141101 19:57:26 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.1.61/var/ebs-28575.pid ended

 

sincosabc
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
mysql启动报错MySQL server PID file could not be found
09-09
在使用MySQL数据库的过程中，有时会遇到“MySQL server PID file could not be found”的错误，这是一个常见的启动问题，通常意味着MySQL服务器无法找到其进程ID（PID）文件，该文件用于记录数据库服务的运行状态。...
Starting MySQL.Manager of pid-file quit without updating file.[FAILED]的解决方法
09-11
标题中的“Starting MySQL.Manager of pid-file quit without updating file.[FAILED]”是一个常见的MySQL启动时的错误信息，这表明MySQL服务在尝试启动时遇到了问题。这个错误通常与MySQL服务器的进程ID（PID）文件...
centos +　mysql 安装 时候：Starting MySQL. ERROR! Manager of pid-file quit without updating file....
weixin_34258838的博客
04-25 136
博客已经搬家，请访问如下地址：http://www.czhphp.com 下载：wget http://blog.s135.com/soft/linux/nginx_php/mysql/mysql-5.1.33.zip 安装：        unzip mysql-5.1.33.zip        cd mysql-5.1.33.zip       ./configure --pref...
解决mysql服务启动时出现 ERROR! MySQL server PID file could not be found! 问题
qq_39578356的博客
07-22 1万+
解决mysql服务启动时出现 ERROR! MySQL server PID file could not be found! 问题
ERROR!MySQL serverPID file could not be found! Starting MySQLERROR! The server quit without updating
最新发布
2301_78399805的博客
04-23 1157
面试难免让人焦虑不安。经历过的人都懂的。但是如果你提前预测面试官要问你的问题并想出得体的回答方式，就会容易很多。此外，都说“面试造火箭，工作拧螺丝”，那对于准备面试的朋友，你只需懂一个字：刷！给我刷刷刷刷，使劲儿刷刷刷刷刷！今天既是来谈面试的，那就必须得来整点面试真题，这不花了我整28天，做了份“Java一线大厂高岗面试题解析合集：JAVA基础-中级-高级面试+SSM框架+分布式+性能调优+微服务+并发编程+网络+设计模式+数据结构与算法等”
mysql pid not found_解决 MySQL manager or server PID file could not be found! 的方法
weixin_39858275的博客
01-27 183
[root@centos var]# service mysqld stopMySQL manager or server PID file could not be found! [FAILED]解决办法：首先查看一下进程[root@centos mysql]# ps aux |grep mysq*root 2643 0.0 0.2 4536 1224 ? ...
MySQL server PID file could not be found! 问题解决
小海的专栏
07-06 9421
今天重启mysql的时候出现了一个蛋疼的错误，花了很长时间找遍百度和谷歌，试遍各种解决方法，没用，一点改变都没有 既不是磁盘满了，也不是.....等等等，反正都不是 最最蛋疼的是没有日志！！！满脸懵逼生无可恋 结果最终的解决办法是：重启机器！！！ ERROR! MySQL server PID file could not be found! Starting MyS
解决 MySQL manager or server PID file could not be found! 的方法
weixin_34104341的博客
03-29 163
[root@centos var]# service mysqld stop MySQL manager or server PID file could not be found! [FAILED] 解决办法： 首先查看一下进程 [root@centos mysql]# ps aux |grep mysq* root 2643 0.0 0...
mysql启动时报错：Starting MySQL… ERROR! The server quit without updating PID file
12-14
MySQL是世界上最流行的关系型数据库管理系统之一，当遇到“Starting MySQL… ERROR! The server quit without updating PID file”的启动错误时，通常意味着服务器未能成功启动并更新其进程ID（PID）文件，这可能是...
ERROR! MySQL server PID file could not be found!的解决方法
kodmoqn的博客
06-07 2214
ERROR! MySQL server PID file could not be found!的解决方法
ERROR! MySQL server PID file could not be found! Starting MySQL . ERROR! The server quit without up
huanglei1234567890的专栏
05-30 3549
一般的问题是没有权限。1）解决方法 ：给予权限，执行 “chown -R mysql:mysql /var/data” “chmod -R 755 /usr/local/mysql/data”  然后重新启动mysqld！2）如果1还是不可以，那可能是由于mac系统升级导致的权限不够，执行如下sudo chown -R mysql /usr/local/mysql/data一般就可以了。...
MySQL server PID file could not be found!
weixin_34410662的博客
09-20 119
重启mysql提示MySQL server PID file could not be found! Starting MySQL...The server quit without updating PID file (/usr/local/mysql/data/rekfan.pid). 我只能呵呵了吗？不是。 我是这样做的，先看下是不是有这个进程，然后结束，再重启，代码：   p...
Linux The server quit without updating PID file的几种解决方法
热门推荐
zsk_john的技术分享专用博客
07-08 9万+
Linux The server quit without updating PID file的几种解决方法 不管是在安装还是运行MySQL的时候，都很有可能遇到报错：Linux The server quit without updating PID file。字面意思是无法更新pid文件，pid大家都懂得，就是MySQLserver的主进程，MySQL中比较重要的三个文件，一个是管进程的，也就是上面报错的那个pid文件，这个文件名是本机的域名加pid后缀，第二个文件是mysql.sock 文件，这..
Starting MySQL...... ERROR! Manager of pid-file quit without updating file.
weixin_33787529的博客
01-02 509
[root@localhost mysql]# /etc/init.d/mysqld startStarting MySQL...... ERROR! Manager of pid-file quit without updating file.下面是错误日志[root@localhost mysql]# cat /data/mysql/localhost.err15122...
出现ERROR The server quit without updating PID file
qq_45688439的博客
01-04 1万+
万恶之源 ERROR! The server quit without updating PID file (/usr/local/var/mysql/XXXX.local.pid) 解决办法 本人使用brew install mysql 下载，macOS： gg之，推荐按下面的顺序一个一个试： 1.可能进程里已经存在mysql进程 解决方法：用命令ps -ef|grep mysqld查看是否有mysqld进程，如果有使用“kill -9 进程号”杀死，然后重新启动mysqld！（作者是做完第五条再做这个
mysql服务启动失败 Starting MySQL. ERROR! The server quit without updating PID file
mark's technic world
08-27 2万+
问题描述】 使用 service mysqld start  启动MySQL服务失败，提示 Starting MySQL. ERROR! The server quit without updating PID file 【解决方案】 在my.cnf配置文件中的 [mysqld_safe] 下添加  log-error = /apps/logs
解决执行Mysql报错: ERROR: The server quit without updating PID file (/data/xxx.pid)
xiaoyouyouaaa的博客
04-20 4231
解决执行Mysql报错: ERROR! The server quit without updating PID file (/data/xxx.pid), 以及​ The innodb_system data file ‘./ibdata1‘ is of a different size 12800 pages
ERROR! MySQL server PID file could not be found! Starting MySQL... ERROR! The server quit without updating PID file (/home/mysql/mysql.pid).
12-28
ERROR! MySQL server PID file could not be found! 这个错误通常是由于MySQL无法找到PID文件而导致的。PID文件是MySQL服务器进程的标识文件，用于记录服务器进程的ID。当MySQL启动时，它会尝试读取PID文件以确定服务器是否已经在运行。 出现这个错误的原因可能有以下几种情况： 1. PID文件路径错误：MySQL配置文件中指定的PID文件路径可能不正确。你可以检查MySQL配置文件（通常是my.cnf或my.ini）中的pid-file参数，确保它指向正确的路径。 2. 权限问题：MySQL进程可能没有足够的权限在指定的路径下创建PID文件。你可以检查PID文件所在目录的权限，并确保MySQL进程有足够的权限在该目录下创建文件。 3. MySQL进程已经在运行：如果MySQL进程已经在运行，但是PID文件却不存在，那么可能是由于之前的MySQL进程异常退出而没有删除PID文件。你可以尝试手动删除PID文件，并重新启动MySQL。 以下是一个示例的解决方法： . 检查PID文件路径是否正确： - 打开MySQL配置文件（通常是my.cnf或my.ini）。 - 查找pid-file参数，并确保它指向正确的路径，例如：pid-file=/var/run/mysqld/mysqld.pid。 2. 检查PID文件所在目录的权限： - 使用ls -l命令检查PID文件所在目录的权限，例如：ls -l /var/run/mysqld/。 - 确保MySQL进程有足够的权限在该目录下创建文件，例如：sudo chown mysql:mysql /var/run/mysqld/。 3. 删除PID文件并重新启动MySQL： - 使用rm命令删除PID文件，例如：sudo rm /var/run/mysqld/mysqld.pid。 - 重新启动MySQL服务，例如：sudo service mysql restart。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值