-
-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
数据库无法启动,报错日志如下 #22
Comments
这个是 /data/mysql/log3306/error.log |
mkdir -p /data/mysql/ |
[root@localhost tmp]# yum -y remove everwar-1.2.0-all.el7.centos.x86_64.rpm 无法remove |
那我把mysql目录rm,直接reinstall |
执行systemctl status everwar-mysqld 日志 Oct 24 18:15:50 localhost.localdomain systemd[1]: everwar-mysqld.service: main process exited, code=exited, status=139/n/a |
一键安装的二进制安装包暂时不开放,在内测阶段。 |
期待发布二进制一键安装包 |
mysqld_multi log file version 2.16; run: Tue Oct 24 17:05:57 2023
Starting MySQL servers
2023-10-24T09:05:57.807451Z mysqld_safe error: log-error set to '/data/mysql/log3306/error.log', however file don't exists. Create writable for user 'mysql'.
mysqld_multi log file version 2.16; run: Tue Oct 24 17:13:37 2023
Starting MySQL servers
2023-10-24T09:13:38.271808Z mysqld_safe error: log-error set to '/data/mysql/log3306/error.log', however file don't exists. Create writable for user 'mysql'.
mysqld_multi log file version 2.16; run: Tue Oct 24 17:15:56 2023
Starting MySQL servers
2023-10-24T09:15:57.454470Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:15:57.480589Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
2023-10-24T09:15:57.613125Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
mysqld_multi log file version 2.16; run: Tue Oct 24 17:19:54 2023
Starting MySQL servers
2023-10-24T09:19:55.427254Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:19:55.450415Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
2023-10-24T09:19:55.594908Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
mysqld_multi log file version 2.16; run: Tue Oct 24 17:19:56 2023
Starting MySQL servers
2023-10-24T09:19:57.437938Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:19:57.462534Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
mysqld_multi log file version 2.16; run: Tue Oct 24 17:19:57 2023
Starting MySQL servers
2023-10-24T09:19:57.594093Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
2023-10-24T09:19:57.993352Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:19:58.017495Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
mysqld_multi log file version 2.16; run: Tue Oct 24 17:19:58 2023
Starting MySQL servers
2023-10-24T09:19:58.153184Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
2023-10-24T09:19:58.585484Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:19:58.612819Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
2023-10-24T09:19:58.754115Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
mysqld_multi log file version 2.16; run: Tue Oct 24 17:19:58 2023
Starting MySQL servers
2023-10-24T09:19:59.221977Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:19:59.247625Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
2023-10-24T09:19:59.382434Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
mysqld_multi log file version 2.16; run: Tue Oct 24 17:22:58 2023
Starting MySQL servers
2023-10-24T09:22:58.905305Z mysqld_safe Logging to '/data/mysql/log3306/error.log'.
2023-10-24T09:22:58.928231Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data3306
2023-10-24T09:22:59.063396Z mysqld_safe mysqld from pid file /data/mysql/data3306/mysqld.pid ended
The text was updated successfully, but these errors were encountered: