[root@QAQ ~]# sudo tail -n 50 /var/log/mysql/error.log 2023-07-14T02:43:01.816556Z 0 [Note] Shutting down plugin 'partition' 2023-07-14T02:43:01.816558Z 0 [Note] Shutting down plugin 'BLACKHOLE' 2023-07-14T02:43:01.816566Z 0 [Note] Shutting down plugin 'ARCHIVE' 2023-07-14T02:43:01.816568Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2023-07-14T02:43:01.816594Z 0 [Note] Shutting down plugin 'MRG_MYISAM' 2023-07-14T02:43:01.816597Z 0 [Note] Shutting down plugin 'MyISAM' 2023-07-14T02:43:01.816605Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL' 2023-07-14T02:43:01.816608Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2023-07-14T02:43:01.816610Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2023-07-14T02:43:01.816612Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2023-07-14T02:43:01.816614Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2023-07-14T02:43:01.816616Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2023-07-14T02:43:01.816618Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2023-07-14T02:43:01.816620Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2023-07-14T02:43:01.816622Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2023-07-14T02:43:01.816624Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2023-07-14T02:43:01.816626Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2023-07-14T02:43:01.816628Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2023-07-14T02:43:01.816630Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2023-07-14T02:43:01.816632Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2023-07-14T02:43:01.816634Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2023-07-14T02:43:01.816636Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2023-07-14T02:43:01.816638Z 0 [Note] Shutting down plugin 'INNODB_METRICS' 2023-07-14T02:43:01.816640Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO' 2023-07-14T02:43:01.816642Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2023-07-14T02:43:01.816644Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2023-07-14T02:43:01.816645Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2023-07-14T02:43:01.816647Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2023-07-14T02:43:01.816649Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2023-07-14T02:43:01.816651Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2023-07-14T02:43:01.816653Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM' 2023-07-14T02:43:01.816655Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2023-07-14T02:43:01.816657Z 0 [Note] Shutting down plugin 'INNODB_CMP' 2023-07-14T02:43:01.816659Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2023-07-14T02:43:01.816661Z 0 [Note] Shutting down plugin 'INNODB_LOCKS' 2023-07-14T02:43:01.816664Z 0 [Note] Shutting down plugin 'INNODB_TRX' 2023-07-14T02:43:01.816666Z 0 [Note] Shutting down plugin 'InnoDB' 2023-07-14T02:43:01.816703Z 0 [Note] InnoDB: FTS optimize thread exiting. 2023-07-14T02:43:01.816748Z 0 [Note] InnoDB: Starting shutdown... 2023-07-14T02:43:01.916861Z 0 [Note] InnoDB: Dumping buffer pool(s) to /www/server/data/ib_buffer_pool 2023-07-14T02:43:01.917024Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 230714 10:43:01 2023-07-14T02:43:03.438469Z 0 [Note] InnoDB: Shutdown completed; log sequence number 2767449 2023-07-14T02:43:03.439797Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2023-07-14T02:43:03.439814Z 0 [Note] Shutting down plugin 'MEMORY' 2023-07-14T02:43:03.439819Z 0 [Note] Shutting down plugin 'CSV' 2023-07-14T02:43:03.439823Z 0 [Note] Shutting down plugin 'sha256_password' 2023-07-14T02:43:03.439825Z 0 [Note] Shutting down plugin 'mysql_native_password' 2023-07-14T02:43:03.439939Z 0 [Note] Shutting down plugin 'binlog' 2023-07-14T02:43:03.440752Z 0 [Note] /www/server/mysql/bin/mysqld: Shutdown complete
时间: 2024-04-15 16:27:59 浏览: 111
根据您提供的最新错误日志,MySQL 在关闭过程中没有显示任何明显的错误。这表明 MySQL 进程正常关闭。
为了进一步排除问题,我建议您尝试执行以下步骤:
1. 检查 MySQL 进程是否已完全终止。您可以使用以下命令检查:
```
ps aux | grep mysql
```
确保没有任何与 MySQL 相关的进程正在运行。
2. 尝试手动启动 MySQL 服务,并查看是否有任何错误消息。使用以下命令启动服务:
```
sudo systemctl start mysqld
```
3. 如果手动启动 MySQL 服务时出现错误,请检查 `/var/log/mysql/error.log` 中的最新错误日志,以获取详细的错误信息。您可以使用以下命令查看最新的错误日志:
```
sudo tail -n 50 /var/log/mysql/error.log
```
如果问题仍然存在,请提供最新的日志信息和任何其他相关配置文件的内容,以便我能够更好地帮助您解决问题。
相关问题
-- 一个 ID 为 19 的新会话已为用户 root 建立。 -- -- 该会话的首进程为 2221644。 7月 14 10:24:11 QAQ systemd[1]: Started Session 19 of user root. -- Subject: session-19.scope 单元已结束启动 -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- session-19.scope 单元已结束启动。 -- -- 启动结果为“done”。 7月 14 10:24:11 QAQ sshd[2221644]: pam_unix(sshd:session): session opened for user root by (uid=0) 7月 14 10:25:01 QAQ CROND[2224034]: (root) CMD (flock -xn "/var/log/oneav/cron.lock" -c '/opt/threatbook/OneAV/oneav/script/install/oneav_service_monitor.sh') 7月 14 10:25:20 QAQ kernel: device eth0 entered promiscuous mode 7月 14 10:25:26 QAQ kernel: device eth0 left promiscuous mode 7月 14 10:26:23 QAQ sudo[2227882]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/tail -n 50 /var/log/mysql/error.log 7月 14 10:26:23 QAQ sudo[2227882]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice 7月 14 10:26:23 QAQ sudo[2227882]: pam_unix(sudo:session): session opened for user root by root(uid=0) 7月 14 10:26:23 QAQ sudo[2227882]: pam_unix(sudo:session): session closed for user root lines 2357-2375/2375 (END)
根据提供的日志信息,我看到您使用 `tail` 命令查看了 `/var/log/mysql/error.log` 文件的最后 50 行,并显示了部分输出。
若要修改日志文件的显示行数,您可以通过调整 `tail` 命令的参数来实现。例如,如果您只想显示最后 10 行,可以使用以下命令:
```
tail -n 10 /var/log/mysql/error.log
```
这将显示 `/var/log/mysql/error.log` 文件的最后 10 行。
请注意,根据给出的日志输出,您已经成功查看了文件的最后 50 行。如果您有其他问题或需要其他帮助,请告诉我。
阅读全文