Forcing close of thread 123 use

记一次mysql5.5假死的问题

......
181023 22:00:03  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 11386948072
181023 22:00:09  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
181023 22:00:10  InnoDB: Waiting for the background threads to start
181023 22:00:11 InnoDB: 5.5.53 started; log sequence number 11386948072
181023 22:00:11 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
181023 22:00:11 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
181023 22:00:11 [Note] Server socket created on IP: '0.0.0.0'.
181023 22:00:12 [Note] Event Scheduler: Loaded 0 events
181023 22:00:12 [Note] MySQLa: ready for connections.
Version: '5.5.53'  socket: ''  port: 3306  MySQL Community Server (GPL)
181229 22:33:03 [Note] MySQLa: Normal shutdown

181229 22:33:03 [Note] Event Scheduler: Purging the queue. 0 events
181229 22:33:05  InnoDB: Starting shutdown...
181229 22:33:05  InnoDB: Shutdown completed; log sequence number 15328113867
181229 22:33:05 [Note] MySQLa: Shutdown complete

181229 22:33:05 [Note] Plugin 'FEDERATED' is disabled.
181229 22:33:05 InnoDB: The InnoDB memory heap is disabled
181229 22:33:05 InnoDB: Mutexes and rw_locks use Windows interlocked functions
181229 22:33:05 InnoDB: Compressed tables use zlib 1.2.3
181229 22:33:05 InnoDB: Initializing buffer pool, size = 47.0M
181229 22:33:05 InnoDB: Completed initialization of buffer pool
181229 22:33:05 InnoDB: highest supported file format is Barracuda.
181229 22:33:06  InnoDB: Waiting for the background threads to start
181229 22:33:07 InnoDB: 5.5.53 started; log sequence number 15328113867
181229 22:33:07 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
181229 22:33:07 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
181229 22:33:07 [Note] Server socket created on IP: '0.0.0.0'.
181229 22:33:07 [Note] Event Scheduler: Loaded 0 events
181229 22:33:07 [Note] MySQLa: ready for connections.
Version: '5.5.53'  socket: ''  port: 3306  MySQL Community Server (GPL)
190223  9:29:49 [Note] MySQLa: Normal shutdown

190223  9:29:49 [Note] Event Scheduler: Purging the queue. 0 events
190223  9:29:51 [Warning] MySQLa: Forcing close of thread 560392  user: 'root'
190223  9:29:51 [Warning] MySQLa: Forcing close of thread 560391  user: 'root'
......

状态表现

重启mysql网站就可以正常访问

排查

在mysql文件中找到了日志文件
搜索了一下找到解决方法
在my.ini配置中的[mysqld]下加入
skip-locking
skip-name-resolve
mysql重启错误：1076错误
查看了事件查看器中的windows日志，unknown option --skip-locking，明显这参数配置有问题。。。
所以又搜索了一下得到答案

答案

在新版本的mysql中，skip-locking被替换成了skip-external-locking