半人疯 发表于 2017-10-30 23:04:11

mysql 升级,screen进程没有了,启动不成功

mysql 升级 5.7,screen 进程没有了 。
然后按照如升级失败可将/usr/local/oldmysql日期的目录重命名为mysql,并将/etc/下的my.conf.bak.日期的配置文件重命名为my.cnf和/etc/init.d/下的mysql.bak.日期重命名为mysql即可恢复原mysql。(下面MySQL升级至MariaDB及升级MariaDB一样)
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


操作后sudo /etc/init.d/mysql restart
[....] 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.
failed!systemctl status mysql.service
● mysql.service - LSB: start and stop MySQL
   Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-10-30 22:56:24 CST; 55s ago
   Docs: man:systemd-sysv-generator(8)
Process: 12863 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Oct 30 22:56:23 VM-34-185-ubuntu systemd: Starting LSB: start and stop MySQL...
Oct 30 22:56:23 VM-34-185-ubuntu mysql: Starting MySQL
Oct 30 22:56:24 VM-34-185-ubuntu mysql: . * The server quit without updating PID file (/usr/local/mysql/var/VM-34-185-
Oct 30 22:56:24 VM-34-185-ubuntu systemd: mysql.service: Control process exited, code=exited status=1
Oct 30 22:56:24 VM-34-185-ubuntu systemd: Failed to start LSB: start and stop MySQL.
Oct 30 22:56:24 VM-34-185-ubuntu systemd: mysql.service: Unit entered failed state.
Oct 30 22:56:24 VM-34-185-ubuntu systemd: mysql.service: Failed with result 'exit-code'.journalctl -xe
Oct 30 22:59:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 22:59:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:00:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:00:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/sbin/ntpdate ntpupdate.tencentyun.com >/dev/null &)
Oct 30 23:00:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:00:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:01:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:01:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:01:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
Oct 30 23:01:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
Oct 30 23:01:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:01:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:02:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:02:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:02:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
Oct 30 23:02:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
Oct 30 23:02:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:02:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:03:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:03:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 30 23:03:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/sa/agent/secu-tcs-agent-mon-safe.sh /usr/local/sa/agent
Oct 30 23:03:01 VM-34-185-ubuntu CRON: (root) CMD (/usr/local/qcloud/stargate/admin/start.sh > /dev/null 2>&1 &)
Oct 30 23:03:01 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root
Oct 30 23:03:02 VM-34-185-ubuntu CRON: pam_unix(cron:session): session closed for user root

[ 本帖最后由 半人疯 于 2017-10-30 23:05 编辑 ]

半人疯 发表于 2017-10-30 23:24:54

还可以解救么

如果不能怎么能提取原来的数据库文件 :L忘记备份了

licess 发表于 2017-10-31 13:17:59

回复 2# 的帖子

前面已经贴出了恢复的方法,恢复后就是带原来数据库的
另外/root 下面也有另外单独备份的完整sql 备份文件
页: [1]
查看完整版本: mysql 升级,screen进程没有了,启动不成功