Chinaunix首页 | 论坛 | 博客
  • 博客访问: 2829791
  • 博文数量: 587
  • 博客积分: 6356
  • 博客等级: 准将
  • 技术积分: 6410
  • 用 户 组: 普通用户
  • 注册时间: 2008-10-23 10:54
个人简介

器量大者,福泽必厚

文章分类

全部博文(587)

文章存档

2019年(3)

2018年(1)

2017年(29)

2016年(39)

2015年(66)

2014年(117)

2013年(136)

2012年(58)

2011年(34)

2010年(50)

2009年(38)

2008年(16)

分类: LINUX

2016-05-10 17:07:22

[root@localhost var]# tail -f  localhost.localdomain.err 
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_CMP'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'INNODB_TRX'
2016-05-10 16:32:31 1842 [Note] Shutting down plugin 'InnoDB'
2016-05-10 16:32:31 1842 [Note] InnoDB: FTS optimize thread exiting.
2016-05-10 16:32:31 1842 [Note] InnoDB: Starting shutdown...
2016-05-10 16:33:31 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:34:31 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:35:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:36:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:37:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:38:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:39:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:40:32 1842 [Note] InnoDB: Waiting for purge thread to be suspended
2016-05-10 16:41:33 1842 [Note] InnoDB: Waiting for purge thread to be suspended
###一直停在这里,大概有10分钟还多,这时候lsof -i:3306 发现端口已经不在监听了,网上搜了下,仿佛是一个bug

没办法了,只好ps aux | grep  mysql   找到pid kill 掉,发现kill不了,启动的时候,有下面的报错!

160510 16:41:58 mysqld_safe A mysqld process already exists
2016-05-10 16:42:33 1842 [Note] InnoDB: Waiting for purge thread to be suspended
##不得已只好kill -9 了,虽然我清楚不能使用-9 ,现在万不得已了,kill -9 后,发现mysql相关进程真的没有了,于是/etc/init.d/mysql start

160510 16:43:19 mysqld_safe Starting mysqld daemon with databases from /data/mysql/var
2016-05-10 16:43:20 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2016-05-10 16:43:20 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-05-10 16:43:20 0 [Note] /data/mysql/bin/mysqld (mysqld 5.6.24-log) starting as process 18706 ...
2016-05-10 16:43:20 18706 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2016-05-10 16:43:20 18706 [Note] Plugin 'FEDERATED' is disabled.
2016-05-10 16:43:20 7f97327377e0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-05-10 16:43:20 18706 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-10 16:43:20 18706 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-10 16:43:20 18706 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-05-10 16:43:20 18706 [Note] InnoDB: Memory barrier is not used
2016-05-10 16:43:20 18706 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-10 16:43:20 18706 [Note] InnoDB: Not using CPU crc32 instructions
2016-05-10 16:43:20 18706 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-05-10 16:43:21 18706 [Note] InnoDB: Completed initialization of buffer pool
2016-05-10 16:43:21 18706 [Note] InnoDB: Highest supported file format is Barracuda.
2016-05-10 16:43:21 18706 [Note] InnoDB: Log scan progressed past the checkpoint lsn 431065305061
2016-05-10 16:43:21 18706 [Note] InnoDB: Database was not shutdown normally!
2016-05-10 16:43:21 18706 [Note] InnoDB: Starting crash recovery.
2016-05-10 16:43:21 18706 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-05-10 16:43:21 18706 [Note] InnoDB: Restoring possible half-written data pages 
2016-05-10 16:43:21 18706 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 431070547456
InnoDB: Doing recovery: scanned up to log sequence number 431075790336
InnoDB: Doing recovery: scanned up to log sequence number 431081033216
InnoDB: Doing recovery: scanned up to log sequence number 431086276096
InnoDB: Doing recovery: scanned up to log sequence number 431091518976
InnoDB: Doing recovery: scanned up to log sequence number 431096761856
InnoDB: Doing recovery: scanned up to log sequence number 431102004736
InnoDB: Doing recovery: scanned up to log sequence number 431107247616
InnoDB: Doing recovery: scanned up to log sequence number 431112490496
InnoDB: Doing recovery: scanned up to log sequence number 431117733376
InnoDB: Doing recovery: scanned up to log sequence number 431122976256
InnoDB: Doing recovery: scanned up to log sequence number 431128219136
InnoDB: Doing recovery: scanned up to log sequence number 431133462016
InnoDB: Doing recovery: scanned up to log sequence number 431138704896
InnoDB: Doing recovery: scanned up to log sequence number 431143947776
InnoDB: Doing recovery: scanned up to log sequence number 431146136153
2016-05-10 16:43:30 18706 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 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   
###这里从0 开始到99 ,整个的数据库恢复过程,需要些时间,和库的大小和硬件性能有关系!
InnoDB: Apply batch completed
2016-05-10 16:54:59 18706 [Note] InnoDB: 128 rollback segment(s) are active.
2016-05-10 16:54:59 18706 [Note] InnoDB: Waiting for purge to start
2016-05-10 16:54:59 18706 [Note] InnoDB: 5.6.24 started; log sequence number 431146136153
2016-05-10 16:55:00 18706 [Note] RSA private key file not found: /data/mysql/var//private_key.pem. Some authentication plugins will not work.
2016-05-10 16:55:00 18706 [Note] RSA public key file not found: /data/mysql/var//public_key.pem. Some authentication plugins will not work.
2016-05-10 16:55:00 18706 [Note] Server hostname (bind-address): '*'; port: 3306
2016-05-10 16:55:00 18706 [Note] IPv6 is available.
2016-05-10 16:55:00 18706 [Note]   - '::' resolves to '::';
2016-05-10 16:55:00 18706 [Note] Server socket created on IP: '::'.
2016-05-10 16:55:00 18706 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode.
2016-05-10 16:55:00 18706 [Warning] 'user' entry '@localhost.localdomain' ignored in --skip-name-resolve mode.
2016-05-10 16:55:00 18706 [Warning] 'proxies_priv' entry '@ root@localhost.localdomain' ignored in --skip-name-resolve mode.
2016-05-10 16:55:02 18706 [Note] Event Scheduler: Loaded 0 events
2016-05-10 16:55:02 18706 [Note] /data/mysql/bin/mysqld: ready for connections.
Version: '5.6.24-log'  socket: '/data/mysql/mysql.sock'  port: 3306  Source distribution


到了这里,lsof -i:3306  已经在监听了,可以连接了!
##简单记录下!
阅读(2791) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~