小白上路又遇石头绊脚...请求帮助

McWong 发表于 2017-2-20 10:38:45

Shutting down MySQL.... SUCCESS!
Starting MySQL.170220 10:32:35 mysqld_safe Logging to '/usr/local/mariadb/var/mariadb.err'.
. SUCCESS!

新装lnmp已经出现这提示,不过没有影响使用一直不知道什么回事...
知道昨天才知道这是个报错,请大神们指教下,问题如何处理...

licess 发表于 2017-2-20 12:33:32

这是正常启动信息，而且都提示你成功了！
你从哪里知道这是报错的！？

McWong 发表于 2017-2-20 12:53:07

回复 2# 的帖子

哦哦，这是正常启动信息来的啊~
军哥请看看报告，内含有我调数据库后不能启动的信息的...我怕怕立即调回来

licess 发表于 2017-2-20 20:28:44

回复 3# 的帖子

1702200:57:39 InnoDB: The InnoDB memory heap is disabled
1702200:57:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
1702200:57:39 InnoDB: Compressed tables use zlib 1.2.7
1702200:57:39 InnoDB: Initializing buffer pool, size = 2.0G
1702200:57:39 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /usr/local/mariadb/var/ib_logfile0 is of different size 0 268435456 bytes
InnoDB: than specified in the .cnf file 0 536870912 bytes!
InnoDB: Possible causes for this error:
(a) Incorrect log file is used or log file size is changed
(b) In case default size is used this log file is from 10.0
(c) Log file is corrupted or there was not enough disk space
In case (b) you need to set innodb_log_file_size = 48M
1702200:57:39 Plugin 'InnoDB' init function returned error.
1702200:57:39 Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
1702200:57:39 Unknown/unsupported storage engine: InnoDB
1702200:57:39 Aborting
你修改过innodb_log_file_size参数吗？

如要修改该参数需要先正常关闭mysql，再将数据库目录下的ib_logfile0、ib_logfile1、ib_logfile2等之类的文件移动到其他目录
修改好innodb_log_file_size参数后再启动mysql

页: [1]

VPS侦探论坛's Archiver