想着wordpress反正可以在线安装,就 不想在本地上写好再发了。复述一遍经过, 登录阿里云完成域名解析,之后在宝塔新增站点,为其添加数据库,然后通过域名访问,来到了wordpress的安装界面,开始一步步安装。非常的和谐自然,wordpress的默认界面都是很丑的,在安装好以后,我就打开了后台主题准备挑选模板。然后就出现了这种问题。
但是这难不倒我,捣鼓了半天,发现数据库被异常关闭了。我就在宝塔面板 重启启动mysql,在重新刷新网页,正常显示。
然而,过了没一会,mysql又自动关闭。下面是数据库日志
2021-02-25 20:21:22 14514 [Note] InnoDB: The InnoDB memory heap is disabled
2021-02-25 20:21:22 14514 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-02-25 20:21:22 14514 [Note] InnoDB: Memory barrier is not used
2021-02-25 20:21:22 14514 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-25 20:21:22 14514 [Note] InnoDB: Using Linux native AIO
2021-02-25 20:21:22 14514 [Note] InnoDB: Using CPU crc32 instructions
2021-02-25 20:21:22 14514 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2021-02-25 20:21:22 14514 [Note] InnoDB: Completed initialization of buffer pool
2021-02-25 20:21:22 14514 [Note] InnoDB: Highest supported file format is Barracuda.
2021-02-25 20:21:22 14514 [Note] InnoDB: The log sequence numbers 25558926 and 25558926 in ibdata files do not match the log sequence number 41317266 in the ib_logfiles!
2021-02-25 20:21:22 14514 [Note] InnoDB: Database was not shutdown normally!
2021-02-25 20:21:22 14514 [Note] InnoDB: Starting crash recovery.
2021-02-25 20:21:22 14514 [Note] InnoDB: Reading tablespace information from the .ibd files...
2021-02-25 20:21:22 14514 [Note] InnoDB: Restoring possible half-written data pages
2021-02-25 20:21:22 14514 [Note] InnoDB: from the doublewrite buffer...