VPS侦探论坛

标题: mysql 升级，screen进程没有了，启动不成功 [打印本页]
作者: 半人疯    时间: 2017-10-30 23:04
标题: mysql 升级，screen进程没有了，启动不成功
mysql 升级 5.7，screen 进程没有了 。
然后按照
  1. 如升级失败可将/usr/local/oldmysql日期的目录重命名为mysql，并将/etc/下的my.conf.bak.日期的配置文件重命名为my.cnf和/etc/init.d/下的mysql.bak.日期重命名为mysql即可恢复原mysql。(下面MySQL升级至MariaDB及升级MariaDB一样)
  2. 1.4上init.d的启动脚本和my.cnf在/usr/local/oldmysql日期的目录下名字分别为init.d.mysql.bak.日期和my.cnf.bak.日期。
复制代码

/usr/local/mysql
/etc/my.cnf
/etc/init.d/mysql


操作后
  1. sudo /etc/init.d/mysql restart
  2. [....] Restarting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
  3. failed!
复制代码
  1. systemctl status mysql.service
  2. ● mysql.service - LSB: start and stop MySQL
  3.    Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
  4.    Active: failed (Result: exit-code) since Mon 2017-10-30 22:56:24 CST; 55s ago
  5.      Docs: man:systemd-sysv-generator(8)
  6.   Process: 12863 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

  8. Oct 30 22:56:23 VM-34-185-ubuntu systemd[1]: Starting LSB: start and stop MySQL...
  9. Oct 30 22:56:23 VM-34-185-ubuntu mysql[12863]: Starting MySQL
  10. Oct 30 22:56:24 VM-34-185-ubuntu mysql[12863]: . * The server quit without updating PID file (/usr/local/mysql/var/VM-34-185-
  11. Oct 30 22:56:24 VM-34-185-ubuntu systemd[1]: mysql.service: Control process exited, code=exited status=1
  12. Oct 30 22:56:24 VM-34-185-ubuntu systemd[1]: Failed to start LSB: start and stop MySQL.
  13. Oct 30 22:56:24 VM-34-185-ubuntu systemd[1]: mysql.service: Unit entered failed state.
  14. Oct 30 22:56:24 VM-34-185-ubuntu systemd[1]: mysql.service: Failed with result 'exit-code'.
复制代码
  1. journalctl -xe
  2. Oct 30 22:59:01 VM-34-185-ubuntu CRON[13562]: pam_unix(cron:session): session closed for user root
  3. Oct 30 22:59:01 VM-34-185-ubuntu CRON[13563]: pam_unix(cron:session): session closed for user root
  4. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13640]: pam_unix(cron:session): session opened for user root by (uid=0)
  5. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13641]: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
  6. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13638]: pam_unix(cron:session): session opened for user root by (uid=0)
  7. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13639]: pam_unix(cron:session): session opened for user root by (uid=0)
  8. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13643]: (root) CMD (/usr/sbin/ntpdate ntpupdate.tencentyun.com >/dev/null &)
  9. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13644]: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
  10. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13638]: pam_unix(cron:session): session closed for user root
  11. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13639]: pam_unix(cron:session): session closed for user root
  12. Oct 30 23:00:01 VM-34-185-ubuntu CRON[13640]: pam_unix(cron:session): session closed for user root
  13. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13718]: pam_unix(cron:session): session opened for user root by (uid=0)
  14. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13717]: pam_unix(cron:session): session opened for user root by (uid=0)
  15. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13719]: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
  16. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13720]: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
  17. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13717]: pam_unix(cron:session): session closed for user root
  18. Oct 30 23:01:01 VM-34-185-ubuntu CRON[13718]: pam_unix(cron:session): session closed for user root
  19. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13793]: pam_unix(cron:session): session opened for user root by (uid=0)
  20. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13794]: pam_unix(cron:session): session opened for user root by (uid=0)
  21. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13795]: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
  22. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13796]: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
  23. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13793]: pam_unix(cron:session): session closed for user root
  24. Oct 30 23:02:01 VM-34-185-ubuntu CRON[13794]: pam_unix(cron:session): session closed for user root
  25. Oct 30 23:03:01 VM-34-185-ubuntu CRON[13870]: pam_unix(cron:session): session opened for user root by (uid=0)
  26. Oct 30 23:03:01 VM-34-185-ubuntu CRON[13869]: pam_unix(cron:session): session opened for user root by (uid=0)
  27. Oct 30 23:03:01 VM-34-185-ubuntu CRON[13871]: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
  28. Oct 30 23:03:01 VM-34-185-ubuntu CRON[13872]: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
  29. Oct 30 23:03:01 VM-34-185-ubuntu CRON[13869]: pam_unix(cron:session): session closed for user root
  30. Oct 30 23:03:02 VM-34-185-ubuntu CRON[13870]: pam_unix(cron:session): session closed for user root
复制代码

[ 本帖最后由 半人疯 于 2017-10-30 23:05 编辑 ]
作者: 半人疯    时间: 2017-10-30 23:24
还可以解救么

如果不能  怎么能提取原来的数据库文件   忘记备份了
作者: licess    时间: 2017-10-31 13:17
标题: 回复 2# 的帖子
前面已经贴出了恢复的方法，恢复后就是带原来数据库的
另外/root 下面也有另外单独备份的完整sql 备份文件



欢迎光临 VPS侦探论坛 (https://bbs.lnmp.com/) Powered by Discuz! X3.4